SEA92LA133 · Mooney M20C
Mooney M20C · Accident: hard landing
From King County International Airport - Boeing Field (BFI) to an unrecorded destination
Event
- NTSB case
- SEA92LA133
- 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
Mooney M20C
- Aircraft type
- Mooney M20
- 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
- N5794Q
- Operator
- Brees, Eunice G. · private individual
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo 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
- Landing · flare/touchdown
- 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
- Landing gear, main gear strut › Overload
- Landing gear, nose gear strut › Separation
- Pilot in command › Directional control, not maintained
- Pilot in command › Proper descent rate, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
UPON ARRIVAL AT THE AIRPORT THE PILOT SET UP TO LAND WITH A TAILWIND COMPONENT. DURING THE FLARE A DOWNDRAFT WAS ENCOUNTERED AND THE AIRCRAFT LANDED HARD. THE PILOT ATTEMPTED A GO AROUND AND THEN ABORTED THE ATTEMPT DURING WHICH THE AIRCRAFT DEPARTED THE RIGHT SIDE OF THE RUNWAY. AFTER LEAVING THE RUNWAY THE NOSE GEAR SEPARATED FROM THE AIRCRAFT AND THE RIGHT MAIN LANDING GEAR STRUT COLLAPSED.
Probable cause
THE PILOT IN COMMAND'S NOT MAINTAINING THE PROPER RATE OF DESCENT AND NOT MAINTAINING DIRECTIONAL CONTROL, AND SEPARATION OF THE NOSE GEAR STRUT AND OVERLOAD OF THE RIGHT MAIN GEAR STRUT. FACTORS CONTRIBUTING TO THE ACCIDENT WERE: WEATHER CONDITIONS: TAILWIND AND DOWNDRAFT, AND THE PILOT IN COMMAND'S SELECTION OF THE WRONG RUNWAY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA133
- Event ID
- 20001211X15009
- Case number
- SEA92LA133
- 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: 4720e194eb9f9d0f22f0dfde564a7d25ec3ee95eab9841a73f2ad00a1f3b6a68; retrieved 2026-09-21T23:14:30.460Z.