CHI04LA249 · Johnson-Moore Zenith CH 701
Johnson-Moore Zenith CH 701 · Accident: loss of control on ground/water during landing
From Jerry Sumners Sr Aurora Municipal Airport (2H2) to Galena, MO (private airstrip)
Event
- NTSB case
- CHI04LA249
- 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
Johnson-Moore Zenith CH 701
- Aircraft type
- Johnson Moore ZENITH CH 701
- 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
- N2077Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jerry Sumners Sr Aurora Municipal Airport (2H2), Aurora, MOTo Galena, MO (private airstrip)
- 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 · landing roll
- 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
- Loss of control on ground/water
- 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
- Directional control › Not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane collided with a tree following a loss of directional control while landing on a private airstrip. The pilot reported that after touching down, the airplane made an immediate hard left swerve. The airplane traveled off the left side of the airstrip where it contacted a 12-inch diameter tree. He stated the tree was located approximately 50 yards off the side of the airstrip. The pilot reported the windsock on the airstrip was indicating little to no wind at the time. Approximately one year prior to this accident, the pilot and airplane were involved in a similar occurrence where the airplane veered sharply to the left after touchdown and traveled into tall brush. The pilot stated they inspected the brake system after that occurrence and they did not find any problems with it. He stated they repaired the airplane and he flew it three or four times prior to this accident.
Probable cause
A loss of directional control for undetermined reasons. A factor associated with the accident was the tree that the airplane contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA249
- Event ID
- 20040920X01468
- Case number
- CHI04LA249
- 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, coordinates. 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: 6110d7bfa771e01c970ce83ee00897195d13b79288482717baf83c04a15c7e4e; retrieved 2026-09-21T09:13:21.882Z.