FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR16FA064 · North American F51 D

5 Feb 2016 · Maricopa, AZ, United States

North American F51 D · Accident: aerodynamic stall/spin while maneuvering

From Stellar Airpark (P19) to Stellar Airpark (P19)

Report a problem

Event

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

North American F51 D

Aircraft type
North American F51
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
N551JP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stellar Airpark (P19), Chandler, AZTo Stellar Airpark (P19), Chandler, AZ
Aircraft age
About 72 years (built 1944)
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
Aerodynamic stall/spin
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 › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial pilot and pilot-rated passenger took off during the morning for a personal flight to perform aerobatic maneuvers in the World War II fighter airplane. Witnesses reported seeing the airplane performing acrobatic maneuvers. The airplane was last observed by the witnesses descending in a nose-down spiral until it impacted the ground, where a postimpact fire ensued. All the witnesses that commented about the airplane's engine stated that they heard the engine running during the nose-down spiraling descent, and some of the witnesses stated that they heard a change indicating that the engine was going from full power to a lower power setting. Postaccident examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

A performance study based on radar data indicated that the airplane climbed rapidly from 5,700 to 7,700 ft mean sea level (msl), which required a significant nose-up attitude and a climb rate of over 8,000 ft per minute. It is likely that the airplane's airspeed slowed at the top of the climb and that the airplane experienced an accelerated stall and entered a spin.

According to the airplane flight manual (AFM), power-on spins should never be intentionally performed in this airplane and recovery from a power-on spin required that the pilot close the throttle completely and apply controls for recovery. The manual stated that "after the rudder is applied for recovery, between 9,000 to 10,000 ft of altitude is lost." However, the maximum radar recorded altitude of 7,700 ft msl was about 6,426 ft above ground level; therefore, there was insufficient altitude available to recover the airplane from a spin. Further, the change in engine sound heard by some of the witnesses was consistent with the closing of the airplane's throttle during a power-on spin recovery as called for by the AFM.

Although ethanol was detected in the pilot's tissue samples, the levels detected were not consistent with levels expected from ingestion, which suggests that the ethanol may have been from postmortem production. Further, the level detected in the liver was below that generally considered impairing. Therefore, given the low levels of ethanol detected, some or all which may have resulted from postmortem production, it is unlikely the ethanol detected impaired the pilot at the time of the accident.

The pilot's medical records indicated that he had a history of atrial fibrillation that resulted in an embolic stroke about 4 years before the accident. The neurological deficits from the stoke had resolved, and his heart disease had been effectively treated with no evidence of recurrence. Therefore, there was no evidence that the pilot's medical condition contributed to the accident.

Probable cause

The pilot’s failure to maintain airplane control while performing an acrobatic maneuver and his subsequent failure to recover from an inadvertent spin due to insufficient altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16FA064
Event ID
20160205X52131
Case number
WPR16FA064
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: 6d73c563639d18f7c802005cd08b68dfd6c047d7acba92ef99908923fb29a489; retrieved 2026-09-14T21:40:58.159Z.