Providence Station Clock is Wrong (Again)

Arriving at the station much earlier than usual this morning I was locking up my bike when I heard an MBTA train dinging and roaring its way Northwards to Boston. Glancing up at the station clock I saw the time was 7:12, which was weird, since I thought the train before mine went at 7:15. Entering the station and turning to look at the new LED screens that have supplanted the old mechanical timetable board I saw that I was right: that was the 7:15 train, and it had left at 7:15.

The station clock is wrong. Still wrong from the last time I noticed it (when I politely asked the Amtrak staff to let somebody know the clock was wrong). Wrong again (Governor Chafee had to get involved to fix the clocks last time).

Why is this a problem in the age of ubiquitous network-updated timekeeping devices in our phones? Why indeed.

Clocks are nice in themselves, as an aesthetic part of the common environment, and they should also be useful. A clock which tells the wrong time is subversive of utility: it is anti-useful, worse than useless, especially in the context of a building containing precisely-timed means of getting to work. The worst case scenario is that the clock is a bit slow. If it was a little fast more people would be on time for their departure.

The railways, after all, are the original reason why accurate, universal timekeeping became important. Before the railways localities kept their own time, often based on the position of the sun. With the arrival of intercity railways it became important to keep time universally so that railway companies could accurately communicate to all stations the predicted arrival time of the train.

What a shabby state of affairs it is that a railway station clock be the purveyor of misleading times. Better that the station have no clock than to have a wrong clock.

What to do, then? I mean to find out who I need to persuade that it is important that the Providence Station clock be either right, or gone.