Amtrak, B-Movies, Web Development, and other nonsense

Tag: Trans-Bridge Lines

The Bus

This is part of a series of posts chronicling our difficult journey to the 2014 edition of B-Fest, the annual bad movie festival at Northwestern University in Evanston, Illinois.

I’m sitting on a bench at the Metropark train station in Iselin, New Jersey. It’s January 23. It’s very cold. I’m pondering how it came to this. Some form of cosmic retribution for the near-perfect runs on the Vermonter and Silver Star earlier in the month?

It started well enough, with Ken dropping us off at the Easton Bus Terminal a little before 8 AM. We planned to take the 8:10 Trans-Bridge Lines bus, which would deliver us to New York by 10:00, more than enough time to catch the 11:35 Northeast Regional (train 125) for Washington, D.C.

It went wrong almost immediately, as multiple crashes in the cold, snowy weather turned I-78 into a gigantic parking lot. By 10:20 or so we had reached Terminal A at Newark Airport (nearly an hour late), and the traffic situation into New York didn’t sound promising. Google Maps predicted an arrival in New York at 11:20-11:30, which was far too close for comfort.

If we misconnected in New York with 125 we were out of luck on the Amtrak front. 125 is the last train with a valid connection to the Capitol Limited, and the last train period scheduled to reach DC prior to the Capitol Limited‘s departure owing to weather-induced cancellations. If we arrived late into New York the only choice would be to rebook for the Lake Shore Limited, accepting the necessary repricing and likely unavailability of sleeping accommodations. I’ve documented at length why the Lake Shore Limited isn’t a desirable option.

The alternative was to bail out at Newark, ride the AirTrain out to the airport train station (on the Northeast Corridor), and catch our train south of New York. Using the last of my laptop’s battery I worked out a plan. We would get off at Newark, ride the AirTrain to station, and hop a New Jersey Transit train to Metropark in Iselin. As we walked through the terminal I called Amtrak and adjusted our itinerary to originate from Metropark instead of New York. We left the Trans-Bridge bus to its fate.

Featured image courtesy of Adam E. Moreira (Own work) [GFDL or CC-BY-SA-3.0], via Wikimedia Commons.

HEWEBNE: outbound

This coming Monday I’m giving at talk at HighEdWeb New England about collaborative development in open source, focusing on liberal arts colleges. If this were one of my movie reviews that would be the “A plot.” The “B plot” is that I’m taking the train to the conference, and that unusually for me it’ll be 100% new mileage.

The conference is Mount Holyoke but I’m taking the Vermonter from New York up to Brattleboro. There are two reasons for this. The first is that my friend who’s picking me up lives closer to Brattleboro than Amherst. The second is that this train will be rerouted to the west bank of the Connecticut River in a year or two, and I want to ride the old route before that happens. Again, I’m that guy.

The ride in from Easton to New York was uneventful. Trans-Bridge Lines does a good job. Its buses are comfortable (for 90 minutes anyway) and the free wifi gets the job done. I-78 was remarkably empty. The only hiccup was finding New York Penn overrun with mouth breathing collegians dressed in green. Sigh. Amtrak Police finally showed up with a bullhorn and cleared them out. Yay!

Today’s Vermonter has five Amfleet cars: four reserved coaches and a cafe/business class car. At the front is an EMD AEM-7, one of Amtrak’s venerable “toasters” now in its fourth decade of service. It brought the train up from Washington and will pull it to New Haven, where we’ll swap it out for a GE P42DC “Genesis” diesel locomotive. We have to do this since there’s no electrification north of New Haven. Lunch today consisted of a turkey panini (good), hummus plus pretzel bits (okay), and iced tea. I’m pleased to finally ride over the Hell Gate Bridge but it really is more impressive from the park below looking up.

Early into New Haven and the power change starts at once which means no head-end power (HEP). I think of this as a staple of American railroading, though very few passenger trains do it now. The long-distance trains which travel south from New York (Silver Star, Silver Meteor, Crescent, Palmetto) change engines in Washington. The Vermonter does here in New Haven. The Pennsylvanian does in Philadelphia. I think some of the upstate New York trains do in Albany (switching from dual-mode electro-diesel to straight up diesels). Fascinating to think about the long-haul diesels which run, essentially uninterrupted, for fifty hours on the Western trains.

