2015 Oxnard train derailment

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2015 Oxnard train derailment
Photograph of train similar to that involved in the accident
A Metrolink train similar to the one involved in the accident.
Date February 24, 2015
Time 5:44 a.m. local time (13:44 UTC)
Location Oxnard, California
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Country United States
Rail line Ventura County Line
Operator Metrolink
Type of incident Vehicle obstructing line
Cause Under investigation; Possible design flaw on cowcatcher
Statistics
Trains 1
Passengers 48
Crew 3
Deaths 1
Injuries 29

The 2015 Oxnard train derailment occurred on February 24, 2015 when a Metrolink passenger train collided with a truck on a grade crossing and derailed at Oxnard, California, United States. The train engineer died from his injuries a week later and 29 others were injured.

Background

An overpass had been planned for almost two decades for the Rice Avenue crossing where the accident eventually occurred. Funding, however, remained unavailable in Ventura County for the estimated $35 million grade separation project.[1]

Accident

Lua error in package.lua at line 80: module 'strict' not found. The accident occurred at 5:44 a.m. local time (13:44 UTC) when a passenger train collided with a 2005 Ford F-450 pick-up truck and trailer on the Rice Avenue grade crossing in Oxnard, California. The train derailed, with three cars falling onto their sides and a fourth remaining upright, as did the locomotive which was pushing the train from the rear.[2][3] The train was traveling from East Ventura to Los Angeles and was accelerating after leaving the Oxnard station 2 miles (3.2 km) away from the crash site.[4] It was traveling at 64 miles per hour (103 km/h) when the emergency brakes were applied[5] and had slowed to 56 miles per hour (90 km/h) when it hit the truck.[5] The train's usual cruising speed is 79 miles per hour (127 km/h);[6] it was traveling under that speed.[7][8] The train cars consisted of a Hyundai Rotem cab car #645, three Hyundai Rotem bi-level cars #206, #211 and #263, and an EMD F59PH diesel-electric locomotive #870 at the rear. All four cars derailed, with #263 remaining upright.[9] According to the train crew, the truck appeared to possibly have been on fire before the collision.[6] However, this was likely to have been the flashing headlights of the vehicle, which was facing the train, as the driver attempted to signal to the train crew that he was ahead of them. The train was being operated at the time by a student engineer with the train engineer in the control cab with him.[10] The truck driver is reported to have driven along the tracks having turned too early before the intersection at Fifth Street and then having gotten his wheels jammed in the tracks from which he was then unable to extricate it. The truck was 80 feet west of the intersection and facing the train when the accident occurred.[2][11][12]

There were 48 passengers and three crew on board the train.[13] Of those, 30 were injured.[14] Initially, 28 of the injured were taken to hospital; 20 were released and eight were admitted, four of them said to be in critical condition.[6][15] Later, two more passengers were transported to hospitals and released.[15] Victims were treated at the Community Memorial Hospital, Los Robles Hospital & Medical Center, St. John's Regional Medical Center, St. John's Pleasant Valley Hospital, and Ventura County Medical Center.[16]

The truck driver was Jose Alejandro Sanchez-Ramirez, 54, who did not speak English, and who had a previous DUI conviction in his home state of Arizona although there was no indication that he was intoxicated at the time of the accident and no charges of being intoxicated were ever brought against him.[17][18] Sanchez-Ramirez left the scene on foot following the accident, but was later taken into custody about a mile away. According to his attorney, the man was trying to summon help in a remote part of the county without a vehicle and with no guarantee anyone he found would be able to communicate with him.[19] When he finally encountered police officers, he handed them the cell phone on which he had been talking to his son so that his son could explain to the officers what had just happened to the train.[20] He was booked on suspicion of hit and run and held on $150,000 bail, but prosecutors later declined to file criminal charges against him and he was released two days later.[21][22] Sanchez was due back in court in May 2015.[23]

Aftermath

Metrolink trains between East Ventura and Moorpark were canceled. A bus service was provided for passengers traveling to these stations.[3] Local roads around the scene of the accident were closed.[4] Amtrak Pacific Surfliner service between Los Angeles and Goleta, that uses the same Union Pacific coast line, was also cancelled.[15]

The train engineer, Glenn Steele, 62, was one of the critically injured and died one week later.[24] After the accident, Steele experienced two cardiac arrests on Wednesday February 25, but lived after those events.[25] At the time of his death, Steele was the most senior engineer with Metrolink,[26] having spent half of his 42-year-long Amtrak career with Metrolink.[10][27] Steele died at Cedars-Sinai Medical Center early on March 3.[28] A resident of Homeland, California, Steele was a grandfather.[10]

In March 2015, two of those injured due to the crash sued the truck driver, and his employer, Harvest Management LLC.[29]

File:BNSF 5696 pulling Metrolink into East Ventura station 2016-03-25.jpg
BNSF 5696 pulling Metrolink in the aftermath of the derailment

As a result of the accident, Metrolink announced on September 3, 2015 that they will restrict use of the cab cars for at least a year as they will undergo a review of the safety features. Meanwhile, they will use BNSF Railway locomotives to add a second locomotive to each train set. A BNSF locomotive will be positioned in front of the cab car. The cab cars will remain in service as passenger coaches used elsewhere in a train's lineup of cars.[30][31]

On February 22, 2016, Jose Alejandro Sanchez-Ramirez was charged with manslaughter by Ventura County prosecutors.[32]

Investigations

The National Transportation Safety Board has launched an investigation into the accident.[14][19] A Go-team was dispatched to the scene.[33] The train was fitted with a forward-facing camera in the cab car.[2] The NTSB has verified that the forward-facing camera was recording data and the collision itself was recorded by the camera.[12] Although it was initially stated that the truck became stuck on the tracks, NTSB later clarified that it is unclear if the vehicle was stuck and that it was not a typical grade crossing incident where a vehicle is crossing the tracks and is stopped or struck before completing the crossing. The vehicle was not in the crossing nor between the crossing arms.[12]

The Federal Railroad Administration opened an investigation into the accident, the twelfth at the crossing in ten years. An average of eight passenger and 24 freight trains use the line in each direction each day.[3][34] A preliminary report was published on March 19, 2015.[9] A report later that year found that the cow-catcher and a coupler on the train had manufacturing flaws, although no conclusion was reported regarding their role in the crash.[35]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 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. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 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 Lua error in package.lua at line 80: module 'strict' not found.
  16. 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. Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 Lua error in package.lua at line 80: module 'strict' not found.
  20. 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.