Blue Note Employee Loses Her Legs After Being Hit by a Subway Car…

Screen shot 2014-03-05 at 2.29.11 PM
  • Save

Teena Katz, a financial analyst at Blue Note Records, lost both of her legs after being run over by a subway car.

Katz and her family need assistance so they can afford prosthetics, medical bills, and related expenses.

According to New York Daily News, Teena was headed home on December 26th, 2013, when the incident occurred.  While in Grand Central Station she began to feel light-headed. Next thing she knew she was waking up on the track bed.  The train had severed her legs.  Surprisingly, Teena opened her eyes and apologized to first responders for delaying the train.

Katz has just been released from the hospital.  During the stay, she underwent through 12 surgeries.

If you want to make a financial contribution to Teena you can do so via her blog.  Money will go towards “medical bills, prosthetics, refitting her home to be handi-abled, pimping her ride to be handi-abled, and more.”

6 Responses

  1. Willis

    Wow, sad news. I don’t know her, but she sounds like a good person. Help is on the way.

  2. River Waters

    I went to the blog and got this error:

    Internal Server Error. Please contact a server administrator.

    What gives? I want to donate.

  3. Paul Resnikoff

    What a depressing story, not only for Teena but also for the train conductor and others involved. We can only wish a speedy recovery, and give thanks for our own health. Accidents happen, and sometimes, very serious accidents happen.

    When I visited Seoul in 2012, I noticed the stations had large glass (or plexi-glass) protectors between the passengers and trains. This type of accident could never happen there, and intentional suicides or horrific incidents involving pushed passengers would become history. Actually, I’m surprised that more problems don’t occur given the heavy crowds and often narrow platforms in New York’s subway stations.

  4. AnAmusedGeek

    I actually sent an email to the tech contact listed on the whois record yesterday. The response indicated they were aware of the problem and (frantically) trying to fix it. Unfortunately, it still seems to be down.