Valhalla train crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Valhalla train crash
NTSB investigators survey the vehicles involved in the accident
NTSB investigators survey the vehicles involved in the accident
Date February 3, 2015
Time 6:30 p.m. EST (23:30 UTC)
Location Valhalla, New York
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Country United States
Rail line Harlem Line
Operator Metro-North Railroad
Type of incident Grade crossing collision
Cause Under investigation
Statistics
Trains 1
Passengers At least 650
Deaths 6
Injuries 15
Damage 2 train cars
1 automobile
$3.7 million

On the evening of February 3, 2015, a commuter train on Metro-North Railroad's Harlem Line struck a passenger car at a grade crossing near Valhalla, New York, United States, between the Valhalla and Mount Pleasant stations, killing six people and injuring fifteen others, including seven in "very serious condition." The crash was the deadliest in Metro-North's history, as well as the deadliest such crash in the United States since the June 2009 Washington Metro train collision had killed eight passengers and injured eighty.

The crash occurred after an earlier accident on the Taconic State Parkway, which parallels that section of track, had led to the road's closure in one direction. Drivers from the Taconic State Parkway sought alternate routes, one of which went through the grade crossing. The driver of an SUV was caught inside the crossing gate when it descended, wedging itself into the rear of her vehicle, apparently attempted to rectify the situation by crossing the tracks instead of backing up. She, along with five passengers on the train, died when her vehicle was struck by it. The impact tore loose more than 450 feet (140 m) of third rail; after piercing her car, it went into the front of the train, broken into sections.

Since grade-crossing accidents typically do not lead to fatalities on board the train, investigators from the National Transportation Safety Board (NTSB) were particularly interested in determining why the fatalities occurred. They believed that fuel from the SUV may have combined with sparks from the dislodged third rail to cause a fire on board the train. They were interested in finding out how the SUV driver got into the position she did in the first place; the detour caused by the earlier road accident may also have played a role.

Background

Bombardier M7A trainsets, similar to those forming the No. 659 train

At about 5:30 p.m., shortly before sunset on February 3, 2015, a vehicle traveling south along the Taconic State Parkway north of the hamlet of Valhalla in the town of Mount Pleasant, in central Westchester County north of New York City, struck another vehicle making a turn onto Lakeview Avenue from the northbound parkway. Responding emergency services closed both lanes of the southbound Taconic and one northbound lane. Drivers heading both directions left the parkway, seeking alternate routes back to it on local surface roads.[1]

At 5:44 p.m., Train 659 of Metro-North Railroad's Harlem Line, which provides commuter rail service over an 82-mile (132 km) route from New York City to Wassaic in northeastern Dutchess County, departed Grand Central Terminal in Manhattan, 26 miles (42 km) south of Valhalla. It was an express train of eight carriages,[2] formed by four Bombardier M7A electric multiple units, bound for Southeast in Putnam County,[lower-alpha 1] with Chappaqua its first scheduled stop.[3][4] At the controls was Stephen Smalls, a 32-year-old resident of Orange County and three-year Metro-North employee. He had been an engineer for nine months.[5]

The part of the parkway in Valhalla remained closed. One detour available to northbound traffic involved using Lakeview Avenue and turning at the large Kensico Cemetery, a short distance to the west. Lakeview Avenue crossed the two tracks using a grade crossing.[1] The next such crossing was Commerce Street, a lightly traveled local road to the north that intersects the tracks diagonally. It continues northwest through the cemetery for a quarter-mile (400 m), then turns north again down a slight rise back over another grade crossing to a signalized intersection with the parkway.[1] After a crash at the Commerce Street crossing in 1984 that had killed the driver of the van involved,[6] boom barriers had been installed.[7]

Accident

File:Valhalla train wreck site.jpg
The Commerce Street crossing in Valhalla where the wreck occurred, three months later

