CHI07CA156 · Luscombe 8A
Luscombe 8A · Accident: loss of control in flight on approach
From 3I1 · Elwood, IN to an unrecorded destination
Event
- NTSB case
- CHI07CA156
- 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
Luscombe 8A
- Aircraft type
- Luscombe 8
- 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
- N2897K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3I1 · Elwood, INTo not recorded
- 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 pattern final
- 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 in flight
- 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
- Stall/mush
- 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
- Copilot/second pilot › Supervision, inadequate
- Pilot in command › Airspeed, low
- Pilot in command › Altitude, low
- Pilot in command › Stall/mush, inadvertent
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 contacted the ground following a loss of control during a simulated forced landing. Both pilots stated they had performed two simulated emergency landing approaches and the accident occurred on the third simulated emergency landing. Both pilots reported that during the third simulated emergency, the commercial pilot made a 180 degree turn to return to the landing strip. The commercial pilot reported they were "to low and to slow" when they reached the landing strip. The CFI reported he added full power, but it was too late and the airplane contacted the ground at a slow speed.
Probable cause
The commercial pilot's failure to maintain adequate altitude and airspeed which resulted in the airplane mushing into the terrain during the simulated forced landing along with the CFI's failure to adequately supervise the commercial pilot's actions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA156
- Event ID
- 20070622X00782
- Case number
- CHI07CA156
- 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: 8b3e2094d7a4a00c4ea17d097d93b91e8efcbdc64fdd28bef7aa37edc47b3065; retrieved 2026-09-21T18:30:38.728Z.