I hope I don’t offend anyone (too much) when I opine that Connecticut, at least what I can see of it, is ugly. Admittedly March is an unkind month for viewing the outdoors when there’s no snow on the ground.

We hit our dwell stops (New Haven and Springfield) with plenty of time to spare. Amtrak’s issuing a faster timetable on Monday, and I’d say that’s reasonable. I’ve arrived or departed from Springfield numerous times over the years but this is the first time I’ve headed east. We go as far as Palmer, and then perform a thankfully rare “backup” maneuver. There’s no northeast/southwest connecting track at Palmer, so we have to make what amounts to a J-turn in railroading–crossing the connecting track, stopping, throwing a switch (manually, no less), then reversing direction. The re-route I mentioned earlier will eliminate this step.

Here’s some very crude text art illustrating what we’re doing:

            C
            \_ 
             \\_________________
A_____________\_________________\(E)______B
               \
                \D

A-B is the CSX main between Springfield and Boston. C-D is the New England Central Railroad. The direct intersection between the two has no switch. We pull past toward B to the switch at (E), then backup on to the second track which links up at C. It’s horribly slow and inefficient. You leave Springfield at 3:15 PM. By 3:45 PM you’re just getting down with this nonsense and heading north.

Amtrak’s obviously embarrassed about it. There’s a nice long warning about it over the PA, emphasizing that this is normal and planned. I think the only constituency who enjoys this are the railfans who gather since it’s such a great photo-op.

I’m now on the stretch that Amtrak will leave in a year or two. This New England Central RR track is rough; some stretches are worse even than CSX around Buffalo, which has always been my “gold standard” for an unpleasant ride. It makes no sense to rehabilitate it of course when Massachusetts and the Feds are fixing up the new, more direct, route. I don’t disagree with the logic at all. Still, damn. There’s some talk of new service over this route to link Amherst with New London. I don’t see it getting done without serious federal money, and there are other more pressing passenger rail projects.

As I submit this we’re fifteen minutes out from Brattleboro and dead on schedule. No better way to travel.

Amtweets?

I’m on the road today, heading back to Michigan for a friend’s wedding. This involves three different transit operations playing ball: Trans-Bridge Lines between Easton and the Port Authority Bus Terminal (PABT) in New York, the MTA between the PABT and Pennsylvania Station (Penn), and finally Amtrak from Penn to Kalamazoo, via Union Station in Chicago.

One of the minor pleasures of taking the bus from the valley to New York (and there aren’t many so you really can’t be choosy) is running along the Northeast Corridor near Jersey City. Today, a little bit after 11 AM, I spotted the Silver Star, just a few minutes into its 31-hour, 1500-mile run to Miami and points in between. I recognized it from the two Viewliner sleepers behind the HHP-8 locomotive (see this page for more on train identification). Pleased, I tweeted the following:

On the bus to NYC and just saw the @AMTRAK Silver Star go by. Too fast for a picture!

This drew a quick reply from Amtrak’s social media folks. I’ve found them to be pretty responsive…

@mackensen Very cool! We’re glad you got to see it 🙂 How’s your ride going?

Amused that I’d gotten them interested, I replied with the following:

@Amtrak not bad but we’re crawling through the Holland tunnel. Happily I’m on the Lake Shore Limited this evening.

That tweet went out from the tunnel, incidentally. I continue to be impressed with Verizon’s coverage. That last tweet drew an odd reply, ending our little colloquy:

@mackensen We are sorry for any delay, we hope to have you to your destination ASAP! We look forward to having you on board again later!

I’ve been thinking this one over. At first I was deeply confused, but I’m coming to realize that I never said whose bus I was on, although I don’t think Amtrak operates any Thruway services in New Jersey. Also, it probably comes naturally to Amtrak to apologize for service delays (*cough*), even ones it isn’t responsible for.

Anyway, thought I’d mention all this. It really can be fun to tweet at Amtrak and see what you get back. A couple months ago I was coming back from New Orleans and got help up by Norfolk Southern maintenance in northern Indiana. I started including @Amtrak in my tweets slagging away at NS and eventually drew a friendly reply.

From Amtrak, that is. Those bastards at NS never said a word.