MKC89FA104 · Callair A-9
Callair A-9 · Accident: airframe, component or system failure while maneuvering
From 6K1 · Marceline, MO to 6K1 · Marceline, MO
Event
- NTSB case
- MKC89FA104
- 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
- 1 · 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
Callair A-9
- Aircraft type
- Callair A-9
- 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
- N3581G
- Operator
- Anderson, John Kurt · private individual
- Onboard fatalities
- Unknown
- Route
- From 6K1 · Marceline, MOTo 6K1 · Marceline, MO
- 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
- Maneuvering · aerial application
- 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
- Airframe, component or system failure
- 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
- Company maintenance personnel › Maintenance, inspection, inadequate
- Flt control syst, rudder control cable/rod › Failure, total
- Pilot in command › Aircraft control, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS PRACTICING AGRICULTURAL SPRAY RUNS WHEN THE ACCIDENT OCCURRED. AFTER MAKING A STEEP RIGHT TURN TO ALIGN WITH THE FIELD, THE ACFT DESCENDED AND IMPACTED THE TERRAIN.A POST-CRASH FIRE ENSUED. METALLURGICAL EXAM OF THE RUDDER CABLE REVEALED THAT ALL WIRES ON FOUR OF THE SEVEN CABLE STRANDS WERE WORN THROUGH. THE PLT WAS THOUGHT TO HAVE HAD LESS THAN 100 HOURS TOTAL FLIGHT EXPERIENCE. A TEARDOWN OF THE ENGINE FAILED TO REVEAL ANY ANOMALIES WHICH WOULD HAVE SUGGESTED A FAILURE/MALFUNCTION.
Probable cause
THE PILOTS FAILURE TO MAINTAIN CONTROL AND PREVENT THE AIRPLANE FROM DESCENDING WHILE IN A TURN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MKC89FA104
- Event ID
- 20001213X28393
- Case number
- MKC89FA104
- 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: 78cbef9f70d1831d1acc467c069dc96262c9486b84182532f6460fa264bfac47; retrieved 2026-09-21T03:19:44.308Z.