The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB DCA25LA339 · Preliminary: the investigation is not finished

Embraer EMB-145XR incident near Roanoke, Virginia, September 25, 2025

On September 25, 2025 at about 1:17 am local time, a 2003 Embraer EMB-145XR, registered N21129, suffered minor damage in an incident during landing (landing roll) near Roanoke, Virginia (Roanoke–Blacksburg Regional Ai airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 53 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 25, 2025 · about 1:17 am local time
Place
Roanoke, Virginia · Roanoke–Blacksburg Regional Ai · map
Type
Incident
Injuries
No one was hurt; 53 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Embraer EMB-145XR, built 2003 · all EMB-145XRs on the register
Registration
N21129 · registry record · serial 145703
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area overshoot during landing (landing roll) defining event

The aircraft

  • Airframe total time: 49,630 hours
  • Last inspection: 100-hour inspection, September 12, 2025
  • Maximum gross weight: 53,351 lb
  • Seats: 55
  • Landing gear: retractable

The flight

  • Departed from: KIAD Dulles VA
  • Destination: KROA Roanoke VA
  • Flight plan: IFR
  • Runway 34, 5,810 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 260° at 5 knots
  • Visibility: 1.8 statute miles
  • Sky: broken clouds at 4,900 ft; a few clouds at 3,200 ft
  • Temperature: 72°F (22°C), dew point 70°F (21°C)
  • Altimeter: 30.05 inHg
  • Observation at 9:12 pm from KROA

Weather report (METAR): SPECI KROA 250112Z 26005KT 1 3/4SM +RA BR FEW032 BKN050 OVC085 22/21 A3005 RMK AO2 TWR VIS 2 RAB07 P0000 T02170211=

Injuries

FatalSeriousMinorNone
Cabi1
Flig2
Passengers50

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number DCA25LA339.