WPR16FA169 · Boeing A75N1(PT17) UNDESIGNAT
Boeing A75N1(PT17) UNDESIGNAT · Accident: low altitude operation/event while maneuvering
From Madras Municipal Airport (S33) to Madras Municipal Airport (S33)
Event
- NTSB case
- WPR16FA169
- 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
- 1 · 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
Boeing A75N1(PT17) UNDESIGNAT
- Aircraft type
- Boeing A75
- 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
- N999PP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Madras Municipal Airport (S33), Madras, ORTo Madras Municipal Airport (S33), Madras, OR
- Aircraft age
- About 75 years (built 1941)
- 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 · aerobatics
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA169
- Event ID
- 20160827X12409
- Case number
- WPR16FA169
- 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: e819239a288c6fb62a3ebf19563012859a04135ce5761a3e6140d3371eb0cd39; retrieved 2026-09-14T21:59:00.506Z.