FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN03LA135 · Cessna A185F

22 Jul 2003 · Angel Fire, NM, United States

Cessna A185F · Accident: loss of control on ground/water during takeoff

From Santa Fe Municipal Airport (SAF) to Angel Fire Airport (AXX)

Report a problem

Event

NTSB case
DEN03LA135
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 A185F

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
N60VA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Fe Municipal Airport (SAF), Sante Fe, NMTo Angel Fire Airport (AXX), Angel Fire, NM
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
Takeoff · roll/run
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 › Directional control, not obtained/maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The instructor stated that this was a "re-familiarization" flight for the pilot and that the pilot also wanted a better understanding of flying in and around the airport. With the private pilot at the controls, they entered the traffic pattern and set up for a touch-and-go landing on runway 17. The landing was uneventful, and the pilot slowed the airplane down to approximately 10 to 15 knots. When the pilot added power for take-off, the airplane swerved to the left and the airplane's left main landing gear departed the left side of the runway. As the pilot applied rudder and aileron control to recover, the airplane veered to the right across the runway. When the airplane departed the right side of the runway, the instructor called out "I've got it." The airplane ground-looped to the right and struck a ditch between the runway and taxiway.

Probable cause

the instructor's inadequate supervision which resulted in the pilot's loss of directional control and the subsequent impact with the ditch. Contributing factors include the instructor's inadequate remedial action and the inadvertent ground loop/swerve.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN03LA135
Event ID
20030729X01209
Case number
DEN03LA135
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: 54a64e0a6bb6fbe77358311f177163283177821e908cfffc847e6d2e140265f8; retrieved 2026-09-22T08:55:48.672Z.