CHI96LA193 · Cessna 172
Cessna 172 · Accident: in flight collision with object on approach
From Lowell City Airport (24C) to Lowell City Airport (24C)
Event
- NTSB case
- CHI96LA193
- 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
- 0
- 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
Cessna 172
- Aircraft type
- Cessna 172
- 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
- N1106F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lowell City Airport (24C)To Lowell City Airport (24C)
- 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
- Approach · VFR go-around
- 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
- Designated examiner › Procedure inadequate
- Pilot in command › Inadequate initial training
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses reported the airplane made a landing approach with a quartering tailwind. The witnesses said the airplane hit the runway hard and bounced into the air two times. They reported the engine went to full power after the second bounce. The airplane had flown through five trees before colliding with the second story of a home. Shortly after getting the airplane's occupants out of the airplane, there was an explosion in the home. The pilot said he did a go-around as the airplane neared the runway's midpoint. He said he '...focusd on the trees in front of [him] and pulled significantly on [the] yoke trying to make the plane climb.' The pilot said he was not familiar with the terms 'back side of the power curve,' or 'region of reverse command.' The accident pilot's instructor was asked how he taught landings. He said the landing technique comes to the student through flying '...a whole bunch...' with the student. The accident pilot said his private pilot checkride lasted about 35 minutes. His logbook records confirm this. The FAA Designated Pilot Examiner's records showed 1.2 hours spent on a flight test.
Probable cause
was inadequate initial training of the pilot and inadequate flight test procedures by the FAA Designated Pilot Examiner when he reportedly had the pilot demonstrate 12 pilot operations from the FAA's practical flight test standards in 35 minutes during the pilot's private pilot flight test. A factor in this accident was the pilot's improper landing approach and go-around procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA193
- Event ID
- 20001208X05920
- Case number
- CHI96LA193
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-06-11.
- API snapshot SHA-256: 959a92f0e364ce24628daf3cfa4b275364dd989e4d1ed4716795da98270e32c4; retrieved 2026-09-21T12:42:19.845Z.