FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA163 · Cessna 185F

8 Apr 1996 · Placerville, CA, United States

Cessna 185F · Accident: loss of control on ground/water during landing

From Placerville Airport (PVF) to Placerville Airport (PVF)

Report a problem

Event

NTSB case
LAX96LA163
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 185F

Aircraft type
Cessna 185
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
N61905
Operator
Unknown
Onboard fatalities
Unknown
Route
From Placerville Airport (PVF)To Placerville Airport (PVF)
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) › Remedial action, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot had just purchased the conventional gear airplane from the CFI, and he desired a check-out. The CFI talked the owner through the first landing. Then, the CFI took the controls and planned to demonstrate performance of a three-point touchdown. The CFI did not indicate that anything unusual occurred except the airplane veered right during rollout. According to the CFI, he attempted to take corrective action by applying left rudder, but the airplane continued rolling to the right. The airplane exited off the side of the runway, entered a dirt area, and nosed over. No mechanical failures or malfunctions were experienced.

Probable cause

the CFI's failure to take adequate remedial action to preclude the loss of direction control during landing rollout.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA163
Event ID
20001208X05609
Case number
LAX96LA163
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: b311f733291fc07418cede770f3614529e7fe0dda44314f8266897a01af39f13; retrieved 2026-09-22T22:39:30.215Z.