Fire at Grand Central

Below is a letter to the editor that I emailed to the New York Times regarding an incident I’ll never forget. It was never published. Thus, I’ve decided to share it on my new blog. For some background, I was taking an excursion to the (now defunct) Astor Pl. K-Mart because they had large vats of Folgers Coffee that nobody else had at the time. It was on a hot Sunday afternoon, around 3PM.

Sitting at the front of the last car, reading an interview with Allan Holdsworth in Guitar Player magazine (unequivocally the greatest guitar player of all time, past, present or future bar none), I was shivering from the air conditioner blasting right on me. Without any further ado, here’s the rest of the story…


13 September 1999

Dear Editor,

While reading your article about the fire at Grand Central Terminal I noted a discrepancy in the facts. The article stated erroneously that the fire occurred at the south end of the northbound platform. This is incorrect as the fire took place at the north end of the southbound platform. I know this because I was a passenger in the last car of a southbound #6 train, pulling into the station at the peak of the fire.

As we pulled into the station, I felt an intense blast of heat from the air conditioner ducts followed by flames sweeping over the train. In a moment, the car was engulfed by the flames as we passed by the fully involved storage room. Stopping only a few feet away from the fire, the doors opened, there was a slight panic as we exited the train and made our way towards the stairs.

There was no light, save for that shed by the flames. The smoke was dense, with a sickening odor of burning wood, mixed with a faint trace of the even more sickening, acrid odor of burning plastic, and breathing became increasingly labored as we searched for the turnstiles.

Looking back on it, I find myself wondering why we ever left the 51st Street station. Why was the existence of this fire not communicated to the engineer before we pulled into Grand Central? By the time we arrived, the station was already completely evacuated, except for those of us on the train. Since the platform was deserted by the time we pulled in, it was obvious that it was known there was a fire, long before my train arrived, probably long before we even left 51st Street.

Once we pulled in, the doors opened and we were left to our own devices. It is fortunate that this incident occurred on a quiet Sunday afternoon, rather than a packed rush hour, whereby the ensuing panic most surely would have led to serious injuries and fatalities. The fact that there were no serious injuries, or worse, was a matter of pure luck.

Clearly, the MTA is totally unprepared for any such potential disaster. The actions as well as inactions on that day were completely irresponsible, and demonstrated clearly that should such an event, or even worse situation, occur at the height of rush hour, we cannot trust the MTA to have any plans to expedite the safe evacuation of passengers trapped on the trains or stations.
I for one am appalled.

David Kahn

First post

Never has it occurred to me that I would ever write a blog post. Nevertheless, here I am, writing a blog post. Beginning with the assumption that nobody would likely ever see it, I initially considered the quality of its content irrelevant. Upon further consideration, I realized that someone might see this, thus it should at least be reasonably coherent.

With that being said, my next dilemma was the subject: just what should I write about? Suddenly, it dawned on me that writing about writing a first blog post, or any blog post for that matter, just might be the ticket. After all, who writes about such frivolities? Blog posts are frivolous, are they not? Yet, that is precisely what makes it a potentially intriguing topic. Thus, after much internal debate, I decided that it should at least pass muster with ENG101 scrutiny, sans citations if possible.

Following my usual practice of unloading a raw brain dump, to be later edited judiciously, my thoughts turned to how I might approach the questions surrounding creation of a blog post. There are of course the usual questions of what to write about, and how to organize and present it. However a couple of other, gnawing questions burned inside: why bother? And just what do I want to say? Answering the former question is easy, as the goal was originally learning how to code themes and plugins for WordPress, in hopes of securing gainful employment. Answering the former question was easy, the latter not so much.

To be sure, contemplating a first blog post can lead to brief fantasies of becoming a famous “influencer”, and receiving millions from advertisers seeking access to my enormous audience. Then reality hits home as I look up and around my rinky dink little hovel of an apartment and half dead laptop and lukewarm mug of coffee waiting for me to polish it off, or replace it with a fresh mugful. While I have much to say about numerous topics, with little thought needed, I have little to say about writing a blog post. It’s just not something I’m all that passionate about. Thus I have to actually think about it. Yet here I am, at the end of my fourth paragraph, wondering if I’ve said anything relevant, or even reasonably coherent.

It gives me a deeper appreciation and respect for professional writers, who are required to do this every day. Writers block, infamous and insidious lurks wherever and whenever one is facing a blank page or screen, be it paper, word processor, text editor, or for that matter, the WordPress blog post editor. Now I remember why I’ve embraced the raw brain dump approach. Without it, I’d never be able to write even one sentence.