20250924018699I

Incident · Minor damage

FAA incident report · Embraer EMB-145XR · Roanoke, VA · September 24, 2025

Date
September 24, 2025 · 21:17 local
Place
Roanoke, VA
Airport
Roanoke-Blacksburg Regional
Phase of flight
Landing: Touchdown
Operating rules
Air carrier (Part 121)
Operator
JJBA
Damage
Minor damage
Aircraft
N21129
NTSB investigation
NTSBDCA25LA339
Reported as
Embraer EMB-145XR
Reported engine
Rolls-Royce AE3007 series
People aboard
53
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
Pilot’s flight hours
2,478 total1,014 in this make and model208 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Commuteair ucaprivacy data omitted, a flight from iad, dulles airport to roa, Roanoke airport, landed on roa rwy 34 and overran the end of the runway into the emas (engineered material arresting system). During the final segment of the ILS approach to runway 34, the first officer observed that the aircraft was high on the PAPI (precision approach path indicator) crossing the runway threshold. After crossing the runway markings, the first officer called for a go around. The captain did not respond and continued the landing. When the aircraft floated further down the runway, the first officer called for a go around a second time. The captain again did not initiate a go around and continued the landing. When the aircraft touched down, the crew applied maximum braking and full thrust reversers. The aircraft overran the end of the runway and came to rest in the emas area. The landing numbers were calculated for a wet runway and runway condition code of 5.

As the FAA filed it

COMMUTEAIR UCA^PRIVACY DATA OMITTED^, A FLIGHT FROM IAD, DULLES AIRPORT TO ROA, ROANOKE AIRPORT, LANDED ON ROA RWY 34 AND OVERRAN THE END OF THE RUNWAY INTO THE EMAS (ENGINEERED MATERIAL ARRESTING SYSTEM). DURING THE FINAL SEGMENT OF THE ILS APPROACH TO RUNWAY 34, THE FIRST OFFICER OBSERVED THAT THE AIRCRAFT WAS HIGH ON THE PAPI (PRECISION APPROACH PATH INDICATOR) CROSSING THE RUNWAY THRESHOLD. AFTER CROSSING THE RUNWAY MARKINGS, THE FIRST OFFICER CALLED FOR A GO AROUND. THE CAPTAIN DID NOT RESPOND AND CONTINUED THE LANDING. WHEN THE AIRCRAFT FLOATED FURTHER DOWN THE RUNWAY, THE FIRST OFFICER CALLED FOR A GO AROUND A SECOND TIME. THE CAPTAIN AGAIN DID NOT INITIATE A GO AROUND AND CONTINUED THE LANDING. WHEN THE AIRCRAFT TOUCHED DOWN, THE CREW APPLIED MAXIMUM BRAKING AND FULL THRUST REVERSERS. THE AIRCRAFT OVERRAN THE END OF THE RUNWAY AND CAME TO REST IN THE EMAS AREA. THE LANDING NUMBERS WERE CALCULATED FOR A WET RUNWAY AND RUNWAY CONDITION CODE OF 5.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.