Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 3, 2010 · Cessna 172D · N2593

Durango, CO

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 3, 2010
Injury Outcomes
2 injuries (2 minor injuries)
Location
Durango, CO
Aircraft
Cessna 172D
Tail Number
N2593
Operator
Meca Supply
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CEN11LA001

The first takeoff attempt was aborted when the passenger's door popped open. The pilot taxied back to the end of the runway, closed the door, and began the takeoff. During the second takeoff attempt, as the airplane reached about 200 feet, the engine sputtered and lost power. The pilot enriched the mixture and applied carburetor heat, and the engine sputtered and lost power a second time. The pilot said that, during the forced landing, he shut the fuel off and turned off the master switch before the airplane impacted a dry river bottom. A postaccident examination of the airplane revealed that the fuel selector was found in the BOTH position at the accident site, even though the pilot reported he shut the fuel off prior to impact. The engine was test run to full power, and no anomalies were noted. It is likely that the pilot inadvertently turned off the fuel before the last takeoff, particularly since he was unfamiliar with this model of airplane.

NTSB Probable Cause

A total loss of engine power due to the pilot inadvertently moving the fuel selector to the OFF position. Contributing to the accident was the pilot's unfamiliarity with this model accident airplane.

Full Narrative

On October 3, 2010, approximately 1100 mountain daylight time, a Cessna 172D, N2593, was substantially damaged when it impacted terrain following a loss of engine power during takeoff from Animas Airpark (00C), Durango, Colorado. Visual meteorological conditions (VMC) prevailed at the time of the accident. The personal flight was being conducted under the provisions of 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. The pilot and passenger on board the airplane sustained minor injuries. The cross-country flight was originating at the time of the accident, and was en route to Page (PGA), Arizona. In a telephone interview, the pilot stated that whereas he had considerable experience in Cessna 172s, this was an older "D" model and a rental airplane. He had never flown He and his wife had flown from PGA to 00C two days before without incident and they were returning home. The pilot said he took off from runway 19 and when the airplane had climbed about 200 feet and was at midfield, the engine lost power. The pilot pushed the nose over to maintain airspeed and made a forced landing in a river bottom. According to the pilot's accident report, the fuel tanks were full and a preflight inspection was accomplished with no anomalies noted. Prior to takeoff, the mixture was leaned for maximum takeoff power, the fuel selector was positioned on both tanks, the flaps were set to 10 degrees, and the magnetos were checked. The first takeoff attempt was aborted when the passenger's door popped open. The pilot taxied back to the end of the runway, closed the door, and began the takeoff. The airplane was rotated about halfway down runway 19 (5,010 feet long). After climbing about 200 feet, the engine "sputtered a little, followed by silence!" The pilot said there was no remaining runway on which to land and he was committed to "going off the cliff at the south end of the mesa (the airport is situated on top of a mesa). The pilot enriched the mixture and applied carburetor heat. The engine "sputtered again like it wanted to run, then went silent." The pilot said he shut the fuel off, leaned the mixture, and turned off the master switch. The pilot cleared a power line by dropping 20 degrees of flaps and using up elevator. The airplane hit a brush pile in a flat attitude and bounced 40 feet. A Federal Aviation Administration (FAA) inspector from the Salt Lake City Flight Standards District Office (FSDO) went to the accident site. He interviewed the pilot and the fixed base operator (FBO). The inspector said he found the fuel selector in the BOTH position. The pilot has said he turned the fuel selector to the OFF position. In a telephone interview, the pilot stated that although he had considerable experience in Cessna 172s, this was an older "D" model and a rental airplane. He had never flown the Cessna 172D before. The fuel selector on recent model 172s’ has the left tank in the 9 o’clock position, the right tank in the 3 o’clock position, both tanks in the 12 o’clock position, and the off position in the 6 o’clock position. Earlier model 172s had an L-shaped selector handle with a long hand and a short hand. On December 30, 2010, the engine was functionally tested at the facilities of Air Transport in Phoenix, Arizona. No anomalies were noted and full power was achieved. Asked how this accident could have been prevented, it pilot responded in the accident report: "Stick to flying my own airplane."

Flight

Event TypeAccident
Event Time11:00 MDT
Nearest AirportAnimas Airpark (1nm)
Runway19
Runway Length5010 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172D
Tail NumberN2593
Aircraft CategoryAir
DamageSubstantial
OperatorMeca Supply
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-300-D · Reciprocating · 145
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 37 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind6 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point64 F / 43 C
Altimeter30.34 inHg
Observation Time16:53
Weather SourceWFAC

Appendix: Source Data