# Accident 20020109000399A: Cessna 172N, Durango, CO, January 9, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 9, 2002, 11:30 local time
- Place: Durango, CO
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 37.5500° N, 107.8669° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.5500&lon=-107.8669&mi=10
- Aircraft: N3535E, a cancelled registration (https://openairdocs.org/deregistered/N3535E-2012-10-04) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Fatal injuries: 0
- NTSB investigation: [NTSB FTW02LA063](https://openairdocs.org/ntsb/FTW02LA063) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020109000399A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT DEPARTED FARMINGTON, NM ON THE MORNING OF JANUARY 09, 2002. FLEW UP A CANYON NEAR DURANGO, WAS UNABLE TO CLIMB OR TURN AROUND. A/C CRASED AT APPROX. 1130 AM LOCAL TIME WITH THREE (3) SOULS ON BOARD. PILOT RECEIVED MINOR INJURIES, PASSENGERS HAD SERIOUS INJURIES. A/C WAS DESTROYED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB FTW02LA063](https://openairdocs.org/ntsb/FTW02LA063), Jan 9, 2002: Cessna 172N (N3535E), Durango, CO, substantial damage. Probable cause: the pilot's failure to maintain clearance with the trees and mountainous terrain while maneuvering. A contributing factor was the pilot's delay in taking remedial action.

## Other reports on N3535E (1)

Matched to the same aircraft by N-number and date.

- [Accident 19960612013419A](https://openairdocs.org/incident/19960612013419A), Jun 12, 1996: Cessna 172N (N3535E), Farmington, NM, Substantial damage. Lost control on touch and go practice. Exited runway across grass taxiway and ramp then struck parked aircraft. (-23) upon touchdown rwy 25, the aircraft…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.