CHI05FA056 · Cessna 421C Riley Turbine E
Cessna 421C Riley Turbine E · Accident: in flight collision with object en route
From Johnson County Executive Airport (OJC) to Zephyrhills Municipal Airport (ZPH)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI05FA056
- 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
- 5 · all aircraft and ground
- 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
- Instrument Meteorological Cond
Cessna 421C Riley Turbine E
- Aircraft type
- Cessna 421
- 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
- N844JK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Johnson County Executive Airport (OJC), Olathe, KSTo Zephyrhills Municipal Airport (ZPH), Zephyrhills, FL
- 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
- En route · descent
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed Possible conflict
Cause areas
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane received substantial damage on impact with trees, terrain, and a residence about one mile from the departure airport during instrument meteorological conditions. The airport elevation was 1,096 feet mean sea level. The personal flight was operating on an instrument flight rules (IFR) flight plan with a filed equipment suffix designating that the airplane was equipped with a Global Positioning System. Airplane records indicate that the airplane was equipped with a GPS but was not approved for IFR navigation. The pilot was issued a departure clearance to 3,000 feet and heading of 130 degrees. Radar data indicates that the airplane leveled off at an altitude approximately 2,000 feet during a 32 second period while executing a right turn to the assigned heading. Witnesses reported that the airplane impacted terrain in a right wing nose low attitude. Wreckage distribution and ground scarring was indicative of a high-speed impact with terrain. No anomalies that would have precluded normal operation of the airplane were noted. The calculated airplane weight was approximately 597 lbs above the maximum gross weight of the airplane.
Probable cause
The pilot's failure to maintain adequate altitude/clearance during cruise flight, resulting in collision with trees. Contributing factors were the low altitude and low ceiling.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05FA056
- Event ID
- 20050126X00106
- Case number
- CHI05FA056
- 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: c2e637143671553fb3d1066f814cc2fbed2c9be00c2ba52b0f8808b483475636; retrieved 2026-09-20T18:08:11.147Z.