SEA00LA006 · Piper PA-24-250
Piper PA-24-250 · Accident: hard landing on approach
From Bozeman Yellowstone International Airport (BZN) to an unrecorded destination
Event
- NTSB case
- SEA00LA006
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N8078P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bozeman Yellowstone International Airport (BZN)To not recorded
- Aircraft age
- Not recorded
- 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 pattern final
- First occurrenceThe 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
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command(cfi) › Remedial action, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot, whose flight review had expired, was in the process of completing a flight review recurrency flight, when the instructor reduced the power and asked him to execute a simulated forced landing. As he stretched the glide in an attempt to make it to the approach end of the runway, the airspeed became lower than normal approach speed. Although the aircraft was able to reach the end of the runway, just after it crossed the threshold, it dropped onto the runway with sufficient force to cause substantial damage. Although the airspeed had slowed below normal approach speed as the aircraft neared the approach end of the runway, the instructor pilot did not add power, nor did she call for termination of the simulated forced landing exercise.
Probable cause
The pilot-in-command's (CFI) failure to take remedial action. Factors include the private pilot letting the airspeed get too low.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA006
- Event ID
- 20001212X20054
- Case number
- SEA00LA006
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- 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. 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: 52417a6685a8ac34e27049f027f6c448e45fa5c229174aecd2651d851a456ffe; retrieved 2026-09-21T20:21:59.302Z.