LAX98LA055 · Cessna 172N
Cessna 172N · Accident: hard landing
From Reid-Hillview Airport of Santa Clara County (RHV) to an unrecorded destination
Event
- NTSB case
- LAX98LA055
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N739HE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Reid-Hillview Airport of Santa Clara County (RHV)To 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 › Airspeed, excessive
- Pilot in command › Flare, misjudged
- Pilot in command › Proper descent rate, not obtained/maintained
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the student pilot's second landing of his third solo instructional flight, he had been cleared for the option. He remembers feeling fatigued and disoriented before turning to the base leg; however, once he turned on final he felt normal again. He stated that he configured the aircraft for landing, but that his airspeed was high and the aircraft was descending at a rapid rate. The student said the aircraft landed hard and became airborne again. He attempted to recover from the hard landing, but the aircraft continued to porpoise down the runway until the nose gear collapsed.
Probable cause
the student pilot's failure to maintain an appropriate airspeed and proper rate of descent, and his misjudged landing flare, which led to an uncontrolled porpoise and eventual collapse of the landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98LA055
- Event ID
- 20001208X09212
- Case number
- LAX98LA055
- 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: 7770c355b9e2f21fd6aa0fbacb95f2c6ac58ed9725ca6c69f884ff3d01f5c307; retrieved 2026-09-22T18:10:09.632Z.