NJ Transit might as well not communicate at all
32 Comments »August 2nd, 2007 by ripper
I’m at a loss for words right about now. Say what you want about NJ Transit and how they blame Amtrak for everything under the sun that happens. I won’t complain about that anymore because I’ve done my share of complaining on this subject (Point fingers all you want…us commuters have one finger we’d like to point).
NJ Transit is a FUCKING disgrace. Period. A little harsh? Let me lay out the facts of tonight’s commute, shall I? You be the judge.
First off, let me just run a simple test. You’ll see why I need to do this in a few moments. I’m sending a test e-mail from my yahoo.com account to my transithell.com just to see how long it takes. Under 1 minute. OK. Benchmark set.
Here’s where it all started tonight:
Due to Amtrak signal problem, trains departing and arriving NYPS are subject to 10 - 15 minute delays.
Sent: 04:32 PM (Received at 4:41 PM)
I’m still at work at this point. Doesn’t at all seem that bad. Signal troubles these days are as common as Lindsay Lohan arrests. I got to Penn Station at 6:08 or so, just in time for my 6:13 train. As I walk down from the 7th Avenue entrance, I see the first board with the timetable and 5 trains on standby. This will be another fun night I think to myself. As I walk by the newer NJ Transit concourse, it looks like this picture (courtesy of RVL_Girl). See, here’s the funny thing. This was taken on Tuesday. See, I wasn’t kidding how common delays are. I mean seriously. Imagine there was an emergency?
So I continue on my way down to the old NJ Transit waiting area and go down the stairs. It’s just wall to wall people. No idea if there is air on in the place because it feels and smells like a 3rd world country.
Due to a disabled train in the tunnel, trains arriving into New York Penn Station are subject to 15 - 20 minute delays.
Sent: 06:04 PM (Received at 6:18 PM)
Ok, so was the first communication wrong in saying signal problems? Did the signal problems cause the disabled train? All I know is that disabled trains in tunnels is BAD news for us commuters. 2 tunnels. 1 out of service. You do the math. So here I am and there goes the 6:13 train. Cancelled.
Next up, the 6:34.
Update: Due to single tracking in the tunnel, trains arriving and departing NYPS are subject to 20 - 30 minute delays.
Sent: 06:22 PM (Received at 7:22 PM) - Are you seeing a pattern here?
No word on the cancelled train. There were others too. All I know is we are up to 30 minutes and seriously, my shirt was stuck to my back at this point.
Update: Due to single tracking in the tunnel, trains arriving and departing NYPS are subject to 30 - 40 minute delays.
Sent: 06:41 PM (Received at 7:38) – See these are useless because I’m not even getting these when they are needed.
Northeast Corridor #3973 (6:13pm from NYPS) Operating 25 minutes late near Secaucus.
Sent: 06:51 PM (Received at 7:38)
Huh?? The 6:13 train is 25 minutes late (getting out my calculator) puts us at 6:38. This was sent at 6:51. Either way, YOU ALREADY CANCELLED THE TRAIN like 40 minutes ago. Now I’m looking around for the candid cameras. Someone must be putting me on.
Northeast Corridor #3731 (6:32pm from NYPS) Operating 40 minutes late near Secaucus.
Sent: 06:53 PM (Received at 7:38)
Now I don’t even know what’s going on. All I know is I now have a decision in all of this fiasco. I can take the 6:32 or the 6:34. The 6:34 is the express train that would get me in sooner than the 6:34 (Yes, NJ Transit makes everything really complicated). Since the 6:13 was cancelled and the announcements in the station were only saying 10-15 minute delays, I figured that the 6:34 would be crowded but was still my best horse. The 6:32 is called (honestly, I have NO idea what time it is. I was about to have a heat stroke). I let the crowd rush to that train and I wait for the 6:34.
Northeast Corridor #3975 (6:34pm from NYPS) Cancelled, passengers to #3875 (6:47pm).
Sent: 07:17 PM (Received at 7:41)
Ripper, you asshole.
Update: Due to single tracking in the tunnel, trains arriving and departing NYPS are subject to 10 - 15 minute delays.
Sent: 07:22 PM (Received at 8:31)
It continues.
Northeast Corridor #3877 (7:13pm from NYPS) Operating 20 minutes late.
Sent: 07:49 PM (Received at 9:04)
I think I’m only subscribed to the NEC train messages. I can’t imagine what the other ones said. I’m sure they were just as comical because there was a bunch of trains cancelled. I had finally gotten on the 6:47 train that left at like 7:15 or something.
So, after all that, let’s recap what we’ve learned (outside of Amtrak being at fault for everything under the sun at NJ Transit):
1) NJ Transit communicates worse than if someone was trying to tell me the truth in Russian (for the record, I can’t speak Russian).
2) NJ Transit alerts are pretty damn useless because you don’t get them for like an hour after they send them which is like 20 minutes after the actual problem which is like 30 minutes after they cancel a train. (Yeah, I can’t even follow that either. Don’t bother going back. You’ll only hurt yourself).
3) After all this, yet again, nobody collected tickets on my train (I was on the 6:47, which left at like 7:15.
4) Someone who left work less than 2 hours before me got home before me. Big deal you say? Sure, he left before me. He lives in New Hampshire.
5) I have NO confidence that the employees of NJ Transit could handle an emergency.
Seriously. This was half the commute today. Thousands of people were yet again delayed for long periods of time tonight. Keep blaming Amtrak for signals and infrastructure. Why can’t you send e-mails? Why can’t you make announcements? Why can’t you get things right? Please? Just once. I’m begging someone to fix this.


















So then we hit 8:36 and the train fires up and pulls away. The conductor then tells everyone that they are on the 8:36 to NY Penn. I then look at NJ Transit’s website and find this:
There was an AP article in the media discussing the about prioritization between NJ Transit and Amtrak trains: