No, here it is again...
Sorry so you did, I lost track of who was saying no collisions and all the exaggerations.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
No, here it is again...
Perhaps because you brought up 1967 back in post #6
Perhaps also you missed this:
June 2012 Oklahoma
http://www.dailymail.co.uk/news/art...missing-freight-train-collision-Oklahoma.html
http://www.ntsb.gov/doclib/reports/2013/RAR1302.pdf
As stated, it does seem in that light that somebody somewhere has fallen down very badly on this one.
How can you make this determination based on what little information is available? .
UP had a collision in 2012 in Goodwell, Oklahoma, about 700 miles away. For you UK folks, that is about the length of your entire country top to bottom. it would be quite a stretch to say it is the 'same area'.
Jesus T. freaking Christ! See if I start another thread in this forum. Can't even post anything without some people starting a freaking arguement. Always somebody has to start one. I'm so damn sick of this
With regard to your comment regarding the size of the British rail network...
What caused this is still unknown ... but when this same thing happens over, and over, time, and time again ... It gets my britches all bunched up in a wad when several crew members are killed.
I did read a report on how train crews are forced to work repeated shifts, long hours, and are drunk from overwork exhaustion, unfit for the drive ... (finding that link)
http://www.angelsontrack.org/rrsafety.html
http://utu.org/2005/04/24/fatigue-killing-railroad-crews/
A 1997 survey of more than 1,500 freight crew members by the North American Rail Alertness Partnership — a group of industry, government and union officials — found that about 80% had reported to work while tired, extremely tired or exhausted.
Many put in 60 to 70 hours a week, sometimes more. They can be called to work any time during the day or night, constantly disrupting their sleep patterns.
The irregular shifts often place bleary-eyed crews at the controls between 3 and 6 a.m., when experts say the body’s natural circadian rhythm produces maximum drowsiness.
The United Transportation Union countered that the railroad was severely understaffed in the area and many conductors were exhausted from working for weeks — sometimes months — without a day off.
“We were running with a skeleton crew,” said union official Greg Haskin. “Guys were burned out and calling in sick. They were working 12- to 16-hour days up to 90 days straight. You can’t expect people to work like that and be safe.”
Moreover, it is legal under the act for engineers, conductors and brake operators to work up to 432 hours a month. In contrast, truckers can drive no more than 260 hours a month under federal law, while commercial pilots are restricted to 100 hours of flying a month.
Just because multiple train crash sites are separated by County or State boundary lines, or are on multiple separate rail lines, or involve multiple railroad companies ... That does not mean that they are not happening in the same "general area" ... a "general area" can mean, ie: "The Midwest US" or the "Mississippi River to California coast".
More than likely all the blame will be easily put on the deceased crew members, "operator error" ... even though the CTC might have been defective, that will all be covered up by falsification by RR company legal crews.
1) https://www.ble-t.org/pr/archive/headline031500c.html
2) http://www.insiderexclusive.com/jus...f-railroads-24-million-dollar-cover-up-part-i
3) https://www.google.com/search?q=bns...ing+fatalities&rls=org.mozilla:en-US:official
Just because multiple train crash sites are separated by County or State boundary lines, or are on multiple separate rail lines, or involve multiple railroad companies ... That does not mean that they are not happening in the same "general area" ... a "general area" can mean, ie: "The Midwest US" or the "Mississippi River to California coast".
Since the accident has occurred in an area where other accidents have occurred in the past, then I wonder if there is something wrong with the track layout such as a signal sighting problem.
I would fully agree, however that is all relative. This all took place on planet earth too.
I don't agree that this makes the accidents related other that they were of similar nature. The general opinion seemed to be "didn't this just happen in the same area?" mostly because of the comment that you yourself made. If it had, then yes I would also speculate that something must be wrong with the track or systems governing it or some other related factor between the two, but this has not been shown to be the case.
Not that I place blame on JCitron directly for coming to this conclusion, but it would be easy to be mislead to believe that this was actually the case when the wreck sites were very far from each other.