I was ready to write a humor based article on how you can gauge the importance of a subway service announcement from how easy it is to understand it — the more important the announcement, the more likely that it will be garbled and impossible to understand. This is despite the fact that many service announcements are pre-recorded and have been for awhile.
The introduction of automated, pre-recorded service advisories, voiced by Bloomberg Radio personalities, in the new R142 trains that have been running on IRT lines since 2000 are certainly an improvement. But even in those trains, sudden changes in schedules require the interjection of live announcements, often susceptible to the same issues mentioned above that other cars and station PA systems face. Although most planned service changes are announced with signs posted in stations, trains are regularly delayed or diverted from their normal routes for a variety of reasons, and in these instances the only way for passengers to know what is happening is to listen to the announcements. To make things worse, some stations – a whopping 35% of them as recently as 2005 – still don’t have PA systems installed.
Since my office moved to Brooklyn recently, I have been taking the F train to the York Street station, which is the first station stop in Brooklyn. That’s an additional 8 or so stops from where my office was when it was in Midtown Manhattan.
On the way home recently, I was reading a book and comfortably sat. The train stopped at the Queensbridge Plaza. An announcer came on the communication system and told us that we would need to get off the train and wait for another train, as the train we were on would be going back to Manhattan.
Five minutes passed, and the train was still there. Another announcement came and said that there would be no Queens service from the station, and that we should take the train across the platform back to Manhattan, transfer to an R train, and then come back to Queens that way.
I joined everyone in unhappily going over to the other side of the platform, crossing an over bridge, where we got on the train and waited to go back to Manhattan. Five more minutes passed and I thought about just going outside and taking a taxi. It was Friday at 5:45 PM, and I needed to be home before seven due to the quickly approaching holy Sabbath, which precludes me from being on a train during it.
Suddenly, another barely understandable announcement made itself somewhat heard. The gist of the message was that they made a mistake, and that the train on the other side of the tracks would be going to Queens after all. The same train, that is, that was never sent back to Manhattan and where I had a perfectly good and comfortable seat.
There was a rush to get back to the other train — nearly everyone on the train went to the other train. On the ride back to Kew Gardens, there was an announcement made about there being “train traffic ahead of us” before every stop, making the train delay even further. How could there have been train traffic ahead of us when we were on one line and had not gone anywhere for about fifteen or so minutes? I finally got home about half an hour later than I should have been.
There are so many questions I have that will likely remain unanswered. Why did the announcers feel they had to send back the train? Why did they end service to Queens at the station only to reverse this decision five minutes later? Sometimes even a mumbled semi-coherent piece of information is better than no information at all.