# NTSB DCA25LA339: Embraer EMB-145XR, N21129, Roanoke, VA, September 25, 2025 - Type: NTSB incident investigation - Classification: Incident · No injuries · Class 3 · Limited · Preliminary report - Date: September 24, 2025, 21:17 local (Sep 25, 2025, 01:17 UTC) - Place: Roanoke, VA · On Airport, Pinned to EMAS location - Coordinates: 37.334762, -79.965094 - Nearby events: https://openairdocs.org/map.md?lat=37.3348&lon=-79.9651&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Landing area overshoot](https://openairdocs.org/ntsb-events/380) - Highest injury: No injuries - Injuries: 53 uninjured - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Major Investigations Division - Parties: Embraer, Brazil CENIPA, FAA AVP-110, ALPA National, CommuteAir MD Safety, ALPA - NTSB case key (mKey): 201709 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DCA25LA339 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201709/pdf - Page: https://openairdocs.org/ntsb/DCA25LA339 ## Preliminary report On September 24, 2025, at 2117 eastern daylight time (EDT), CommuteAir (dba United Express flight 4339), Embraer EMB-145XR, N21129, experienced a runway excursion while landing at Roanoke-Blacksburg Regional Airport (ROA), Roanoke, Virginia (VA). The airplane overran the end of runway 34 and came to rest in the engineered materials arresting system (EMAS). There were no injuries to the 3 crew and 50 passengers onboard and there was no damage to the airplane. The scheduled domestic passenger flight was operating under the provisions of Title 14 Code of Federal Regulations Part 121 from Washington Dulles International Airport (IAD), Dulles, VA to ROA. According to the flight crew, this was the second leg of day four, of a four-day rotation, and the first leg on the incident airplane. Prior to departure, the airplane had to be deplaned twice for maintenance related anomalies. After boarding for a third time, the flight crew reviewed the weather and briefed the thunderstorms approaching ROA. The airplane pushed back approximately two and a half hours after the scheduled departure time. En route, the flight crew reviewed the Automatic Terminal Information Services (ATIS) weather information for ROA. The ATIS reported calm winds, no precipitation, a cloud ceiling of 15,000 feet, and that runway 6 was in use. The captain, pilot flying, briefed the localizer approach to runway 6. The first officer (FO), pilot monitoring, suggested reviewing the landing performance details for a wet runway, or a runway condition code (RCC) of 5, but the captain declined due to the ATIS not reporting precipitation. During descent, the flight crew checked in with approach control and was informed of precipitation along the approach path to runway 6 and that other aircraft were using runway 34 for landing. The captain requested the FO set up for the instrument landing system (ILS) approach to runway 34 and to brief the approach. The FO set up the ILS runway 34 approach, briefed the approach changes, and monitored the weather radar. Figure 1. Jeppesen instrument approach plate for ILS runway 34 approach. After turning on final approach, the flight crew observed the runway and heard the previous landing aircraft report marginal visibility and bumpy conditions. During the approach, the rain intensity increased, and the captain requested that the FO run the performance calculation for landing on a wet runway with a RCC of 5. The FO ran the performance calculations and determined that they would have a margin of approximately 200 feet more than was required, without thrust reverser usage. The captain briefed the go-around procedures and that they would divert to Piedmont Triad International Airport (GSO), Greensboro, North Carolina if they executed a go-around. On short final, the rain intensity increased, and the captain requested windshield wipers at high. As the airplane descended below 500 feet, the FO observed that they were high on the precision approach path indicator(PAPI) and then observed the captain correcting the flight path, but recalled they were still high as the airplane crossed the threshold. After crossing the runway markings, the FO called for a go-around, but the captain continued. About halfway down the runway, the FO called for a go-around a second time, but the captain continued. The airplane touched down and the flight crew applied maximum braking and deployed the engine thrust reversers. The airplane overran the end of the runway and came to rest in the EMAS. The FO attempted to communicate with air traffic control (ATC), but the communications button had disengaged. After engaging the communications button, the FO coordinated with ATC and contacted the flight attendant (FA). The FA verified that there were no injuries. The flight crew completed the emergency evacuation checklist and prepared for an evacuation. Airport rescue firefighting (ARFF) personnel boarded the airplane and assisted with evacuating passengers down a ladder. Figure 2. Airplane main landing gear witness marks in the EMAS at ROA. (Source: ROA) As part of the investigative process, the NTSB invited the qualified parties to participate in the investigation. These included the Federal Aviation Administration, CommuteAir, and the Air Line Pilots Association. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Aeronautical Accidents Investigation and Prevention Center of Brazil, the State of Manufacture for the airplane, was appointed to support the investigation with Embraer as their technical advisor. The flight data and cockpit voice recorder were sent to the NTSB Vehicle Recorder Laboratory in Washington, DC. The following NTSB specialists were assigned: Cockpit Voice Recorder, Flight Data Recorder, Airports, Meteorology, Air Traffic Control, and Operational and Human Factors. The investigation is ongoing. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Landing area overshoot](https://openairdocs.org/ntsb-events/380) (defining event); cases with it: [Embraer EMB-145XR, 1 case](https://openairdocs.org/ntsb-events/380/sequence.md?model=3260214), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) ## Aircraft - Registration: [N21129](https://openairdocs.org/aircraft/N21129), registered now, S/N 145703, built 2003 (OpenAirDocs) - Reported make and model: EMBRAER EMB-145XR - Registry model: [Embraer EMB-145XR](https://openairdocs.org/model/embraer-emb-145xr) (registry code 3260214) (OpenAirDocs) - Registry engine: [Rolls-Royce AE3007 series](https://openairdocs.org/engine/rolls-royce-ae3007-series) (registry code 54582, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: 145703 - Year built: 2003 - Airframe hours: 49630 - Damage: Minor damage - Flight: Part 121 - Operator: CommuteAir, doing business as United Express - Registered owner: United Airlines Inc - Airworthiness certificate: Standard, Transport - Last inspection: 100 hour, September 12, 2025 - Departed: KIAD, Dulles, VA - Destination: KROA, Roanoke, VA - Flight plan: IFR - Airport: ROA, Roanoke–Blacksburg Regional Airport, runway 34, 5,810 × 150 ft, asphalt - Equipment: Stall warning system, Satellite tracking device, Onboard weather, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, ADS-B, Angle of attack indicator, Auto-pilot, Data recorder ## Weather - Conditions: Instrument (IMC), Night - Wind: 260° at 5 knots - Visibility: 1.75 statute miles - Lowest ceiling: 4,900 ft broken - Temperature: 72 °F, dew point 70 °F - Altimeter: 30.05 inHg - Observed at: KROA - METAR: SPECI KROA 250112Z 26005KT 1 3/4SM +RA BR FEW032 BKN050 OVC085 22/21 A3005 RMK AO2 TWR VIS 2 RAB07 P0000 T02170211= ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Incident 20250924018699I](https://openairdocs.org/incident/20250924018699I), Sep 24, 2025: Embraer EMB-145XR, Roanoke, VA, Minor damage. 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… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.