WPR19FA103 · Cirrus SR22
Cirrus SR22 · Accident: VFR encounter with IMC en route
From Cal Black Memorial Airport (U96) to Big Spring Mc Mahon-Wrinkle Airport (BPG)
Event
- NTSB case
- WPR19FA103
- 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
Cirrus SR22
- Aircraft type
- Cirrus SR22
- 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
- N173CT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cal Black Memorial Airport (U96), Halls Crossing, UTTo Big Spring Mc Mahon-Wrinkle Airport (BPG), Big Spring, TX
- Aircraft age
- About 11 years (built 2008)
- 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
- VFR encounter with IMC
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The noninstrument-rated pilot departed on a visual flight rules (VFR) cross-country flight. About 25 minutes after takeoff, the airplane reached its highest altitude of 17,300 ft mean sea level (msl) and was approaching a line of precipitation and thunderstorms. About 20 minutes later, the airplane entered a descent at a rate of about 1,000 ft per minute. The airplane then leveled off at an altitude of about 8,575 ft msl (about 3,000 ft above ground level), about 1,000 ft below the predicted cloud base, and a short time later, the airplane transitioned to a right descending turn that continued until ground contact, reaching a descent rate of about 5,175 ft per minute. The debris field and fragmentation of the airplane was consistent with a high-speed, right-wing-low impact. Examination of the wreckage did not reveal any anomalies with the airframe or engine that would have precluded normal operation, and there was no evidence of an inflight breakup. The airplane’s airframe parachute system was not deployed.
Analysis of weather information indicated that the airplane likely encountered a line of developing and expanding rain showers, with updraft and downdraft conditions, precipitation, and reduced visibility as the pilot likely descended to fly under the cloud bases. Due to the developing and expanding rain shower line, outflow boundaries and low-level wind shear conditions were likely present in the area at the accident time.
A convective SIGMET as well as AIRMETs for instrument flight rules conditions, mountain obscuration, and moderate icing were valid for the route of flight and in the area of the accident site at the accident time. When activating his flight plan, the pilot indicated to the weather briefer that he was aware of the AIRMETs; however, whether he was aware of the SIGMET was not determined based on the available information.
Although the pilot did not receive an official weather briefing, records suggest that he downloaded weather imagery three days before the flight. He had an active subscription to a commercial satellite weather service for the airplane, which was also equipped with multiple avionics devices capable of receiving and displaying weather information. Whether or to what extent the pilot accessed weather imagery in-flight could not be determined.
The reduced visibility and the pilot’s lack of experience in flight by reference to instruments provided conditions conducive to the development of spatial disorientation, and the airplane’s descending turn, rapid descent, and high-speed impact with the ground were consistent with the known effects of spatial disorientation. Given the available information, it is likely that the noninstrument-rated pilot encountered instrument meteorological conditions as he continued toward and subsequently attempted to fly below an area of rain shower and thunderstorm activity, and experienced spatial disorientation that resulted in a loss of airplane control.
Probable cause
The noninstrument-rated pilot's continued visual flight rules flight into an area of forecast instrument meteorological conditions, which resulted in spatial disorientation and a subsequent loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA103
- Event ID
- 20190331X20824
- Case number
- WPR19FA103
- 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, cause areas. 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: 264345e5976ac15d8f167de6fcfe822d6e736303f88e97f681141b6695648d06; retrieved 2026-09-15T06:56:08.960Z.