LAX06CA209 · Cessna 152
Cessna 152 · Accident: hard landing
From Buchanan Field (CCR) to Buchanan Field (CCR)
Event
- NTSB case
- LAX06CA209
- 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
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
- N5534M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buchanan Field (CCR), Concord, CATo Buchanan Field (CCR), Concord, 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
- 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
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, misjudged
- Pilot in command › Recovery from bounced landing, inadequate
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 landed hard and the left wing struck the runway. The student pilot reported that when he turned the airplane onto the final leg of the traffic pattern, he noticed smoke coming from a field close to the runway. The student pilot was worried about his flight visibility and the effects that the smoke would have on the handling characteristics of the airplane. Due to these concerns, he was less focused on his landing and approached the runway at too high of an airspeed. When the airplane touched down, it bounced three times and drifted to the left. He added right rudder to prevent the airplane from veering off of the runway and the airplane sharply turned to the right and the left wing struck the ground. The student pilot said that there were no mechanical malfunctions with the airplane.
Probable cause
the student pilot's unstabilized approach, misjudged landing flare, inadequate recovery from a bounced landing, and failure to maintain directional control. A contributing factor to the accident was the in-flight distraction.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06CA209
- Event ID
- 20060707X00898
- Case number
- LAX06CA209
- 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: a92d43449e7d217699e3e83e9e6fba4a01e58eda8054744491f02baeab534ef1; retrieved 2026-09-22T04:43:48.761Z.