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

Boeing A75N1(PT17) accident near Madras, Oregon, August 27, 2016

On August 27, 2016 at about 9:25 pm local time, a 1941 Boeing A75N1(PT17), registered N999PP, was destroyed in an accident during maneuvering (aerobatics) near Madras, Oregon (Madras Municipal airport). It was an air show or air race flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain clearance from the runway during a low-level aerobatic maneuver. Contributing to the accident was a high density altitude and the pilot's failure to plan/adequately compensate for high density altitude conditions.

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

What the record shows

Date
August 27, 2016 · about 9:25 pm local time
Place
Madras, Oregon · Madras Municipal · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Boeing A75N1(PT17) UNDESIGNAT, built 1941 · all A75N1(PT17)s on the register
Registration
N999PP · no longer on the register · serial 75-2389
Damage
Destroyed
Flight
Air show or air race flight · general aviation rules (Part 91)

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

As part of an air show, the commercial pilot was attempting to perform an inside loop immediately after takeoff. He had successfully accomplished the maneuver the previous day, as well as at many previous air shows. Witnesses observed the airplane lift off the runway and remain in a level attitude just above the runway surface before it climbed to perform the loop. Witnesses reported that the airplane descended from the top of the loop to a point in which its pitch attitude was between 10° and 20° nose-down until it impacted the runway. Video footage of the accident indicated that the pilot was in control of the airplane throughout the maneuver, and postaccident examination revealed no evidence of a preimpact mechanical malfunction or failure that would have precluded normal operation. Another performer at the airshow reported that, during the evening practice the day before the accident, he observed the pilot perform the same maneuver, and described it as "sketchy" because of the low altitude at which the pilot completed the loop. He added that he previously asked the pilot how to perform this maneuver and the pilot said that it was a "complete crapshoot"; at the top of the loop, the pilot would decide whether he would "pull through and continue the loop or rollout into a half-Cuban or an Immelmann," both of which are recovery aerobatic maneuvers. Prior to takeoff, the Air Boss reported to the pilot a density altitude (DA) of 4,600 ft. Postaccident calculations revealed that the DA at the time of the accident was about 5,221 ft, both of which are well above a standard day. The high density altitude conditions would have degraded the airplane's overall performance, resulting in decreased engine power available and reduced rate of climb. It is likely that the pilot failed to adequately compensate for the changes in airplane performance due to the high density altitude conditions, which resulted in a collision with terrain.

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. Abrupt maneuver during takeoff
  2. Low altitude operation/event during maneuvering (aerobatics) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during maneuvering (aerobatics)
  4. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • factor Personnel issues › Task performance › Planning/preparation › Performance calculations › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • factor Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Effect on operation

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: instrument airplane; instrument: airplane
  • Flight time: 10,000 hours in all
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rear
  • Injury: fatal

The aircraft

  • Last inspection: annual inspection, April 20, 2016
  • Maximum gross weight: 2,683 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Pratt & Whitney R985 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: S33 Madras OR at 9:25 pm
  • Destination: S33 Madras OR
  • Runway 34, 5,089 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 330° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°F (34°C), dew point 36°F (2°C)
  • Altimeter: 29.90 inHg
  • Observation at 9:29 pm from KS33

Injuries

FatalSeriousMinorNone
Flight crew1

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

10 documents, released by the NTSB on June 13, 2018. 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.