FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA358 · Cessna 172 P

1 Jul 2016 · Bountiful, UT, United States Narrative disagrees

Cessna 172 P · Accident: low altitude operation/event while maneuvering

From Skypark Airport (BTF) to Skypark Airport (BTF)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
GAA16CA358
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 172 P

Aircraft type
Cessna 172
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
N52071
Operator
Unknown
Onboard fatalities
Unknown
Route
From Skypark Airport (BTF), Bountiful, UTTo Skypark Airport (BTF), Bountiful, UT
Aircraft age
About 36 years (built 1980)
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
Maneuvering · low-altitude flying
Defining eventThe 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
Low altitude operation/event
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that during an "introductory flight" for two passengers, he departed the airport and flew into a canyon where the airplane encountered an "unforeseen immense downdraft". He further reported that he immediately initiated a right turn to exit the canyon but it became clear that a turn was not possible due to the mountainous terrain. Subsequently, the pilot decided to make an emergency landing on a mountain road. After touchdown the airplane skidded off the dirt road and down an embankment. A post-crash fire resulted in substantial damage to the fuselage and both wings.

The pilot reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

As a safety recommendation the pilot reported that he should have given himself more altitude before entering the canyon.

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 post-crash fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA358
Event ID
20160705X75553
Case number
GAA16CA358
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 3b61a2618ee02bb449556fb6e8911401e7226cd34c0190a4e206b169cb6d4c62; retrieved 2026-09-16T03:36:56.437Z.