The U.S. aircraft register, updated daily
Accidents · NTSB WPR17FA213 · Final report

Cessna 172L accident near Perkinsville, Arizona, September 22, 2017

On September 22, 2017 at about 11:35 pm local time, a 1972 Cessna 172L, registered N7070Q, was destroyed in an accident during maneuvering (low-alt flying) near Perkinsville, Arizona. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 22, 2017 · about 11:35 pm local time
Place
Perkinsville, Arizona · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 172L, built 1972 · all 172Ls on the register
Registration
N7070Q · no longer on the register · serial 17260370
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Turbulence encounter during maneuvering (low-alt flying) defining event
  2. Loss of control in flight during maneuvering (low-alt flying)
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Turbulence › Terrain induced turbulence › Effect on operation
  • cause Environmental issues › Conditions/weather/phenomena › Wind › Downdraft › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Turbulence › Terrain induced turbulence › Ability to respond/compensate
  • Environmental issues › Conditions/weather/phenomena › Wind › Downdraft › Ability to respond/compensate

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 120 hours in all; 100 in this make and model
  • Last flight review: February 25, 2017
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,064.7 hours
  • Last inspection: annual inspection, June 27, 2017; 30 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4M (piston); 1,664 hours total
  • Fire on the ground

The flight

  • Departed from: PRC Prescott AZ at 11:21 pm
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 200° at 15 knots, gusting 22
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 66°F (19°C), dew point 16°F (-9°C)
  • Altimeter: 29.86 inHg
  • Observation at 11:53 pm from KPRC, 20 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

15 documents, released by the NTSB on July 2, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.