FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA150 · Compagnie Daher TBM 700

7 Apr 2023 · Ashland, OR, United States

Compagnie Daher TBM 700 · Accident: loss of control in flight on approach

From Crater Lake-Klamath Regional Airport (KLMT) to Rogue Valley International-Medford Airport (KMFR)

Report a problem

Event

NTSB case
WPR23LA150
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Compagnie Daher TBM 700

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6924G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Crater Lake-Klamath Regional Airport (KLMT), Klamath Falls, ORTo Rogue Valley International-Medford Airport (KMFR), Medford, OR
Aircraft age
About 2 years (built 2021)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR go-around
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA150
Event ID
20230410107033
Case number
WPR23LA150
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a48709da8447d68e930398c42f4c29145ecc2eb5892cf5c356b4ec0b17806ca2; retrieved 2026-09-16T17:29:44.563Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: departure, destination. City slot holds the airport name; KLMT is Crater Lake-Klamath Regional Airport at Klamath Falls, OR. City slot holds the airport name; KMFR is Rogue Valley International-Medford Airport at Medford, OR.