Search

On Friday 11/19, I had occasion to be at Olmsted Falls (which is the 1st community west of Berea on the NS (x-CR, PC, NYC mainline) and found all of the xgs in that town blocked by an intermodal train stopped on the controlled siding. The nearest available detours are Barrett Rd. in Berea and Fitch ...

Still no correction of the faulty timekeeping discussed previously. #29 (20th) westbound "Capitol Limited" disappeared before reaching PGH and was last reported 4' 40" late due to mechanical problems. Train showed returning to WAS and being cancelled. However, the problem was apparent...

Heard that WLE brought some passenger equipment into Brewster last week for use on some excursion runs.

Anybody have any information about this?

Received some off-line requests to continue current comments: HIGH-SPEED operations in Ohio continue as #30 (15th) eastbound "Capitol Limited" arrived at SKY 1' 26" before it departed TOL, at least according to Amtrak!!! Why wouldn't the computer reject such data automatically? Or doe...

Results for this period are: TOTAL TRAINS = 1222 ON TIME = 581 (48%) LATE = 641 (52%) AVERAGE DELAY = 41" Of the late trains" 56% were 29" or less late; 24% were 30" to 59" late; 13% were 1' to to' late; 6% were more than 2' late; and <1% had no arrival time shown. BY ROUTE,...

Super high-speed WARP 9 performance continues in Northern Ohio as #30 (8th) that departed CHI about 3'30" late account locomotive failure covered the 44-miles from Toledo to Sandusky so quickly that it arrived at SKY 2' 11" before it departed TOL, at least according to Amtrak!

Sample of recent delays at terminals or en route major stations for which no explanation was provided: #22 (31st) northbound "Texas Eagle" - 40" @ STL #306 (1st) - 15" @ STL #63 (1st) westbound "Maple Leaf" - 28" @ ALB #58 (1st) northbound "City of New Orleans...

On 10/31 on the STL Corridor:

#301 & #304 were annulled, and #21 "Texas Eagle" was 1' late Dp. CHI, but no explanations on the Amtrak Twitter site.

If these are state-funded trains, somebody from the paying states should be questioning Amtrak.

#30 (27th) eastbound "Capitol Limited" was so fast that it arrived in Sandusky 42" before it departed Toledo. It appears that nobody at Amtrak cares about the accuracy of the reported times, nor do they care about explaining the delays at various terminal points, such as: #49 (27th) w...

No ultra-high-speed performance this time around. However: #311 (25th) on the KCY Corridor lost 1' 08" between Independence and KCY, but no cause given; #19 (25th) southbound "Crescent" lost 5' 52" from Manassas to Culpepper, no cause given. Does anybody in the Amtrak senior mana...

A few notes from the performance of the 23rd and 24th: High Speed reigns on #30 (24th) "Capitol Limited" as 116 miles Sandusky to Alliance in 27" ='s 258 mph #306 on the STL Corridor lost 1' 55" SPI to LCN after a 35" late start fr om STL with no reason given #48 (23rd) &quo...

Once again #30 (22nd) eastbound "Capitol Limited" arrived at Sandusky 38" before it departed Toledo.

Makes one wonder just how screwed-up other Amtrak IT programs might be.

Looking at the schedule of #303 on the STL Corridor: #303 has 5' 35" timing for the 284 miles for an average speed of 50.8 mph. In the 1950's / 1960's the GM&O and WAB had 5' 10" timing for an average speed of 55 mph, not to mention better equipment and on-board food services. Sooooo, ...

Things seem to be slowing down for #30 eastbound "Capitol Limited" as the train of the 19th only averaged 105 mph from Sandusky to Alliance.

Obviously Amtrak has taken no corrective action for its reporting errors.

Let's hear it for #30 (19th) which was so fast that it arrived at Sandusky 1' 29" before it departed from Toledo.

I wonder if Amtrak uses the same computer program for their financials?