FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20FA019 · Raytheon A36

20 Nov 2019 · San Marcos, TX, United States

Caroline Aviation Raytheon A36 · Accident: loss of control in flight during initial climb

From San Marcos Regional Airport (KHYI) to Odessa Schlemeyer Field (KODO)

Report a problem

Event

NTSB case
CEN20FA019
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
Instrument Meteorological Cond

Raytheon A36

Aircraft type
Beechcraft 36
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
N88855
Onboard fatalities
Unknown
Route
From San Marcos Regional Airport (KHYI), San Marcos, TXTo Odessa Schlemeyer Field (KODO), Odessa, TX
Aircraft age
About 20 years (built 1999)
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

  • Not determined › Not determined
  • 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 pilot filed an instrument flight rules flight plan for the cross-country flight and received a departure clearance. A witness reported seeing the accident airplane taxi by his hangar before it departed and noted that the visibility at the time was less than the 1/4-mile reported by the airport’s weather observation facility. The airplane departed and was seen on radar before contact was lost shortly thereafter; the pilot never established radio communication with air traffic control. The airplane impacted terrain in a near-vertical attitude about 1/2-mile from the departure runway. Examination of the airplane did not reveal any pre-impact anomalies that would have precluded normal operation. Low instrument flight rules conditions prevailed in the area of the departure airport, including a cloud ceiling of about 300 ft above ground level. The airplane’s sudden descent and near-vertical impact attitude are consistent with a loss of control shortly after takeoff; however, due to a lack of onboard data and complete radar data for the flight, the reason for the loss of control could not be determined based on the available information.

Probable cause

The pilot’s loss of control shortly after takeoff in instrument meteorological conditions for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20FA019
Event ID
20191120X01106
Case number
CEN20FA019
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: 0886ef87661ecf47242a8d37f19af10b74c282b90fbc2a8513b02488a5fd8cb6; retrieved 2026-09-15T07:08:27.908Z.