MKC83FCQ01 · Mooney M20A
Mooney M20A · Accident: in flight collision with object on approach
From Charles B. Wheeler Downtown Airport (MKC) to HALLSTEAD, KS
Event
- NTSB case
- MKC83FCQ01
- 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 M20A
- 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
- N8311E
- Operator
- Amos Max Cox
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo HALLSTEAD, KS
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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 › Compensation for wind conditions, improper
Approximate · Estimated position: the centre of Halstead, KS, the place the record names. Not the accident site.
NTSB narrative
DURING ARRIVAL, THE PILOT NOTED THAT THE WIND WAS FROM THE NORTHWEST. HE ESTIMATE IT WAS FROM 330 DEG AT 20, GUSTING 35 KTS. ON FINAL APPROACH, THE AIRCRAFT WAS REPORTEDLY UNSTABLE DUE TO GUSTY WINDS AND TURBULENCE. THE PILOT OBSERVED AND WAS AWARE OF THE POWER LINES NEAR THE APPROACH END OF THE RUNWAY. HE STATED THAT AIRCRAFT SETTLED, POSSIBLY DUE TO WIND SHEAR, AND HE WAS THEN UNABLE TO AVOID THE LINES. THE AIRCRAFT STRUCK AND SEVERED THE POWER LINES AND THEN IMPACTED THE GROUND JUST SHORT OF THE RUNWAY. THE POWER LINES WERE NOT MARKED. BUT ORANGE FIBERGLASS BALLS WERE MOUNTED ON 35 FT POLES, ABEAM THE APPROACH END OF THE RUNWAY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC83FCQ01
- Event ID
- 20020917X04986
- Case number
- MKC83FCQ01
- 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: c7915ea2f2b4309627940c18b3f4e7492a9cbfdbec544548529c71dc98e075dc; retrieved 2026-09-21T18:05:23.145Z.