FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19FA004 · Piper PA32RT 300

12 Oct 2018 · Poolville, TX, United States

Piper PA32RT 300 · Accident: loss of control in flight en route

From Sierra Blanca Regional Airport (SRR) to Hicks Air Field (T67)

Report a problem

Event

NTSB case
CEN19FA004
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 PA32RT 300

Aircraft type
Piper PA32
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
N221MC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sierra Blanca Regional Airport (SRR), Ruidoso, NMTo Hicks Air Field (T67), Fort Worth, TX
Aircraft age
About 40 years (built 1978)
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 · descent
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
  • Aircraft › Aircraft structures
  • Personnel issues › Psychological

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

NTSB narrative

The pilot and passenger departed on the cross-county flight in visual meteorological conditions. Automatic dependent surveillance-broadcast (ADS-B) and GPS data indicated that, after takeoff, the airplane proceeded east and that, for most of the flight, flew at altitudes that were between 8,500 and 9,500 ft mean sea level (msl). However, as the flight progressed, the weather conditions deteriorated. Toward the end of the flight, the airplane began descending from 9,000 ft msl at a descent rate of about 700 ft per minute. The airplane then entered a descending right turn with a decreasing radius before the ADS-B and GPS data ended. The radius of the turn was initially about 4,000 ft and decreased during the next minute to about 1,000 ft by the final 1 second of the data. As the airplane continued to turn, the descent rate increased; the average rate of descent of the airplane for the final 10 seconds of the recorded ADS-B data was about 12,900 ft per minute.

The airplane wreckage was distributed over a large area with airframe parts located 3,600 ft from the main wreckage location and lighter-weight items from within the airplane located more than 1 mile away. The wreckage distribution indicated that the airplane broke apart during flight and before contacting the ground. Examination of the airframe and engine revealed no anomalies consistent with a prebreakup failure or malfunction.

Weather data indicated that marginal visual flight rules conditions prevailed across the area with ceilings overcast from 2,500 to 3,000 ft agl. Several weather stations immediately north and north-northeast of the accident site reported instrument flight rules (IFR) conditions to low IFR conditions, indicating ceilings of less than 1,000 ft agl and/or visibilities of less than 3 miles. No breaks in the overcast layer of clouds were reported surrounding the time of the accident, so the pilot's visual flight into IMC would have been conducive to the development of spatial disorientation.

The pilot held an instrument rating, but a review of his flight logbook revealed that he had logged a total of only 2.3 hours of actual instrument flight experience, including 0.2 hour during the 3 months preceding the accident. As a result, the pilot did not likely possess the experience or recency to adequately control the airplane through the use of the instruments in IFR conditions. Thus, it is likely that the pilot experienced spatial disorientation during an encounter with IMC, which progressed into a graveyard spiral (as indicated by the tightening of the turn) and a subsequent loss of control.

Probable cause

The pilot's loss of airplane control as a result of spatial disorientation and the exceedance of the structural capabilities of the airplane. Contributing to the accident was the pilot's limited experience in instrument conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19FA004
Event ID
20181013X10104
Case number
CEN19FA004
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: 51c6ee89d8643265d742fd10d9dfd8468a6258e6ba757a600e0d3d0894f6445d; retrieved 2026-09-15T06:49:24.965Z.