LAX91LA379 · Cessna C-152
Cessna C-152 · Accident: hard landing
From San Carlos Airport (SQL) to Palo Alto Airport (PAO)
Event
- NTSB case
- LAX91LA379
- 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 C-152
- Aircraft type
- Cessna C-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
- N89022
- Operator
- Main, Stanley G. · private individual
- Onboard fatalities
- Unknown
- Route
- From San Carlos Airport (SQL), San Carlos, CATo Palo Alto Airport (PAO), Palo Alto, CA
- 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
- Hard landing
- 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 › Recovery from bounced landing, improper
- Pilot in command(cfi) › Remedial action, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT LANDED HARD AND BOUNCED THE AIRPLANE BACK INTO THE AIR ABOUT 20 FEET. THE INSTRUCTOR TOOK OVER THE CONTROLS BUT WAS UNABLE TO GAIN CONTROL OF THE AIRPLANE BEFORE IT STALLED AND STRUCK THE RUNWAY WITH THE LEFT WING AND TAIL. THE AIRPLANE THEN DEPARTED THE LEFT SIDE OF THE RUNWAY, STRIKING A RUNWAY LIGHT. THERE WERE NO MECHANICAL FAILURES OR MALFUNCTIONS WITH THE AIRPLANE BEFORE THE ACCIDENT.
Probable cause
IMPROPER RECOVERY FROM A BOUNCED LANDING BY THE STUDENT PILOT AND THE DELAYED REMEDIAL ACTION OF THE INSTRUCTOR PILOT. CONTRIBUTING TO THIS ACCIDENT WAS THE STUDENT PILOT'S FAILURE TO MAINTAIN THE PROPER DESCENT RATE WHICH RESULTED IN A BOUNCED LANDING AND THE CERTIFIED INSTRUCTOR PILOT'S INADEQUATE SUPERVISION DURING THE LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA379
- Event ID
- 20001212X18110
- Case number
- LAX91LA379
- 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: beac7ae57aafbc4b3ca4ea41d7e5aa281590b8321a2df96da7675c2ac31776a3; retrieved 2026-09-23T03:44:26.050Z.