FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA213 · Cessna 172L

22 Sept 2017 · Perkinsville, AZ, United States

Cessna 172L · Accident: turbulence encounter while maneuvering

From Prescott Regional Airport - Ernest A. Love Field (PRC) to an unrecorded destination

Report a problem

Event

NTSB case
WPR17FA213
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
2 · 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 172L

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
N7070Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo not recorded
Aircraft age
About 45 years (built 1972)
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
Turbulence encounter
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot had received his private pilot certificate about 7 months before the accident. He had told family members that he was planning to fly with his friend, the passenger, and stay in the airport traffic pattern performing touch-and-go takeoffs and landings.

Contrary to the pilot's stated plan, radar data indicated that the airplane departed toward a meandering river canyon immediately after takeoff. The radar data ended just before the airplane entered the canyon, likely due to terrain masking along the route of flight as a result of the airplane descending below the canyon walls.

The wreckage was located about 2 miles beyond the entrance to the canyon, at a tight turn of the river. The wreckage was on the steep face of a boulder-strewn cut bank about 500 ft above the river and 200 ft below the canyon rim. Wreckage debris indicated that the airplane impacted the ground in a near-vertical attitude with low-energy impact signatures, consistent with a low-speed collision and likely the early stages of a spin. The majority of the primary airframe structure was consumed by fire, but postaccident examination did not reveal any anomalies with the remaining airframe or engine components that would have precluded normal operation.

Performance calculations indicated that, while it was theoretically possible to negotiate the canyon bend in the airplane, the pilot would have needed to fly with precision and factor for tailwinds along with turbulence and downdrafts that were likely present in the canyon at that time and would have made escape from the canyon difficult.

The pilot had flown through the canyon with his instructor once before in another, slower, airplane but in the opposite direction of flight than that he took on the day of the accident. The wreckage was located in an area the instructor had specifically warned the pilot about due to the tight radius of the river bend and the close canyon walls, and during that flight they had bypassed the area. It is possible that the pilot did not recognize the turn during the accident flight because he was approaching from the opposite direction.

It could not be determined why the pilot chose to fly into the canyon instead of remaining at the airport as he had stated he planned to do. One possibility was that the airplane would soon need refueling, and the exit of the canyon was in the general direction of the airport where the pilot typically purchased fuel. Additionally, although by all accounts the young pilot was a conscientious and conservative aviator, having his friend on board may have influenced his decision to take a more exciting, yet less safe route.

There were no witnesses to the accident, and no one realized that the airplane was missing until the day after the accident. The airplane was ultimately discovered a few hours after the search was initiated. Although the airplane was equipped with an operational emergency locator transmitter (ELT), it failed to provide timely notification of the accident for at least two reasons. First, the ELT transmitted on the frequencies (121.5/243 MHz) that are no longer monitored by the Air Force Rescue Coordination Center; instead, they are only monitored randomly by some overflying aircraft. Second, the ELT signal was severely attenuated by the combination of its antenna location in relation to the final resting attitude of the airplane. However, due to the nature of the injuries incurred by both occupants, a timelier response to the accident site would not likely have increased their chances of survival.

Probable cause

The pilot's decision to fly into a canyon during wind conditions conducive to turbulence and downdrafts, and his subsequent loss of aircraft control while maneuvering in the canyon. Contributing to the accident was the pilot's limited canyon flying experience.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA213
Event ID
20170923X85234
Case number
WPR17FA213
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: 7215b8310a33aecb7b4a278f9c04274c0cdf2d21754f8fe31abf8cbdb6e8fae4; retrieved 2026-09-15T06:17:45.878Z.