Moderators: jsumali2, richierich, ua900, PanAm_DC10, hOMSaR
william wrote:Surely, the communication sequence with the railroad will be investigated and changes made. It was a local suburban train so getting in touch with the Dispatcher should not have been that hard (unless it was on UP or BNSF tracks).
wjcandee wrote:william wrote:Surely, the communication sequence with the railroad will be investigated and changes made. It was a local suburban train so getting in touch with the Dispatcher should not have been that hard (unless it was on UP or BNSF tracks).
You're right. I now see where the first officer on the scene says he contacted the railroad. Let's hope they take the investigation as seriously as they would if the train had arrived 5 seconds earlier...
Even at a big railroad like UP or BNSF, they have centralized dispatching centers and the ability to see quickly whether trains are in the vicinity of a location and change signals and/or radio the train, so if the communication links and procedures are reliable and smart, even a 2-mile-long freight could have safely been brought to a stop given enough time.
If you look at Twitter, there are already a zillion "why was the train going so fast in a densely-populated area" posts. That should scare the crap out of Metrolink (and the area's railroads), because railroads operate at the speeds they do based upon centuries-old understandings with the areas they serve. We just spent billions on Positive Train Control to prevent what were otherwise very-rare accidents. Crossing collisions with disabled vehicles ARE common, and would seem to be more-readily-preventable if first responders have clear, authenticated access to train dispatch, with specific procedures in place at the railroad.
That train looked to be pretty-close to track speed, which means that the throttle was likely retarded and brakes applied only when the scene came into view of the engineer. No reason to risk the train and its passengers by going into emergency, because it would likely have been futile as of the moment of application.
Amazing how real-life can be even more remarkable than fiction... Takeoff in your 172 on a nice day, engine failure, where-to-land?, survive crash landing on RR tracks, police respond and secure area, then unwarned train bears down, brave police pull you to safety 3 seconds before impact. If I wrote that, an editor would tell me it was trite and implausible. Guess not...
wjcandee wrote:Here in NY, there's usually a railroad emergency number and location identifier posted by crossings. Don't know if they have that in Cali.
william wrote:It is common for Police to have a number to the railroad's Dispatcher Office for cases such as this. The Dispatcher throws up Red signals when notified of a crossing accident. Not saying it would have stopped this from happening but the communication aspect will be investigated.
Its been stated a freight train hitting a car is akin to someone in a car running over an empty Coke can. A Metrolink train traveling 70-79 mph titting a Cessna 172 crashed on the tracks must have been like going through paper mache.
slcguy wrote:Talk about having a bad day, crash in a plane then nearly get hit by a train.
tjwgrr wrote:A passenger train traveling at 55 mph may take a half a mile or more to stop. A freight train traveling at 55 mph may take at least a mile or more to stop. Stopping distances often exceed lines of sight, so in many cases a train cannot stop in time to avoid hitting something on the tracks.
IADCA wrote:tjwgrr wrote:A passenger train traveling at 55 mph may take a half a mile or more to stop. A freight train traveling at 55 mph may take at least a mile or more to stop. Stopping distances often exceed lines of sight, so in many cases a train cannot stop in time to avoid hitting something on the tracks.
Yes, but any significant braking action will still result in a much less serious collision, and - as almost became tragic in this case - would delay the collision by a critical few seconds. This train appeared to still be going full speed or nearly so (and there's no audible braking sound in the videos I've seen until after the collision). If this train had been a few seconds later, it'd be a lot less dramatic on video. If it had been a few seconds earlier, it'd have been deadly. Seconds do matter.
wjcandee wrote:Remarkable video. Very sad that the responses to the Tweet from LAPD are filled with such puerile and hateful comments. I'm triggered. I need a safe space now.
Also thinking that PD needs a more-robust way of communicating with train dispatchers, who could change signals or, if the train has passed the last signal before the crossing, instruct it by radio, which might have allowed it to slow or perhaps even stop. Here in NY, there's usually a railroad emergency number and location identifier posted by crossings. Don't know if they have that in Cali.
GalaxyFlyer wrote:IADCA wrote:tjwgrr wrote:A passenger train traveling at 55 mph may take a half a mile or more to stop. A freight train traveling at 55 mph may take at least a mile or more to stop. Stopping distances often exceed lines of sight, so in many cases a train cannot stop in time to avoid hitting something on the tracks.
Yes, but any significant braking action will still result in a much less serious collision, and - as almost became tragic in this case - would delay the collision by a critical few seconds. This train appeared to still be going full speed or nearly so (and there's no audible braking sound in the videos I've seen until after the collision). If this train had been a few seconds later, it'd be a lot less dramatic on video. If it had been a few seconds earlier, it'd have been deadly. Seconds do matter.
While true on the aspect of giving time to the revisers, I’ve seen a Conrail demo where their loco hit a car at no more than 10 mph and nobody would have survived.
There are loads of You Tube videos demonstrated the destructive power of even a slow moving train.
william wrote:It is common for Police to have a number to the railroad's Dispatcher Office for cases such as this. The Dispatcher throws up Red signals when notified of a crossing accident. Not saying it would have stopped this from happening but the communication aspect will be investigated.
Its been stated a freight train hitting a car is akin to someone in a car running over an empty Coke can. A Metrolink train traveling 70-79 mph titting a Cessna 172 crashed on the tracks must have been like going through paper mache.
smokeybandit wrote:Train tracks at the end of the runway. How common is that?
GalaxyFlyer wrote:IADCA wrote:tjwgrr wrote:A passenger train traveling at 55 mph may take a half a mile or more to stop. A freight train traveling at 55 mph may take at least a mile or more to stop. Stopping distances often exceed lines of sight, so in many cases a train cannot stop in time to avoid hitting something on the tracks.
Yes, but any significant braking action will still result in a much less serious collision, and - as almost became tragic in this case - would delay the collision by a critical few seconds. This train appeared to still be going full speed or nearly so (and there's no audible braking sound in the videos I've seen until after the collision). If this train had been a few seconds later, it'd be a lot less dramatic on video. If it had been a few seconds earlier, it'd have been deadly. Seconds do matter.
While true on the aspect of giving time to the revisers, I’ve seen a Conrail demo where their loco hit a car at no more than 10 mph and nobody would have survived.
There are loads of You Tube videos demonstrated the destructive power of even a slow moving train.
2eng2efficient wrote:The videos of this event are absolutely insane, like something out of an action movie. It got my pulse up just watching it. The police were courageous and the pilot is lucky to be alive - they got him out with literally seconds to spare.
The second angle of the guy filming adjacent to the tracks is equally wild. Quite idiotically, this man is standing immediately down range from the fuselage, and it looks like he came very close to being decapitated by a part that flies in his direction after the train obliterates the plane.
https://amp.usatoday.com/amp/9155052002
777 wrote:One day I will die, but not today!
Amazing!
F9Animal wrote:I am also certain the train was at full emergency brakes at the time of impact.
Those officers saved that pilots life!
washingtonflyer wrote:smokeybandit wrote:Train tracks at the end of the runway. How common is that?
Welcome to the developed world.
There is a major rail line at the north end of the runway at CLT too.
FiscAutTecGarte wrote:That was an amazing display of self-sacrifice on the part of those officers rescuing that pilot. It made my morning to see it.
bennett123 wrote:One question that no one has asked yet.
Is it a write off?.
bennett123 wrote:One question that no one has asked yet.
Is it a write off?.
wjcandee wrote:Remarkable video. Very sad that the responses to the Tweet from LAPD are filled with such puerile and hateful comments. I'm triggered. I need a safe space now.
Also thinking that PD needs a more-robust way of communicating with train dispatchers, who could change signals or, if the train has passed the last signal before the crossing, instruct it by radio, which might have allowed it to slow or perhaps even stop. Here in NY, there's usually a railroad emergency number and location identifier posted by crossings. Don't know if they have that in Cali.
69bug wrote:I'm thinking that any tower that has railway tracks nearby should have a big red button that would red-light all traffic and alert the railway authorities...
Not a high cost item too.
bug
ER757 wrote:Took some serious cajones to keep working
wjcandee wrote:F9Animal wrote:I am also certain the train was at full emergency brakes at the time of impact.
Those officers saved that pilots life!
I absolutely defer to you on this. I have probably been on a half-dozen (or maybe a few more) pax trains when they dumped the air. There's little at first, then a smooth, somewhat rapid deceleration, then some jittering at the end. I actually had a trainman describe this to me as a young kid while I was sitting talking with him on a long-distance train, then not 30 minutes later that exact thing happened. Car at a crossing. Every time it happened after that, it was pretty-much the same. You hear the TOOSH! sound, then you wonder for a moment whether in fact that's what it was since nothing is happening, then you feel the brakes apply with increasing effect, then you come to a shaking stop. So that train may well have been in emergency when it passed the crossing, but there wasn't much obvious deceleration, which suggests that the application may have been made, as others have noted, when the crossing came into sight, which may have been very-shortly before impact.
musang wrote:I feel sure the driver braked as soon as visual contact was attained.