CEN20FA093 · Beech 200
TLC AIr Beech 200 · Accident: loss of control in flight en route
From Abilene Regional Airport (KABI) to Valley International Airport (KHRL)
Event
- NTSB case
- CEN20FA093
- 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
- 3 · 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
Beech 200
- Aircraft type
- Beechcraft 200
- 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
- N860J
- Operator
- TLC AIr
- Onboard fatalities
- Unknown
- Route
- From Abilene Regional Airport (KABI), Abilene, TXTo Valley International Airport (KHRL), Harlingen, TX
- Aircraft age
- Not recorded
- 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
- 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 › 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 two passengers departed on an instrument flight rules cross-country flight in night instrument meteorological conditions (IMC).
The pilot was instructed by air traffic control to climb to 12,000 ft, and then cleared to climb to FL230. The pilot reported to the controller that the airplane encountered freezing drizzle and light rime icing during the climb from 6,500 ft to 8,000 ft mean sea level (msl).
As the airplane climbed through 11,600 ft msl, the pilot reported that they had an issue with faulty deicing equipment and needed to return to the airport. The controller instructed the pilot to descend and cleared the airplane back to the airport. When asked by the controller if there was an emergency, the pilot stated that they “blew a breaker,” and were unable to reset it.
As the controller descended the airplane toward the airport, the pilot reported that they were having issues with faulty instruments. At this time, the airplane was at an altitude of about 4,700 ft. The controller instructed the pilot to maintain 5,000 ft, and the pilot responded that he was “pulling up.” There was no further communication with the pilot.
Review of the airplane’s radar track showed the airplane’s departure from the airport and the subsequent turn and southeast track toward its destination. The track appeared as a straight line before a descending, right turn was observed. The turn radius decreased before the flight track ended.
The airplane impacted terrain in a right-wing-low attitude. The wreckage was scattered and highly fragmented along a path that continued for about 570 ft.
Examination of the wreckage noted various pieces of the flight control surfaces and cables in the wreckage path. Control continuity could not be established due the fragmentation of the wreckage; however, no preimpact anomalies were found. Examination of the left and right engines found rotational signatures and did not identify any pre-impact anomalies.
A review of maintenance records noted two discrepancies with the propeller deice and surface deice circuit breakers, which were addressed by maintenance personnel. Impact damage and fragmentation prevented determination of which circuit breaker(s) the pilot was having issues with or an examination of any deicing systems on the airplane. The radio transmissions and transponder returns reflected in the radar data indicate that the airplane’s electrical system was operational before the accident.
It is likely that the pilot’s communications with the controller and attempted troubleshooting of the circuit breakers introduced distractions from his primary task of monitoring the flight instruments while in IMC.
Such interruptions would make him vulnerable to misleading vestibular cues that could adversely affect his ability to effectively interpret the instruments and maintain control of the airplane. The pilot’s report of “faulty instruments” during a decreasing radius turn and his initial distraction with the circuit breakers and radio communications is consistent with the effects of spatial disorientation.
Probable cause
The pilot’s loss of airplane control due to spatial disorientation. Contributing to the accident was the pilot’s distraction with a “popped” circuit breaker and communications with air traffic control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20FA093
- Event ID
- 20200220X10054
- Case number
- CEN20FA093
- 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, 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: 648b3aa56f5e2705894477c301aef832e9bc8d3095006ee256b9e3b6e7ed5b1c; retrieved 2026-09-15T07:12:00.584Z.