Today's Acela - #2109

Ok, there are some things that just puzzle me. If you check Amtrak’s train status report today, #2109, the 8 a.m. departure out of Penn Station (NYP) , left an hour late. Yet it is projected to pull into Baltimore (BAL) on time. There is NOT an hour of fat in that schedule, is there? I rode it last week and I don’t know how we could have run much faster.

East Coast posters, help me out here.

First, the Acela trainset is back on train #2109, but that probably isn’t enough to make up the hour on the schedule. The website will probably be updated closer to the train’s arrival time. (10:12AM Eastern Time by the schedule) There are only 4 scheduled stops on this train.

OK, according to Amtrak, the Acele 2109 left NYP an hour late this morning and arrived in Baltimore (BAL) 6 minutes late. I still find that hard to believe that the train made up 54 minutes in that amount of time.

Hmmm, that’s curious. Says it left New York at 9:00 AM, then arrived 30th Street at 9:15 AM. That’s a fast trip for 91 miles…

Train show OT at PHL. I’d question the hour late departure out of NYP. I’ll bet that’s wrong.

I would also be skeptical of that departure and arrival report for Amtrak Acela Express 2109 since Amtrak’s web-site time table for the Northeast Corridor has a note to the effect that work on the Susquehanna River Bridge from July 5 through August 19 could delay trains by 5 - 10 minutes. I was out at Halethorpe, MD (~ 8 miles South of Baltimore) emptying my cameras ,and breaking in a new digital DVD camcorder, and I noticed all of the trains were running close to on-time.