Subscribe

NTSB Determines Probable Cause for NJ Transit Collision

Figure 1. Aerial view of damaged train and portion of struck tree in their final positions.(Source: 6abc Action News.)
The National Transportation Safety Board (NTSB) has released the final report for its investigation of the Oct. 14, 2024, NJ Transit accident in which an Alstom employee was fatally injured when the train struck a tree that had fallen across the tracks near Florence, N.J.

What happened?

“On Oct. 14, 2024, about 5:59 a.m., an Alstom employee operating southbound NJ Transit train 207 was fatally injured when the train struck a tree that had fallen across the tracks of the River Line at milepost (MP) 24.53 near Florence, N.J. (see Figure 1, above). Train 207 was a light rail vehicle (LRV) consisting of two railcars with 41 passengers on board. During the collision, a tree branch penetrated the lead railcar’s forward windshield and struck the operator. Twenty-three passengers were transported to a local hospital with minor injuries. Alstom estimated damages to equipment to be about $194,000. At the time of the accident, visibility conditions were dark with the train’s headlights providing the only illumination, and the weather was 60°F with no precipitation.

“On the day of the accident, the operator reported for duty at 4:48 a.m. at an NJ Transit maintenance facility in Trenton, N.J. She started her scheduled trip from Hamilton Avenue Station at 5:47 a.m., operating train 207. This was the first train to operate on the River Line that day. About 5:55 a.m., the train departed Bordertown Station, the last station north of the accident area. According to event recorder data, the operator initiated an emergency braking application at 5:58:56 a.m. while rounding a right-hand curve north of the point of impact. The train was traveling 65 mph when the braking application began, and the train decelerated for several seconds before striking the tree. The train came to a stop about 880 feet past the estimated point of impact (see Figure 2, below).”

Figure 2. Satellite image of accident location. (Source: Google Earth.)

According to the final report (download below), which follows a preliminary report issued in November 2024, the NTSB says, “while on-scene, it identified abrasive transfer marks on the rails consistent with emergency braking starting near MP 24.61, or about 430 feet north of the point of impact. Because the head end of the train was about 90 feet from its rearmost axle, this corresponds to an emergency braking application beginning when the head end of the train was near MP 24.59, or about 340 feet from the point of impact. The marks ended at the point of impact.”

The NTSB conducted a partial reenactment of the accident at low speed under predawn lighting conditions (see Figure 3, below). During this reenactment, the fallen tree became visible to an approaching train operator about 350 feet north of the point of impact. “According to waivers NJ Transit filed with the Federal Railroad Administration (FRA) when obtaining approval to operate, on FRA-regulated track, the type of LRV involved in this collision, the headlights were designed to illuminate a person standing 500 feet away. Daylight observations of the scene found that the point of impact was visible from about 1,400 feet away.”

Figure 3. View from test train cab during reenactment.

Postaccident examinations of the train did not identify mechanical defects, according to the NTSB report. “Examination of the train’s brakes found normal wear patterns on contact surfaces, but damage to the train prevented a brake test and dynamic testing. Braking tests performed by the vehicle’s manufacturer in 2003 indicated the type of light rail vehicle involved in this collision had an emergency braking distance of 499 feet from 60 mph under ideal conditions. The manufacturer did not test braking performance above 60 mph.”

Analysis

The collision, NTSB says, “resulted from the operator having insufficient time and distance to stop the train after the tree became visible. The investigation did not find evidence of defects with the train or track, and the operator was not impaired by drugs or alcohol.

“Postaccident observations and the design specifications of the train’s headlights suggest that the fallen tree became visible when the train was 350–500 feet away. Daylight observations showed that even though the accident happened near a curve, a train approaching from the north, as this train did, would have had a sightline of about 1,400 feet to the fallen tree’s location. The 1,000-foot difference between these observations indicates that darkness and the reach of the train’s headlights were the factors limiting the visibility during the accident.

“Rail abrasions indicate that the operator initiated emergency braking—the appropriate response to a hazardous obstruction—when the train was about 340 feet from the tree. Given the train’s speed of 65 mph (about 95 feet per second), the operator applied the train’s brakes less than two seconds after seeing the tree. The operator’s actions were therefore correct and timely, and they did not contribute to the accident.

“Although available records did not include the train’s minimum braking distance at 65 mph, this distance would have exceeded the 499-foot braking distance expected at 60 mph under ideal conditions because braking distance increases with speed. The tree was therefore already within the train’s minimum stopping distance when the operator saw the tree, and the train retained enough speed at impact for a tree branch to penetrate the forward windshield and fatally strike the operator.

“The train traveled 880 feet after striking the tree and before coming to a stop. There were no marks on the rails after the point of impact consistent with an emergency braking application, which suggests that the train was applying less braking force after the collision. A postaccident inspection found no defects with the train’s brakes, but damage to the train prevented brake tests. The collision damage may have affected the train’s braking systems, but there was not enough evidence to determine exactly how.

“The arborist’s report found that the tree involved in this accident had decayed internally. The tree fell as a result of this decay, but there was no evidence of a specific event that caused the tree to fall when it did. Investigators on the scene did not see external decay or obvious indications that the tree was unhealthy, and it is therefore unlikely that Alstom’s regular track inspections and seasonal surveys could have identified the tree as a hazard.”

Probable Cause

The NTSB determines that the probable cause of NJ Transit train 207 striking a fallen tree, resulting in a tree branch piercing the front windshield and fatally injuring the train operator, “was the predawn low light conditions that prevented the operator from seeing the tree in time to stop the train.”

Lessons Learned

The investigation identified four cases of trains striking downed trees before this accident. These collisions, NTSB says, “were minor but indicated the presence of a risk that, on October 14, 2024, led to a fatal collision. This accident underscores the importance of incorporating all measurable hazards into system safety programs.”

Comprehensive safety oversight programs are required under federal regulations at 49 CFR Part 674. As a result of this accident, NJ Transit and Alstom completed a corrective action plan to remove tree hazards along the River Line, and the New Jersey Department of Transportation (NJDOT), as the state safety oversight agency, “will continue to monitor efforts to identify and remediate hazards along the River Line,” according to the NTSB.