[4K] Ashland VA 12.30.23: When The Lights Go Down, Part 2

[@Knards]

Nice to see parts of Ashland we cant see due to fixed cams on VRF site.

[@unclerudy9797]

On the VRF Railcam every morning ! Thanks for Posting !

[@FastFlyingVirginian]

You're welcome, glad you enjoyed it! The morning angles around the station are nice.

[@gusfring9895]

I was out picking up grocery and pharmacy orders that day and since it was quite cold outside I decided to watch trains for a while. I heard 195 clear the Glen Allen defect detector while at Kroger, gave it up as missed, and continued to CVS. The first thing I saw was M422's power consist, noting the 2 CN units, pulling to the north end of track 1 Advance, switching to track 2, and then backing down to the consist at NA, while waiting in line at the CVS drive-thru. I then went to my usual location at the Hermitage Rd. grade crossing just north of the Amtrak station. Strangely, 195 had not passed, and all the southbound signals at GN were red. I heard the E750 and M422 crews talking to the dispatchers and ACCA yardmaster, so I knew we had 3 northbounds in addition to 195 and 91, but was puzzled by the sea of red down by the station. There was a huge delay at RVR that, with hindsight, must have been a signal problem because they weren't using track 3 between NA and GN. I never saw or heard any maintenance personnel on the scanner, and the dispatchers never mentioned there was a problem, which is unusual. I also heard the Amtrak crews make some comments that indicated they had not been informed of the nature of the delay, or which trains they were holding for. I thought it was because of an inexperienced holiday relief dispatcher on the FB desk. I've witnessed that phenomenon on a couple of other occasions. As it was, they ran the E750, an estimated 10,000 feet long, up track 4 through the Amtrak station, while trains 195 and 91 passed me at restricted speed and stopped at the GN signal on track 4, with 91's baggage car fouling the track 3 turnout. The coal train crossed over to track 2 at GN and proceeded north. Then 124 came north on 4, worked the station, and followed the same routing after departing Richmond. Meanwhile, L134 was stopped on track 3 at Lakeside waiting for the congestion to clear. After a significant delay, 195 arrived and departed RVR, while 91 pulled in just behind 195, and L134 was brought down track 4 and stopped at GN. I checked the transitdocs.com map after 91 departed; it was nearly on time at Fredericksburg, but almost an hour late once it got out of town. Same for 195. M422 apparently had to double the train on another track in the yard; it pulled north to the north Lakeside signal, stopped, and then backed partway down, blocking the crossing (and my view of 53) for quite a while. I wanted to get a 2nd look at that switcher because I had not seen it from my earlier vantage point at CVS; coincidentally, the Belvedere and Delaware River RR was featured in an article in the "Shortlines" special issue from Kalmbach Publishing, which I had finished reading only days before. Unfortunately, M22 didn't reverse far enough to bring the switcher back into view. I was there longer than planned and started to worry about the frozen items I purchased, so I called it a day at that point. The moral is, don't pass up chances to get trackside because you never know what might happen. What was a normal sequence of events in Ashland turned into a total cluster-foxtrot in Richmond.

[@FastFlyingVirginian]

I used to hear advice from railfan photogs to always carry a camera. That used to mean stashing one in your car, but nowadays technology allows us to carry a perfectly capable cam on our smartphones.

[@robc.5745]

A nice looking station.

[@FastFlyingVirginian]

May we all look as good at 100 years old.