A collision earlier this year involving two trains owned by the same company resulted in minor injuries to both engineers and the derailment of one locomotive and more than two dozen railcars.
The National Transportation Safety Board’s (NTSB) preliminary report into the incident reveals that a westbound CSX Transportation (CSX) freight train collided with an eastbound CSX freight train near Carey, Ohio at 5:08 a.m. on August. 12.
Garbage and fracking sand
The lead locomotive of one train and four railcars carrying trash were derailed on their side. Twenty-one railcars loaded with fracking sand derailed from the second train. Initial accident damage was estimated at $4.9 million.
Both train engineers were taken to a hospital for treatment of minor injuries and postaccident drug and alcohol testing.
Positive train control (PTC) – a system designed to prevent train-to-train collisions – had been disabled on the eastbound train after a system failure occurred previously while the train was en route to Garrett, Indiana.
The crew involved in the accident notified the CSX dispatcher of the disabled PTC system prior to departing Garrett and were given permission to proceed to Columbus where the system could be repaired.
According to the report:
CSX train movements on the Columbus Subdivision are governed by operating rules, timetable instructions, wayside signal indications, and enforced with a positive train control (PTC) system. The CSX dispatcher for the Columbus Subdivision, located in Jacksonville, Florida, coordinated train movements using the signal system. The subdivision was single main track territory with portions of multiple main track territory and passing sidings. The maximum authorized speed in the vicinity of the accident location was 50 mph. The westbound train tonnage required a speed restriction of 40 mph.
During postaccident interviews, the crew of the eastbound train said the wayside signals indicated as they approached control point (CP) Springs that the train would be diverged from the single main track onto main track 2. They stated they saw the westbound train approaching.
No response to flashing headlights
CP Springs on main track 1 and noted the locomotive headlight was on bright. The eastbound train engineer said that he flashed his headlight to indicate to the westbound train engineer to dim the locomotive headlight but received no response.
The PTC system was activated prior to departure. The crew’s first job assignment was to set out 30 empty cars in Carey. CSX instructions specify that for trains operating with active PTC, crews performing pickups, set offs, or other switching activities including shoving movements must: (1) Stop the train/locomotive; (2) Use restricted mode for the PTC system. In restricted mode, the PTC system allows train movement at restricted speed and no longer automatically stops the train before it can violate a red (stop) signal.
Train H70211 was still almost 2 miles long after the 30 empty cars were set out. The conductor, working at the rear of the train, planned to ride a railroad shuttle van to a nearby highway-rail grade crossing to board the lead locomotive and continue westbound to their next job assignment in Fostoria, Ohio. The engineer of train H70211 departed with the PTC system still in restricted mode and continued westbound for about 2 miles to CP Springs. Preliminary event recorder data indicated the train speed never exceeded 20 mph (upper limit threshold of CSX restricted speed rule). The train continued past the red signal at CP Springs and collided with the sixth railcar of the eastbound train W31411.
The NTSB investigation is ongoing. Investigative activities will focus on train crew distractions, crew resource management, and current railroad operating rules for PTC. Parties to the investigation include the Federal Railroad Administration; CSX Railroad; Brotherhood of Locomotive Engineers and Trainmen; Brotherhood of Railroad Signalmen; and International Association of Sheet Metal, Air, Rail, and Transportation Workers-Transportation Division.
The report did not contain a probably cause determination.
Report Abusive Comment