FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA315 · Piper PA 22-150 160

9 Aug 2017 · Las Vegas, NM, United States

Piper PA 22-150 160 · Accident: aerodynamic stall/spin en route

From Dalhart Municipal Airport (DHT) to Santa Fe Municipal Airport (SAF)

Report a problem

Event

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

Piper PA 22-150 160

Aircraft type
Piper PA-22
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
N3664Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Dalhart Municipal Airport (DHT), Dalhart, TXTo Santa Fe Municipal Airport (SAF), Santa Fe, NM
Aircraft age
About 57 years (built 1960)
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
En route · cruise
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

  • Personnel issues › Physical

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

NTSB narrative

**This report was modified on March 15, 2022. Please see the public docket for this accident to view the original report.** The private pilot departed on a cross-country flight in day visual meteorological conditions. When he did not arrive at his destination as planned, a search was initiated, and the airplane was subsequently located in wooded, mountainous terrain near a private airport about 73 miles short of the destination. The orientation of the wreckage was consistent with the airplane impacting terrain following an aerodynamic stall. Examination of the airplane and engine did not reveal any anomalies that would have precluded normal operation, and there was evidence of fuel at the accident site.

The pilot was not in contact with air traffic control during the flight. Radar information showed the airplane maneuvering near the airport before radar contact was lost; the pilot may have been attempting to divert to the airport when the accident occurred. An autopsy of the pilot revealed severe coronary artery disease with 90% stenosis of the left coronary artery as well as evidence of scarring from a previous heart attack. Each of these conditions placed the pilot at significantly increased risk for the sudden development of symptoms from an acute cardiac event. Although the pilot might have decided to divert because he was impaired or incapacitated by the symptoms of an acute cardiac event, this scenario could not be corroborated by any operational evidence. The airplane’s flight track indicated that the pilot maneuvered the airplane into a “bowl” area that included the runway. Afterward, the pilot flew a right downwind leg and turned too closely onto the base leg to complete the base-to-final turn. As a result, the pilot made a 270° left turn inside the rim of the bowl area to align with the runway. As the pilot made the base-to-final turn, he again turned the airplane too closely to complete the turn, most likely because he allowed the bowl area to define the dimensions of the turn. Because of the unnecessary tightness of the turn and the steep bank angle that was required to prevent overshooting the runway, the airplane’s critical angle of attack was exceeded, resulting in an accelerated stall (which has load factors above 1 G and a stall speed higher than the airplane’s 1-G stall speed) and a subsequent loss of control of the airplane. The pilot’s logbook revealed that he logged almost all his 344 hours of total flight experience during or before 2007, with most of those hours logged between 1983 and 1992. Thus, the gap in the pilot’s flight experience, his limited recent flight experience, and the limited instruction that he received after purchasing the accident airplane did not prepare him for the challenges associated with the planned flight or the diversion.

Probable cause

The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering to land, which resulted in an accelerated stall and the pilot’s subsequent loss of control. Contributing to the accident was the gap in the pilot’s flight experience, his limited recent flight experience, and his limited instruction in the accident airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA315
Event ID
20170813X45713
Case number
CEN17FA315
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: 8e43b2d3cf3fda973a6d86a5fb6693f17e0e2823bc709213d9033641add5c39f; retrieved 2026-09-15T06:13:12.943Z.