CHI92LA166 · Cessna 152
St Charles Flying Service Cessna 152 · Accident: loss of control in flight during landing
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI92LA166
- 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 152 Possible conflict
- Aircraft type
- Cessna 152
- 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
- N152AJ
- Operator
- ST. Charles Flying Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- 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
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command(cfi) › Aborted landing, delayed
- Pilot in command(cfi) › Recovery from bounced landing, inadequate
Approximate · Estimated position: the centre of Saint Charles, MO, the place the record names. Not the accident site.
NTSB narrative
THE INSTRUCTOR AND DUAL STUDENT WERE PRACTICING SOFT-FIELD AND CROSSWIND TAKEOFFS AND LANDINGS. THE STUDENT PILOT CAME IN HIGH AND FAST ON THE SECOND APPROACH TO LANDING. THE FLIGHT INSTRUCTOR STATED '...AS WE TOUCHED DOWN THE AIRCRAFT HIT A BUMP WHICH CAUSED US TO BOUNCE 6 TO 8 FEET INTO THE AIR.' THE INSTRUCTOR TOOK OVER THE CONTROLS AND ABORTED THE LANDING. HE STATED: 'IN ATTEMPTING TO GAIN THE LAST FEW FEET OF ALTITUDE FOR CLEARANCE THE AIRCRAFT STALLED AND MUSHED INTO THE HANGAR COMING TO REST ON THE TAIL OF THE AIRCRAFT PARKED INSIDE.'
Probable cause
THE FLIGHT INSTRUCTOR'S DELAY IN INITIATING A GO-AROUND AND IMPROPER RECOVERY FROM THE STUDENT'S BOUNCED LANDING. FACTOR(S) WHICH CONTRIBUTED TO THE ACCIDENT WAS THE STUDENT PILOT OVERSHOOTING THE APPROACH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI92LA166
- Event ID
- 20001211X14807
- Case number
- CHI92LA166
- 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 1992-06-10.
- API snapshot SHA-256: f0b924f8cb7bf07f3c3a96b4b17145bb4a286c8a6e10eb6691a776ecf459f8e7; retrieved 2026-09-23T03:04:29.523Z.