CEN20CA059 · Zenith CH 750
Zenith CH 750 · Accident: loss of control in flight during landing
From Greene County/Lewis A. Jackson Regional Airport (I19) to Greene County/Lewis A. Jackson Regional Airport (I19)
Event
- NTSB case
- CEN20CA059
- 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
- 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
- Visual Meteorological Cond
Zenith CH 750
- Aircraft type
- Zenith CH-750
- 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
- N227L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Greene County/Lewis A. Jackson Regional Airport (I19), Xenia, OHTo Greene County/Lewis A. Jackson Regional Airport (I19), Xenia, OH
- Aircraft age
- Built the same year (2019)
- 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
- Defining eventThe 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
- Loss of control in flight
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the flight was the first flight of the experimental, amateur-built airplane. He stated that he was lined up with the runway centerline for landing, that the airspeed was 60 mph, and that the tachometer was showing 1,600 rpm when he felt the right tire contact the runway. He said "in an instant the left wing came down and the left tire and axle [were] sheared off. The left wing impacted the runway and the plane skidded about 40 feet and came to a full stop." The pilot used a higher landing airspeed because he had been told by other builders of that airplane that he needed to land with speed "so as not [to] get near the stall speed as this aircraft does have leading edge slats and this equates to a high lift wing." Postaccident examination of the airplane revealed that the nose landing gear and the left wing strut sustained substantial damage.
Probable cause
The pilot’s failure to maintain airplane control during landing, which resulted in the right tire contacting the runway first followed by the left wing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA059
- Event ID
- 20200115X65318
- Case number
- CEN20CA059
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 01e40c9636bf50d2f1dfc4aa54b061d18c5719860673913d0485b253911b4633; retrieved 2026-09-16T10:56:57.652Z.