The parkway was still closed around 6:30 p.m., when a Mercedes-Benz ML350 SUV driven by Ellen Schaeffer Brody, 49, of Edgemont, went north on Commerce back towards the parkway.[8][9] Brody left work in Chappaqua at 6 p.m. and was going to meet a friend in Scarsdale.[10] Behind her was a vehicle driven by Rick Hope of Yorktown Heights, returning home from his job in White Plains.[11][12]

At the grade crossing, Train 659 was approaching on the western track. The crossing gates descended, warning lights began flashing and according to Hope, bells rang.[lower-alpha 2] Hope says Brody's SUV was in front of the gate as it descended, but not on the tracks. Had she simply remained where she was, he speculated, the passing train would have at most struck a glancing blow, perhaps damaging only the SUV's front bumper.[12]

The crossing gate struck the top of Brody's SUV before sliding down its rear and becoming stuck. Hope backed up to give her room to do the same. He instead saw Brody get out and walk to the rear, apparently trying to free it. "What struck me was how calm she was—she didn't seem to be panicking, or in a hurry at all, even though the gate was down," he said later. "She wasn't in a hurry at all, but she had to have known that a train was coming."[12] Brody looked at him, and he motioned to her to come back in his direction, although he allows that she may not have seen him due to the glare from his headlights. Brody then returned to her vehicle and, according to Hope, seemed to pause as if she was adjusting her seat belt. The train was getting closer and the situation more urgent. "The thing's dinging,[lower-alpha 3] red lights are flashing, it's going off," he said. "I just knew she was going to back up—never in my wildest dreams did I think she'd go forward."[11]

Instead, Brody did move forward, roughly 30 seconds after the gate came down on her car, investigators determined later.[14] The train, traveling at 58 miles per hour (93 km/h) before the accident,[15] struck the SUV on its passenger side. "There was a terrible crunching sound, and just like that, the car was gone," Hope said. "Disappeared. It happened instantly. There's no way she could have known what hit her."[12] The train was traveling at 49 miles per hour (79 km/h) when it struck the car.[15]

In the train's front car, Chris Gross was suddenly thrown out of his seat. "I heard a loud bang and a lot of screaming," he recalled. Flames were within a foot of his face; another passenger got the emergency exit open and pulled him out. The five passengers who died were all sitting near him, he claimed. Jamie Wallace, in the second car, said that passengers there initially tried to come to the aid of those in the front car, but "we could not get the head car doors open for some reason, it was jammed." After failed efforts to break the door open, "[a] number of us started smelling fumes from the car, the fuel, and we said, 'You know what, we need to get out.'"[16]

Smalls applied the emergency brakes as soon as he saw the vehicle. After the crash, he went back into the burning train several times to rescue passengers. "He did everything he could," said Anthony Bottalico, head of Association of Commuter Rail Employees, the labor union which represents Metro-North workers. Despite that, the train knocked Brody's SUV 1,000 feet (300 m) up the tracks, which dislodged more than 450 feet (140 m) of the third rail,[17] breaking it into 13 39-foot (12 m) segments,[18] most of which accumulated in the front car's passenger compartment, and then into the second car.[11] The New York Daily News reported that injuries from them were responsible for most of the deaths on the train.[19]

Passengers further back in the train heard explosions. "The thing that precipitated people really starting to freak out and break the glass and open the door was there was a loud 'bam,' explosion-type thing," said Fred Buonocore, who was in the fourth car. "And once we jumped off the side, there was another explosion to a lesser degree." At the very rear, passengers said they felt only a small jolt. "It felt not even like a short stop, and then the train just completely stopped," said Neil Rader, who was sitting in the middle-back of the train.[16][20]

Numerous law enforcement agencies, including the MTA Police, and fire/EMS departments in the area responded. This was declared a Mass Casualty Incident, otherwise known as MCI, by the fire and EMS departments on scene at the time.[citation needed]

Aftermath

