FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA120 · Piper PA 28-180

4 Jun 2017 · Santa Rosa Valley, CA, United States

Piper PA 28-180 · Accident: abrupt maneuver while maneuvering

From Camarillo International Airport (CMA) to Camarillo International Airport (CMA)

Report a problem

Event

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

Piper PA 28-180

Aircraft type
Piper PA-28
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
N4871L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Camarillo International Airport (CMA), Camarillo, CATo Camarillo International Airport (CMA), Camarillo, CA
Aircraft age
About 50 years (built 1967)
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
Abrupt maneuver
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The commercial pilot and his son were conducting a personal flight. About 15 minutes after takeoff, the airplane flew a series of passes over a horse arena where the pilot's daughter was riding. The arena was situated within a geographic bowl depression, surrounded by hilly terrain and adjacent to three sets of power transmission lines. A pilot witness in an airplane flying above the accident airplane described the accident airplane's flight path as low and erratic, and a witness close to the arena described the initial pass as "aggressive." The pilot conducted the final pass over the arena at a much lower altitude than the previous passes. Multiple witnesses described the engine noise as "sputtering" and then going quiet either during the descent for the final pass, or just as the airplane flew over the arena. The engine sound then increased as the airplane climbed and entered a steep right bank, then descended into power lines and impacted the ground about 600 ft south of the arena. Calculations based on witness reports and impact geometry indicated that the radius of the turn before impact would have required a high angle of bank, resulting in an increase in stall speed, which would have led to an accelerated stall at an altitude too low for recovery.

Examination revealed no anomalies with the airframe or engine that would have precluded normal operation, and damage signatures and witness accounts indicated that the engine was producing power at the time of the accident. Damage to the airplane's fuel tanks indicated that they contained fuel at the time of impact.

The pilot's son, who was not a pilot, was seated in the front left seat. Since the airplane was equipped with dual controls, it could not be determined who was flying the airplane at the time of the accident.

The pilot was familiar with the terrain in the area of the accident site. Witnesses stated that he had performed low passes there multiple times in the past and was aware of the power lines at the edge of the arena. The reduction in engine noise as reported by witnesses could have been the result of an actual loss of engine power or a power reduction made by the pilot to descend more rapidly in order to perform the pass at a lower altitude; however, if the pilot had been flying at an appropriate and safe altitude and the airplane had experienced a loss of engine power, it would have been within gliding distance of open terrain adequate for a forced landing. Given the pilot's previous behavior and the circumstances of the accident flight, it is likely that the pilot was performing an intentional, ostentatious display at low altitude when the accident occurred.

Toxicology testing of the pilot indicated the presence of multiple impairing medications, as well as tetrahydrocannabinol carboxylic acid, a metabolite of tetrahydrocannabinol (THC), the active compound in marijuana. However, no blood was available for toxicology testing, and there is no known relationship between tissue levels and impairment. As a result, whether the pilot's use of multiple potentially impairing substances contributed to the accident could not be determined.

Probable cause

The pilot's exceedance of the airplane's critical angle of attack while intentionally maneuvering in a steep bank at low altitude, which resulted in an accelerated aerodynamic stall and subsequent loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA120
Event ID
20170604X10441
Case number
WPR17FA120
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: 7fc3752752d48d2c414f4b4857cbb47b2cc1451d35ddb12baf9534bfe4d0a005; retrieved 2026-09-15T06:03:44.369Z.