I spent years in the yard
I spent years in the yard while PTC and T.O. were being "perfected" so I missed out on a lot that caused many of my peers to resent those tools. When you have to deal with the consequence of T.O. breaking your train in half on the side of a hill or PTC putting your key train in emergency multiple times requiring a walking inspection of both sides of the train each time, it's hard to think of the good. I didn't leave the comfort of the yard and a fixed schedule until after COVID-19 so I had a lot to relearn about running trains at track speed again. Some of it is like riding a bike and you just don't forget, but other things take time. I've seen T.O. do things with DP trains I didn't think could be done. You just have to know exactly where and when you can do it. Little insights like that are just another arrow in the quiver so to speak.
PTC giving you the stopping and warning distances can be helpful, but other times it feels like it's way too conservative, especially when you have to squeeze a 9000' train into a 9200' siding. PTC won't really let you move within a couple hundred feet of the signal unless you're under 1 mph. I had an even tighter fit than that recently where I had to get authority to pass the signal from the dispatcher so I could turn PTC off temporarily (actually, put PTC in Restricted Mode). I didn't pass the signal, I just had to get really close. Once I was stopped I gave the authority back and the train we met was able to get by.
I was in for a rude awakening when I came back to the road because I was used to running my territory before PTC and the signals and switches responded a lot quicker. You could make rolling meets a lot easier then. Since our run is long enough we aren't going to hit overtime the idea was you made your money when you took the call so best to get over the road a quick as possible. Well those days are over! You not only have to wait for the signal you can't even respond then because there's a delay between the signal you're staring at and the PTC monitor in the cab.
I was stopping a train at a red signal while another passed me and got down to 15 mph about a quarter mile from the signal. This was a light train and I had it easily under control. The signal goes clear so I immediately come out of dynamics. PTC senses the increased stopping distance and puts my train in emergency! I look at the monitor and PTC shows a red signal. I look at the actual signal and it's still clear. I recover the air, report the problem and we go on our way. Since then I don't react to the signal alone. I wait for the signal and PTC.
PTC has evolved to be a great tool, but it could be improved, especially in how it communicates a speed restriction ahead. For example, if you will be entering the siding ahead and stopping in the clear at the other end of the siding, PTC tells you that the next restriction is "AUTHORITY 40MPH" which is based on the signal indicating diverging approach. The turnout speed on that siding might be 25 mph and there might be a temporary 10 mph on the frog but PTC won't tell you that until after you've passed the diverging approach signal because the turnout is located 25 feet beyond the signal and the frog is another 100 feet or so beyond the switch points. As you pass the diverging approach signal PTC will say "NEXT RESTRICTION: TURNOUT 25MPH" and give the countdown distance as you close in on it then, "NEXT RESTRICTION: FORM A 10MPH" as you close in on the frog.
Now PTC won't let you exceed the stopping distance for those upcoming speed restrictions even though it's not telling you what they are. After all, the next restriction it sees is the signal, and the turnout 25 feet and the frog 125 feet past the signal aren't the "next restrictions" technically, even though to the engineer the 10 mph restriction is the one that matters.
So if you find yourself in the position of having overlooked the 10 mph on the frog and are coming toward the signal planning on hitting the switch at 25 mph PTC is going to start chirping at you that you're speeding but not tell you why. You think you're doing fine but you forgot about the 10 mph. Now is not the time to go rifling through your paperwork to figure out why PTC thinks you're speeding. It's time to get the train under control.
Now for a bit of context for those who don't railroad. If you run a red light on the street or get caught speeding 42 mph in a 30 mph zone you get a ticket or a court summons and you typically pay a fine. But unless you accumulate a bunch of these violations or some really egregious violations you'll continue to be able to operate a motor vehicle on the road without any difficulty other than being a little poorer.
That is not how it works on the railroad. If you pass a signal indicating stop without authority (run a red light) you are immediately pulled from service and decertified for a minimum of 15 days up to 30 days while the matter is investigated. You cannot work as an engineer or a conductor (also a position that requires FRA certification). Instead you can only work as a brakeman or a yard helper. Depending on the severity of the violation the carrier may move for dismissal. If you run another signal later on in your career the company will likely dismiss you.
Speeding is also much more serious on the railroad. If the prescribed speed is 30 mph you can't go any faster, though some allowance of 2-3 mph is made for speedometer accuracy. If you exceed the prescribed speed by 5 mph the conductor is required by rule to place the train in emergency. If the prescribed speed is exceeded by 10 mph or more both crew members will be decertified at a minimum and other discipline will be handed down up to dismissal.
So when we talk about speeding or running red lights it is far more serious on the railroad than it is on the highway.
How would anyone know if you run a red light or speed? The signal system will prompt the dispatcher if a block is shunted where no authority was given for that block. Speeding was easier to get away with before GPS and PTC because unless somebody was doing the math between any two signals there was no system in place to communicate in real time that a violation had occurred.
Enter "the tapes."
The tapes are an on-board record of the train's telemetry. Think of it like the "black box" recovered from a plane crash along with the cockpit voice recorder. Any movement of the throttle, setting or releasing the brakes, ringing the bell, sounding the horn, your speed, etc., is recorded on the tapes (probably been a long time since it was actually reels of magnetic tape, but then again we also call crossing signs whistle boards). "Pulling the tapes" used to be a manual process where the road foreman would have to come to the locomotive and manually download it. Those days are over.
Now the tapes can be pulled remotely and in real time. There are certain events that will trigger an automatic download of the tapes and if anything went bad on that trip you can expect to hear about it.
On my first day of engineer OJT I was asked if I knew what BNSF stood for. "Better not start a family?" I quipped. My engineer was not amused. "It means Better Not Set Fifteen. When you set fifteen pounds or more you flag the trip and anyone who screwed up along the way - the Illinois based engineer who blew the crossing too late or the Kansas based engineer who hit the slow order hot - those guys all just got decertified because you didn't handle the train properly." That was when the tapes would have to be physically downloaded from the locomotive. Now this process happens automatically in real time. There's no getting away with anything anymore.
Let me just point out that I'm not one who wants to "get away" with anything. I take this stuff very seriously and do my level best to keep the train under control even if it means running a couple miles per hour slower or stopping 500 feet from the signal instead of 400 feet. I will be paid a whole lot less if I'm decertified or unemployed. The vast majority of us out here are the same way. You don't succeed long on the railroad if you're trying to break rules, speed or run red blocks.