Just came across this on Youtube.
No injuries, no hazardous materials.
Big insurance headache!
|
Just came across this on Youtube.
No injuries, no hazardous materials.
Big insurance headache!
Replies sorted oldest to newest
Wow...that guy needs to learn how to shoot video. It was so shaky, I couldn't watch it.
@Rich Melvin posted:Wow...that guy needs to learn how to shoot video. It was so shaky, I couldn't watch it.
Same here! Just terrible, also when did this "event" happen?
Looked like yesterday August 25th at one point.
Yea- the video is pretty poor. The audio of the dispatchers talking to the crews was interesting.
@Rich Melvin posted:Wow...that guy needs to learn how to shoot video. It was so shaky, I couldn't watch it.
It calms down at about a minute. I'm guessing it's cell phone video.
Rusty
Just because it is a cell phone video is no excuse for it being so shaky.
Every scene in this 765 video (except the Horseshoe Curve runby and the CVSR scenes at the end) was shot with my cell phone.
If I witnessed a three-train collision I would be shaking too!
@Rich Melvin posted:Just because it is a cell phone video is no excuse for it being so shaky.
Every scene in this 765 video (except the Horseshoe Curve runby and the CVSR scenes at the end) was shot with my cell phone.
Got a bit choked up by that last scene Rich! Can't ask for a better way to go out!
Bob
Oh boy.......there goes lumber prices !
@RSJB18 posted:Got a bit choked up by that last scene Rich! Can't ask for a better way to go out!
Thanks, Bob. Here's the full video of my last trip.
PTC major fail? Or was this in yard limits?
@Rich Melvin posted:Just because it is a cell phone video is no excuse for it being so shaky.
Every scene in this 765 video (except the Horseshoe Curve runby and the CVSR scenes at the end) was shot with my cell phone.
It can be when one tries to go full telephoto, which is where shaky-cam appears in the video. Unless I have something to brace myself on, it's difficult with my phone. The following photo is blurry because I was at full telephoto. At full telephoto, the image was bouncing all over my screen. The railroad was closed and I didn't want to trespass.
Plus, I'd be willing to bet this was a video of opportunity where the fella didn't have opportunity to calmly set up for ideal filming. As I said, it calms down after the 1 minute mark.
At least it's not vertical format...
Rusty
A knowledgeable videographer knows not to go to full telephoto in a grab shot, hand-held situation. It’s impossible for anyone to hand-hold a long lens telephoto shot. That’s what a solid set of sticks (a tripod) is for.
The only reason it calms down is because the guy went to using freeze (still) frames for the scanner audio.
It's an unfortunate mess. Everything in both directions is now stopped and the lines of stopped trains are getting longer. Injuries may have occurred. At the very least, good equipment has been seriously damaged.
Every time I see that there has been a collision or derailment, I am glad that I am retired. Somebody younger is going to be out there swatting mosquitoes, dealing with any injuries that may have occurred, interviewing crews, arranging for removal of equipment still on the rail, reporting findings, answering inquiries by numerous Division and System personnel with their hair on fire, as well as emergency responders, etc. I am at home, wearing a t-shirt and shorts, just finished drinking a cup of really good coffee, and I know that I will be able to attend the Amarillo Sod Poodles baseball game tonight, instead of wearing sweaty clothes and growing beard stubble at a derailment.
With PTC I don’t understand how this happened unless one or more trains involved was not using it because of software issues.
@mackb4 posted:With PTC I don’t understand how this happened unless one or more trains involved was not using it because of software issues.
Sure I can. Everyone logged in, yet in “restricted” mode
I know nothing about PTC - but in the description is this: For those wondering why PTC didn’t prevent this, CP 296 was running PTC exempt meaning they did not have PTC on while running the train.
David
Just to help put it in perspective...In the (shaky) view in the first moments of the video, we're looking roughly northwest towards downtown St.Paul and the wye just to the east of St. Paul Union Depot. The track going off to the left is CP's former Milwaukee Road line to Minneapolis, and the line going to the right is BNSF's line to Minneapolis. (The CP line goes south of downtown St.Paul, BNSF goes on the northside then turns south to join up with CP's line; they then run parallel in a joint operation to Hastings MN where they split - BNSF stays on the east bank of the Mississippi, CP crosses over to the west bank.)
Apparently a northbound and a southbound train were passing each other, and a third train ran a stop signal and kinda tried to wedge between them. The engine of the third train hit the northbound train, which derailed it into the southbound, knocking the car with lumber off the rails. Fortunately speeds around there are generally quite slow, maybe 10-20 mph.
@Lehigh Valley Railroad posted:Sure I can. Everyone logged in, yet in “restricted” mode
Never thought of that one .
Still yet the dispatcher could have seen this a coming if his track line was coding .
Access to this requires an OGR Forum Supporting Membership