FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA204 · Cirrus SR22

31 May 2018 · Midland, TX, United States

Cirrus SR22 · Accident: loss of control in flight during initial climb

From Midland International Air and Space Port (KMAF) to Sierra Blanca Regional Airport (KSRR)

Report a problem

Event

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

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
N670SR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Midland International Air and Space Port (KMAF), Midland, TXTo Sierra Blanca Regional Airport (KSRR), Ruidoso, NM
Aircraft age
About 11 years (built 2007)
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
Initial climb
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

  • Personnel issues › Action/decision

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

NTSB narrative

The student pilot and passenger were departing on a personal flight in the student pilot's airplane. Witnesses saw the airplane climb to about 200 ft above the runway at a slow airspeed, stall, and descend in a right turn until impact with terrain. According to the pilot's wife, he regularly flew the airplane, often with passengers. No pilot logbooks or records were found and the student's flight experience could not be determined. Examination of the airplane revealed no mechanical malfunctions or anomalies that would have precluded normal operation. Given the atmospheric conditions, the density altitude about the time of the accident was 6,660 ft mean sea level (msl).

Probable cause

An inadvertent stall, resulting in an uncontrollable descent and impact with terrain. Contributing to the accident was the high density altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA204
Event ID
20180531X14518
Case number
CEN18FA204
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-06-01.
  • API snapshot SHA-256: 3c539fe5c75c36095e5e7de555731b8b4d5a3f5bf4b9e8ea5a548578222cc69b; retrieved 2026-09-15T06:41:47.725Z.