The U.S. aircraft register, updated daily
Accidents · NTSB WPR23LA150 · Final report

Compagnie Daher TBM 700 accident near Ashland, Oregon, April 7, 2023

On April 7, 2023 at about 11:55 pm local time, a 2021 Compagnie Daher TBM 700, registered N6924G, was destroyed in an accident during approach (VFR go-around) near Ashland, Oregon (Ashland Muni/Sumner Parker Fld airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain adequate airspeed during an attempted go around, which resulted in a runway excursion and impact with terrain.

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

What the record shows

Date
April 7, 2023 · about 11:55 pm local time
Place
Ashland, Oregon · Ashland Muni/Sumner Parker Fld · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Compagnie Daher TBM 700, built 2021 · all TBM 700s on the register
Registration
N6924G · no longer on the register · serial 1377
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

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

The pilot reported he was 2.5 hours into a flight review when the accident occurred. On the last leg of the trip the flight the instructor simulated a runway closure and a diversion to a nearby airport. The pilot verified the favored runway and entered an extended downwind to set up a stable approach. The pilot configured the airplane per the airplane checklist and set his power setting for a torque greater than 10 percent to maintain an airspeed of 80-95 knots indicated airspeed (KIAS). When crossing the runway threshold, the instructor stated there was a simulated obstruction on the runway and instructed the pilot to go around. As the pilot advanced the power, the airplane yawed to the left of the runway centerline. The pilot remembers adding right rudder pressure with no effect. The airplane touched down on the left side of the runway and then departed the runway. The airplane traveled through bushes and scrub trees before coming to rest at the edge of a creek. The pilot and instructor secured the airplane and exited before a small fire engulfed much of the airplane. Although the pilot and instructor did not recall any indication of impending loss of control or an aural stall warning before touchdown, audio recorded from onboard the airplane revealed that during the accident approach an electronic voice called out “Stall. Stall.” three times when the airplane was below 500 ft above ground level (agl), followed by “Airspeed” just before touchdown. During and after touchdown, “Stall. Stall.” sounded four additional times as the airplane decelerated. Recordings from the previous leg also contained stall and airspeed electronic voice call outs before landing. The first-leg landing did not include a go-around. Telemetry data recovered showed airspeeds below the required 80 KIAS during the go around attempt. Airplane data showed that on the last two final approaches the airspeed was below 80 KIAS which is required for a go-around at time stamp 22:55:33 for the previous approach and at 23:51:24 on the accident approach. The airplane’s stall speed when configured to land with full flaps, (Vso) is 65 KIAS. The Pilot’s Operating Handbook (POH) describes a minimum go around speed of 80 KIAS to ensure adequate airflow over the rudder to maintain its effectiveness during a go-around maneuver. It is likely that at the application of go-around power, the airspeed was inadequate to provide the right rudder pressure necessary to overcome the left turning yawing moment that was moving the airplane to the left.

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 control in flight during approach (VFR go-around) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,655 hours in all; 206 in this make and model; 19 in the last 90 days; 9 in the last 30 days; 2,655 as pilot in command
  • Last flight review: June 18, 2021
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Flight instructor

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 9,347 hours in all; 5.3 in this make and model
  • Medical certificate: Class 2
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 225 hours
  • Last inspection: annual inspection, June 14, 2022; 9 hours since
  • Maximum gross weight: 7,394 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Pratt & Whitney PT6A-66D/1354 (turboprop); 225 hours total
  • Fire on the ground

The flight

  • Departed from: KLMT Crater Lake/Klamath Regional Airport OR at 11:15 pm
  • Destination: KMFR Rogue Valley International - Medford Airport OR
  • Flight plan: IFR
  • Runway 30, 3,603 ft by 75 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 250° at 9 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,500 ft; scat at 4,500 ft
  • Temperature: 55°F (13°C), dew point 39°F (4°C)
  • Altimeter: 29.91 inHg
  • Observation at 4:53 pm from KMFR, 15 miles away

Weather report (METAR): KMFR 072353Z 25009KT 10SM BKN055 OVC070 13/04 A2991 RMK AO2 RAE2256 SLP129 P0000 60001 T01330039 10144 20094 53003

Injuries

FatalSeriousMinorNone
Flight crew2

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

13 documents, released by the NTSB on February 20, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 POH Short Final 500 Ft PDF, 2 pages View Download
3 POH Go-around Procedure PDF, 3 pages View Download
4 POH Approach Airspeed PDF, 1 page View Download
5 POH Vso PDF, 1 page View Download
6 Materials Laboratory Factual Report 23-046 PDF, 6 pages View Download
7 Cockpit Display - Specialist's Factual Report PDF, 4 pages View Download
8 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
9 Full Flight Data spreadsheet Download
10 Photos PDF, 2 pages View Download
11 Cockpit Voice Recorder - Specialist's Factual Report PDF, 17 pages View Download
12 Flight Data Recorder - Specialist's Factual Report PDF, 26 pages View Download
13 Flight Data Recorder - Specialist's Factual Report - ATTACHMENT1 - Ldr Tabular Data data file Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N6924G the same tail number, which may have belonged to a different aircraft at the time

1982-07-31NYC82DA177 · accident near Williamson, NY · substantial damage · minor injuries

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.