LAX86LA133 · Cessna 152
Coastal Air… Cessna 152 · Accident: hard landing
From San Luis County Regional Airport (SBP) to an unrecorded destination
Event
- NTSB case
- LAX86LA133
- 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
- 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
- N49429
- Operator
- Coastal Air
- Onboard fatalities
- Unknown
- Route
- From San Luis County Regional Airport (SBP), San Luis Obispo, CATo 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 · 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
- Flight instructor(on ground) › Preflight planning/preparation, poor
- Pilot in command › Flare, attempted
- Pilot in command › Recovery from bounced landing, poor
Approximate · Estimated position: the centre of San Luis Obispo, CA, the place the record names. Not the accident site.
NTSB narrative
ON MARCH 4, 1986 A CESSNA 152 COLLIDED WITH THE RUNWAY SURFACE AFTER THE NOSE WHEEL COLLAPSED. THE STUDENT PILOT WAS ON HIS THIRD CONSECUTIVE SOLO FLIGHT SINCE HIS SOLO ENDORSEMENT. ON HIS THIRD APPROACH THE AIRCRAFT BOUNCED ON LANDING AND BECAME AIRBORNE WITH A NOSE HIGH ATTITUDE. HE APPLIED FORWARD PRESSURE ON THE YOKE TO LEVEL THE NOSE AND THE AIRCRAFT LANDED ON THE NOSE WHEEL AND BEGAN TO PORPOISE. ON THE THIRD OSCILLATION THE NOSE WHEEL COLLAPSED AND THE AIRCRAFT CAME TO AN ABRUPT STOP. THE INSTRUCTOR PILOT WAS A NEW CFII WITH LESS THAN 1000 HOURS FLIGHT EXPERIENCE WHO HAD JUST RECEIVED HIS RATING THREE MONTHS AGO. HE HAD CHECKED THE WEATHER AND BRIEFED THE STUDENT PILOT PRIOR TO THE FLIGHT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86LA133
- Event ID
- 20001213X33091
- Case number
- LAX86LA133
- 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: c15958c299a998bb3ef5e300db7a145c22f5bb08d60263abbf0c7fb56fb3c4ca; retrieved 2026-09-23T14:59:01.118Z.