LAX95LA316 · Cessna 172A
Cessna 172A · Accident: loss of control on ground/water during landing
From 046 to an unrecorded destination
Event
- NTSB case
- LAX95LA316
- 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 172A
- 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
- N7641T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 046To 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
- Loss of control on ground/water
- 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(cfi) › Directional control, not maintained
- Pilot in command(cfi) › Ground loop/swerve, not corrected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT OWNER AND A CFI WERE PERFORMING A BIENNIAL FLIGHT REVIEW. THE FLIGHT INSTRUCTOR SAID THAT AFTER THE BFR WAS SUCCESSFULLY COMPLETED BY THE OWNER HE ASKED IF HE COULD DO ONE TAKEOFF AND LANDING, TO WHICH THE OWNER AGREED. THE FLIGHT INSTRUCTOR STATED THAT THE TAKEOFF AND PATTERN WERE NORMAL; HOWEVER, JUST AFTER TOUCHDOWN HE BEGAN TO HAVE DIRECTIONAL CONTROL PROBLEMS AND COULDN'T GET THE RIGHT RUDDER PEDAL TO MOVE BEYOND THE NEUTRAL POSITION. THE INSTRUCTOR SAID HE COULD NOT MAINTAIN DIRECTIONAL CONTROL AND THE AIRCRAFT DRIFTED OFF THE RUNWAY EDGE, RAN DOWN AN EMBANKMENT, AND NOSED OVER AFTER ENCOUNTERING LARGE BOULDERS. AN FAA AIRWORTHINESS INSPECTOR REPORTED THAT NO DISCREPANCIES WERE FOUND IN AN EXAMINATION OF THE CONTROL SYSTEM.
Probable cause
the flight instructor's failure to maintain directional control of the aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX95LA316
- Event ID
- 20001207X04309
- Case number
- LAX95LA316
- 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: 11192bacfe348dedbab62a2b2f0ec801d1d9e37e6ce140fa599ddb521f732888; retrieved 2026-09-22T23:19:48.420Z.