The U.S. aircraft register, updated daily
Accidents · NTSB ERA26LA345 · Preliminary: the investigation is not finished

Cirrus Design CORP SR20 accident near Asheville, North Carolina, September 19, 2026

On September 19, 2026 at about 2:45 pm local time, a 2019 Cirrus Design CORP SR20, registered N189WM, was substantially damaged in an accident during maneuvering near Asheville, North Carolina (Asheville Rgnl airport). It was an instructional flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

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

What the record shows

Date
September 19, 2026 · about 2:45 pm local time · cases in 2026
Place
Asheville, North Carolina · Asheville Rgnl · cases near this airport · map
Type
Accident
Injuries
2 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR20, built 2019
Registration
N189WM · registry record · serial 2507
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

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

On September 19, 2026, at 1045 eastern daylight time, a Cirrus SR-20, N189WM, sustained substantial damage when it was involved in an accident near Ashville, North Carolina. The flight instructor and the student pilot received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The flight instructor reported that, during the pre-takeoff run-up, while checking the magnetos, the engine rpm dropped by 100 on the right and 150 on the left. Unable to resolve the discrepancy, they taxied back and troubleshot the issue further with the chief flight instructor. The flight instructor was informed that the anomaly was discovered on previous flights and that the mixture needed to be precisely leaned for density altitude. They were departing from Asheville Regional Airport (AVL) Asheville, North Carolina, which had a field elevation of 2,163 ft. After receiving the information, the pilot leaned the fuel mixture, and the magneto check was within limits. No further anomalies were observed. After taxi out, while holding short of the takeoff runway, the instructor performed another engine run-up and checked the magnetos, which yielded normal results. During the takeoff roll, all gauges and indications were reading normal, and the engine was performing normally during the takeoff roll and climb out. During the later stages of the climb, the instructor noticed that the engine cylinder head temperatures (CHTs) were reading a little high, so he enriched the mixture to keep the CHT below 400°. About 10 seconds after adding mixture, while at an altitude of about 3,000 ft, mean sea level the engine lost all power. The instructor took over the controls, turned back toward the airport, and declared an emergency. His attempts to restart the engine were unsuccessful and he pitched for best glide speed. During the descent, they were still over mountainous terrain at 2,000 ft above ground level and the flight instructor determined it was too risky to activate the Cirrus Airframe Parachute System (CAPS) so he aimed towards the first open field and intended to pull the CAPS as soon as they arrived over the field or at 800 ft agl, “whichever came first.” Once over the field, the instructor activated the CAPS; the parachute deployed and the airplane descended and settled onto the field. During the landing, the nose gear collapsed, and the engine compartment and airframe forward of the cockpit were substantially damaged. The wreckage was recovered and retained for further examination.

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. Loss of engine power (total) during maneuvering defining event

The aircraft

  • Airframe total time: 782 hours
  • Last inspection: annual inspection, June 23, 2026; 9 hours since
  • Maximum gross weight: 3,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Operator: Nc Mountain Aero LLC

The flight

  • Runway 17/3, 8,002 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 66°F (19°C)
  • Altimeter: 30.17 inHg
  • Observation at 11:00 am from AVL, 3 miles away

Weather report (METAR): METAR KAVL 191454Z VRB04KT 10SM CLR 26/19 A3017 RMK AO2 SLP185 T02560194 51005

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA26LA345.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.