LAX05CA082 · Cessna 172S
Cessna 172S · Accident: hard landing
From Bakersfield International Airport (L45) to Harris Ranch Airport (3O8)
Event
- NTSB case
- LAX05CA082
- 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 172S
- 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
- N521JD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bakersfield International Airport (L45), Bakersfield, CATo Harris Ranch Airport (3O8), Coalinga, 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 · landing roll
- 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 › Aborted landing, not performed
- 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 encountered soft soil and nosed over during a landing overrun. The pilot said he touched down beyond the threshold and the airplane bounced once. By the time the pilot had recovered from the bounce and the airplane was in the landing rollout, the pilot determined that insufficient runway remained to stop the airplane. He elected not to perform an aborted landing due to the short runway and continued braking efforts. The airplane overran the end of the runway and the nose landing gear encountered soft dirt. The airplane nosed over and came to rest inverted.
Probable cause
the pilot's inadequate recovery from a bounced landing, and his failure to abort the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05CA082
- Event ID
- 20050222X00215
- Case number
- LAX05CA082
- 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: 4298c4548c32643225a0f92d8055103bebba128d18630998661d03310cf6d1af; retrieved 2026-09-22T06:18:35.273Z.