LAX95LA071 · Cessna 175
Cessna 175 · Accident: nose over during landing
From 2Q3 · CA to an unrecorded destination
Event
- NTSB case
- LAX95LA071
- 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 175
- Aircraft type
- Cessna 175
- 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
- N7098M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2Q3 · 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 · 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
- Nose over
- 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 obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT SAID HE WAS ON FINAL APPROACH TO A COUNTY DIRT ROAD HE INTENDED TO USE AS A RUNWAY WHEN THE ENGINE FALTERED AT 75-100 FEET AGL. THE RPM'S FELL FROM 1800 RPM TO BELOW 1000 RPM. HE SAID HE HAD PLANNED HIS GLIDEPATH TO MISS A TREE ON THE ROADWAY SHOULDER. THE ENGINE WOULD NOT RESPOND TO THROTTLE ADVANCEMENT, SO THE PILOT ELECTED TO LAND SHORT ON THE ROADWAY. THE PILOT TURNED THE AIRCRAFT TO THE LEFT TO MISS THE TREE, AND THE LEFT MAIN GEAR SLIPPED OFF THE ROAD AND INTO SOFT SOIL. THE ENGINE THEN RESPONDED TO THROTTLE APPLICATION AND THE PILOT ATTEMPTED TO STEER THE AIRCRAFT BACK ONTO THE CENTER OF THE ROAD. ACCUMULATED SOFT DIRT IN FRONT OF THE MAIN GEAR PULLED THE NOSE GEAR OFF THE ROAD AND INTO SOFT DIRT, WHICH CAUSED THE AIRCRAFT TO NOSE OVER. POSTACCIDENT EXAMINATION OF THE AIRCRAFT BY FAA INSPECTORS REVEALED NO DISCREPANCIES WITH THE AIRFRAME OR ENGINE.
Probable cause
the failure of the pilot to maintain directional control of the aircraft while on the rollout phase of landing on a dirt road. A factor in the accident was the pilot's intentional selection of the road as a landing site.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX95LA071
- Event ID
- 20001207X02881
- Case number
- LAX95LA071
- 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: 53d97ecb90853fcbf204cf5e919ef89e12613a3c97c296a5bc82f2ef9b8d0f55; retrieved 2026-09-23T00:20:55.949Z.