# Accident 20160701010289A: Cessna 172P, Farmington, UT, July 1, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 1, 2016, 14:01 local time
- Place: Farmington, UT
- Damage: Destroyed
- Phase of flight: Cruise/Level Flight
- Operating rules: General operating rules (Part 91)
- Location: 40.0000° N, 111.8400° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.0000&lon=-111.8400&mi=10
- Aircraft: N52071, a cancelled registration (https://openairdocs.org/deregistered/N52071-2018-03-27) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 2
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 455 total, 30 in this make and model, 70 in the last 90 days
- NTSB investigation: [NTSB GAA16CA358](https://openairdocs.org/ntsb/GAA16CA358) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160701010289A

## Narrative

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

CE-172 WITH THREE OCCUPANTS ENTERED A NARROW AND STEEP UP SLOPING CANYON NEAR FARMINGTON UTAH. AT SOME POINT THE PILOT REALIZED THAT THE AIRCRAFT WAS NOT CLIMBING SUFFICIENTLY TO CLEAR TERRAIN. HE ATTEMPTED  A TURN DOWN CANYON BUT DIDN'T HAVE THE PERFORMANCE SO HE RETURNED TO FACING UP CANYON. AIRCRAFT IMPACTED TERRAIN ON THE EDGE OF A DIRT ROAD THEN SLID DOWN A 50 DEGREE SLOPE ABOUT 50 FEET. A POST CRASH FIRE DESTROYED THE AIRCRAFT.

## 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 GAA16CA358](https://openairdocs.org/ntsb/GAA16CA358), Jul 1, 2016: Cessna 172 (N52071), Bountiful, UT, substantial damage. Probable cause: The pilot's decision to fly into a canyon without sufficient room to reverse course if necessary, which resulted in an emergency landing, loss of directional control, collision with terrain, and a…

## Other reports on N52071 (1)

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

- [Accident 20100828043689A](https://openairdocs.org/incident/20100828043689A), Aug 28, 2010: Cessna 172P (N52071), Bartlesville, OK, Substantial damage. On August 28, 2010, student pilot, michael jason pugh, attempted a take off from Bartlesville, airport, (bov) runway 17. He was conducting a solo cross country…

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.