File:Passengers boarding Metro-North shuttle bus after Valhalla train crash.jpg
Passengers at Pleasantville boarding a shuttle bus to North White Plains the morning after the accident

Brody died, as did five passengers aboard the train.[20][21] The lead car caught fire[20] and was eventually destroyed.[8] Damage was estimated at $3.7 million.[15] Passengers who escaped or were evacuated and were not injured were taken to a nearby climbing gym (called The Cliffs), where they were able to stay warm until buses arrived.[16] Nine passengers were taken to Westchester Medical Center, with one of them in very serious condition.[22][11][23] A police helicopter with thermal imaging equipment scanned the cemetery in search of survivors who might have wandered away from the scene and collapsed into the snow, but found none.[24] There were a total of six deaths and fifteen injuries.[25]

Shortly after and as a result of the crash, Harlem Line service was suspended between Pleasantville and North White Plains.[26][27] On the afternoon of February 4, the day after the incident, the NTSB gave permission for Metro-North crews to clear the site. Overnight on February 4, a 100-member crew cleared the vehicles, using a high-rail crane to remove the SUV. The train's locomotive was towed to Metro-North's North White Plains yard, and then workers proceeded to repair the 450 feet of third rail. Metro-North service resumed on the morning of February 5, with delays of fifteen minutes for trains to slow down as they passed the site of the accident.[28] Commerce Street reopened to car traffic on the afternoon of February 5.[29]

At that point in 2015, it was the deadliest passenger train crash in the United States since the 2009 Washington Metro train collision, which killed nine people and injured eighty others.[30] It is also the deadliest crash in Metro-North's history[11] and is only the second Metro-North train incident to result in passenger fatalities, after the derailment 14 months earlier on the railroad's Hudson Line that killed four people.[31]

Fatalities

All but one of the victims were Westchester residents. All of the dead train passengers worked in Manhattan; three of them worked in finance, and two of them at the same firm.

The victims were:

Investigation

File:Metro North accident at Valhalla, NY - 2.jpg
The train involved in the accident at a maintenance facility for further examination

On the night of the accident, the NTSB opened an investigation into the accident, and dispatched a go-team to the site.[39] They planned to stay for a week, collecting evidence and interviewing witnesses.[40]

Investigators said they were particularly interested in one of the crash's unusual aspects. "We do have grade-crossing accidents, and most of the time it's fatal for occupants of the vehicles, and not for train passengers," Robert Sumwalt of the NTSB told The Journal News, Westchester County's main daily newspaper. "We intend to find out what makes this accident different."[40] George Bibel, author of Train Wreck: The Forensics of Rail Disasters, agreed that this is uncommon. "Normally you'd expect the train to sweep the car off the tracks," he said. However, there were other exceptions to this pattern, such as the 2005 Glendale train crash in Southern California, at that time the deadliest in the history of Metrolink, where an SUV abandoned at a grade crossing by a driver who decided not to commit suicide after all derailed the train that struck it, killing 11.[41]

Another unusual aspect was the configuration of the third rail. Unlike other American commuter-rail agencies that operate trains powered by third rails, which have a contact shoe on top of their third rail, Metro-North trains' contact shoes draws current from the bottom of the third rail during operation. The Metro-North's under-running third rails are designed in order to prevent ice from building up on top during winter months and reduce the possibility of inadvertent contact with the high-voltage rail; as a consequence, the Metro-North third rails are much safer than the traditional over-running third rails.[18] To facilitate this, the ends of the third rails adjacent to grade crossings have a slight upturn.[41] "This has never happened before, and this is a rare configuration of a third rail," U.S. Senator Charles Schumer, said. "Do those two add up to the explanation for this terrible, terrible tragedy? Very possibly." But Steve Ditmeyer, a former Federal Railroad Administration official, told the Associated Press it would be impossible to be sure that an under-running shoe lifted the rail without also doing tests to see if the same thing would happen in the more common over-running configuration.[18]

