CHI06CA180 · Piper PA-28-161
Piper PA-28-161 · Accident: loss of control in flight during landing
From Jefferson City Memorial Airport (JEF) to Jefferson City Memorial Airport (JEF)
Event
- NTSB case
- CHI06CA180
- 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
Piper PA-28-161
- Aircraft type
- Piper PA-28
- 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
- N43060
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jefferson City Memorial Airport (JEF), Jefferson City, MOTo Jefferson City Memorial Airport (JEF)
- 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 · flare/touchdown
- 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
- Dual student › Airspeed, not maintained
- Dual student › Flare, excessive
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 impacted a 24-inch high runway edge light during landing. The flight instructor reported that during the landing flare the student "over flared, causing the airplane to stall" and that the airplane drifted to the right side of the runway. The flight instructor stated that he then assumed aircraft control and "applied full throttle and leveled the wings," but the airplane "settled for a moment before gaining speed and altitude." The flight instructor reported that he "felt and heard" the airplane impact the runway light while he was regaining aircraft control. The flight instructor stated that he flew the airplane back to the runway centerline and landed without further incident.
Probable cause
The dual student's excessive landing flare and his failure to maintain adequate airspeed, which resulted in the airplane stalling. A factor to the accident was the flight instructor's delayed remedial action and the runway edge light that the airplane struck.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA180
- Event ID
- 20060801X01069
- Case number
- CHI06CA180
- 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: a9ce5a5cc52a939b44464672f5116fea8d0d58ce6162412a780b4fbfd0b040bd; retrieved 2026-09-22T04:42:19.307Z.