FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA041 · Petrus David Wayne S90

26 Dec 2016 · Fresno, CA, United States

Petrus David Wayne S90 · Accident: loss of control in flight during initial climb

From Sierra Sky Park Airport (E79) to Sierra Sky Park Airport (E79)

Report a problem

Event

NTSB case
WPR17FA041
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

Petrus David Wayne S90

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
N176PA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sierra Sky Park Airport (E79), Fresno, CATo Sierra Sky Park Airport (E79), Fresno, CA
Aircraft age
About 12 years (built 2004)
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
Initial climb
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
Loss of control in flight
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
  • Not determined › Not determined
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot began flight training in 1996 and had accrued about 187 total hours of flight experience by 2012, mostly in low-performance Cessna and Piper airplanes. The pilot then ceased flying until mid-2016, when he purchased the previously-owned experimental amateur-built, high-performance accident airplane.

In late 2016, when he had accrued about 31 hours of flight experience in the airplane, the pilot and a non-pilot rated passenger departed for a local personal flight. Weather conditions were benign, with light winds, clear skies, and moderate temperature. According to multiple witnesses, some of whom were pilots, the airplane entered a steep climb at some point after it lifted off. The airplane then began a sharp right turn while continuing to climb rapidly. Shortly thereafter, the airplane entered a steep descent and impacted marshy terrain about 900 ft to the northeast of the departure end of the runway.

A flight path reconstructed from data recovered from an onboard GPS device indicated a trajectory that was similar to that indicated by the witness accounts. GPS-derived comparison of the profile of the accident takeoff with those of seven of the pilot's other takeoffs in the airplane from the accident airport revealed that five of the other seven takeoff profiles were similar to one another, and that the accident takeoff profile was markedly different from those five. During the accident takeoff, the airplane remained on or near the ground about 25 seconds longer than it did during those five other takeoffs, and then climbed at a rate that was about twice the rates of those five takeoffs. The other two takeoffs exhibited ground or near-ground travel durations of about 40 seconds, with climb rates similar to those of the other five takeoffs.

Postaccident examination of the engine and airframe did not reveal evidence of any pre-impact mechanical deficiencies or failures that would have precluded normal operation, and the damage was consistent with the engine developing at least moderate power at impact. The airplane was equipped with dual flight controls, but the investigation was unable to determine who was manipulating the controls for the takeoff and flight. The relative sizes of the two occupants were not consistent with the passenger being able to overpower the pilot on the flight controls. The takeoff profile was consistent with an aggressive, more exciting technique sometimes referred to as a "high-performance" or "zoom climb" takeoff. The investigation was unable to determine the reason for this takeoff profile that was uncharacteristic from previous departures. The investigation was also unable to determine the reason(s) for the right turn/roll and departure from controlled flight.

Probable cause

The pilot's abnormally steep takeoff climb followed by a loss of control and rapid descent to ground impact, for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA041
Event ID
20161226X80840
Case number
WPR17FA041
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. 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: 6b690a7e686725e69e9329fd06b00e47ab1e96a038d82e7093fc36704add1ced; retrieved 2026-09-14T22:04:43.291Z.