They theorized that the fire aboard the train might have been caused by gasoline from the SUV, ignited by a spark from the third rail and the force of impact. However, said Sumwalt, "the big question everyone wants to know is: Why was this vehicle in the crossing?" The NTSB team believed the crossing was functioning properly, but was aware also that the earlier accident on the Taconic had led to more traffic through it. "We want to understand what, if any, effect that detour had in setting up this accident."[40]

Some area residents suggested the crossing itself was the problem. Lance Sexton, a Manhattan resident who commutes to the area to assemble electronic equipment, described using it to The New York Times: "[C]oming down the hill of the cemetery, you have to put the brakes on earlier ... There's a bank there that always collects water, making it even more dangerous." He also said he and his coworkers often complained about how quickly the train came after the gates went down, gates which had been installed after a 1984 crash killed a van driver. "How safe is that crossing—for this to happen again?" that victim's sister asked the newspaper.[42] While the crossing had undergone upgrades in recent years, including brighter lights and an additional sign warning passing drivers not to stop on the tracks, in 2009 another upgrade, which would have added a sign with flashing lights 100–200 feet (30–61 m) up the road west of the tracks was not installed. "It's way too early to be guessing about what could have or couldn't have made a difference," said a spokesman for the New York State Department of Transportation.[18]

Three days later, the NTSB investigators announced that all safety features at the crossing—the gate, the train's horn, and a sign 65 feet (20 m) away warning drivers not to stop on the tracks—were in good working order and had functioned properly at the time of the accident. The gates had gone down 39 seconds before the train reached the crossing, they said, meaning Brody had spent almost that amount of time inside them. They would next focus on whether she was familiar with the road and whether she was using a phone at the time.[14]

The NTSB released a preliminary report into the accident on February 23, 2015.[15]

Litigation

Three months after the accident, the MTA received 34 separate notices of claim, the first step toward filing a lawsuit, from victims of the crash and their families, on the very last day possible. Most were from passengers injured or killed, and one was from the family of Ellen Brody, the driver of the SUV struck by the train. All claimed negligence by the agency contributed to the crash.[43]

Philip Russotti, lawyer for the Brody family, called the crossing "an accident waiting to happen." The claim cited a "confluence of circumstances" that led to Ellen Brody's presence on the tracks at that time. The approach to the crossing lacked the lights and signage required by federal regulations that would have given her enough advance notice. In 2009, it noted, money was allocated for additional safeguards at the crossing that would have met those standards, but the equipment was never installed.[43]

A railroad substation building along the tracks also blocked the train from view as she reached it, the claim also said. Ideally, it concluded, the crossing was so potentially hazardous it should have been closed a long time ago. "This horrific accident was not the fault of Ellen Brody," Russotti said. In addition to the MTA, the claim said the Brodys intended to sue the town and the county. A lawyer for the MTA declined to comment.[43]

New York personal injury attorney Howard Hershenhorn filed a negligence lawsuit for Robert Dirks' wife Christine Ueda. It names Metro North, the train engineer Steven Smalls Jr., Westchester County and the town of Mount Pleasant among the defendants. The complaint lists bad visibility, poorly designed third rail, local official negligence and unsafe speed among the reasons for the defendants' alleged negligence. "We are going to focus on the operation of the train and the train operator and his failure to recognize and stop the train," Hershenhorn said. "We have spoken with qualified experts who have told us that these are very strong areas."[44]

See also

Notes

  1. The line, from Grand Central Terminal to Southeast Station, is electrified by third rail. Electrification ends at that station; only diesel trains can continue on the Harlem Line to Wassaic.
  2. However, this could not have occurred since bells are only required for pedestrian crossings, and as Commerce Street is not considered one its signals do not have bells.[13]
  3. See note b, above

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 11.4 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 12.3 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 15.3 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. 20.0 20.1 20.2 Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 40.2 Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 43.2 Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.

External links