# Accident 20110614010509A: Cessna 172S, Cortez, CO, June 14, 2011

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 14, 2011, 14:00 local time
- Place: Cortez, CO
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.3017° N, 108.6236° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3017&lon=-108.6236&mi=10
- Aircraft: N6017J, a cancelled registration (https://openairdocs.org/deregistered/N6017J-2013-02-19) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 150 total, 25 in this make and model, 15 in the last 90 days
- NTSB investigation: [NTSB CEN11CA392](https://openairdocs.org/ntsb/CEN11CA392) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110614010509A

## Narrative

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

DURING LANDING PILOT BALLOONED UP. IN AN ATTEMPT TO RECOVER TO A CORRECT LANDING PROFILE, THE PILOT LANDED THE AIRCRAFT NOSE FIRST. THE NOSE GEAR AND RIGHT MAIN GEAR COLLAPSED AND THE AIRCRAFT CAME TO REST OFF THE RUNWAY.

## 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 CEN11CA392](https://openairdocs.org/ntsb/CEN11CA392), Jun 14, 2011: Cessna 172S (N6017J), Cortez, CO, substantial damage. Probable cause: The pilot's failure to maintain aircraft control while landing in gusty crosswind conditions.

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.