CHI02LA157 · Maule M-7-260C
Maule M-7-260C · Accident: in flight collision with object during landing
From Boone County Airport (6I4) to Fishers, IN
Event
- NTSB case
- CHI02LA157
- 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
Maule M-7-260C
- Aircraft type
- Maule M-7
- 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
- N63KP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boone County Airport (6I4), Lebanon, INTo Fishers, IN
- 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 · aborted
- 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
- Substantial
Cause areas
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During an attempted aborted landing the airplane impacted trees and terrain. The pilot reported, "Touchdown took place at about 1/2 of the way down the 1000' long field with a short bounce that put me uncomfortably long. I executed a go around and was surprised by the very sluggish climb performance and the height of the trees at the end of the field. I felt like the full flaps were creating too much drag at the same time I realized that I was perilously close to the pine trees at about 50 feet high. I retracted the flaps to reduce drag at about the same time that the right wing tip caught the pine. The impact slowed the right wing and the aircraft spun to the right coming down in the field north of the trees." The pilot stated, "In retrospect I realize that I had too much fuel 50 [gallons] versus my usual 25 [gallons] for this field and that the temperature and high humidity increased my ground speed due to the higher density altitude and drastically reduced my climb performance where my previous landings here [were] in the winter at much cooler temperatures. The turbulence and gusts caused me to add too much airspeed for a successful short field landing taking into account the power line." A weather reporting station recorded the wind speed around the accident time as 6 knots with no gusts.
Probable cause
The pilot not performing a go-around prior to exceeding the proper touchdown point and the pilot not maintaining altitude/clearance from the trees. Factors to the accident were the pilot's inadequate preflight planning and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA157
- Event ID
- 20020613X00880
- Case number
- CHI02LA157
- 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: 4754296a685763b74b28f57790d8f361c71fec1ac133a879244fdf984302b4ca; retrieved 2026-09-22T10:52:00.873Z.