CEN10CA402 · Grumman Acft ENG COR-Schweizer G-164B
Hoppe Airspay Grumman Acft ENG COR-Schweizer G-164B · Accident: low altitude operation/event while maneuvering
From Independence Municipal Airport (IIB) to Independence Municipal Airport (IIB)
Event
- NTSB case
- CEN10CA402
- 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
Grumman Acft ENG COR-Schweizer G-164B
- Aircraft type
- Grumman G-164
- 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
- N8260K
- Operator
- Hoppe Airspay
- Onboard fatalities
- Unknown
- Route
- From Independence Municipal Airport (IIB), Independence, IATo Independence Municipal Airport (IIB), Independence, IA
- 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 137: Agricultural
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was making an aerial application pass at the south end of a field when the accident occurred. A 30-foot-tall power line ran north and south through the middle of the field. The pilot stated he was paying attention to the trees along the south end of the field during the pass when he realized that he was approaching the wires. He was unable to climb over the wires so he decided to fly under them. In doing so, the airplane contacted 7-foot-high corn and the airplane was pulled down into the field. Substantial damage resulted to the lower wings and the main landing gear mounting truss.
Probable cause
The pilot's failure to pay attention to the power lines and his subsequent failure to maintain clearance from the corn field during the aerial application flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA402
- Event ID
- 20100715X63552
- Case number
- CEN10CA402
- 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: eb5083a458f95cd62e0f13a7a4c193be66afca4147359aee7b39aa0c88c53df1; retrieved 2026-09-15T14:42:15.892Z.