LAX01LA167 · Cessna 152
Cessna 152 · Accident: hard landing
From Hayward Executive Airport (HWD) to an unrecorded destination
Event
- NTSB case
- LAX01LA167
- 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
- N757XS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hayward Executive Airport (HWD), HaywardTo 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
- Pilot in command › Elevator, improper use of
- Pilot in command › Flare, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
An FAA Inspector interviewed the pilot and examined the airplane. The pilot stated he had flown two landing patterns with a certified flight instructor in preparation for his second solo flight. The instructor deplaned and the student made two successful touch-and-go landings prior to the accident. On the third landing the airplane landed hard, bounced, and landed on the nose wheel. The student said that the bounce "was very high and I [tried] to pitch down and let it glide, but the nose wheel touch[ed] down first." The nose wheel was folded back along the underside of the fuselage and the left wingtip struck the runway bending the wing spar.
Probable cause
the student pilot's misjudged landing flare and improper use of the elevator control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA167
- Event ID
- 20010518X00955
- Case number
- LAX01LA167
- 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: 6edb9ab26fc9e3bf05c2e0b91f3c23efe46a6df851b164d0547a5521af86881e; retrieved 2026-09-22T11:58:38.818Z.