FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19FA104 · Israel Aircraft Industries 1124

18 Mar 2019 · Yukon, OK, United States

Sundance Airport FBO Israel Aircraft Industries 1124 · Accident: loss of control in flight during initial climb

From Northwest Florida Beaches International Airport (ECP) to Sundance Airpark (HSD)

Report a problem

Event

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

Israel Aircraft Industries 1124

Aircraft type
Israel 1124
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
N4MH
Onboard fatalities
Unknown
Route
From Northwest Florida Beaches International Airport (ECP), Panama City, FLTo Sundance Airpark (HSD), Oklahoma City, OK
Aircraft age
About 41 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
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

  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The two commercial pilots were conducting a personal, cross-country flight. A video surveillance camera at the airport captured their airplane’s approach. Review of the video revealed that, as the airplane approached the approach end of the landing runway, it began to climb, rolled left, became inverted, and then impacted terrain. The left thrust reverser (T/R) was found open and unlatched at the accident site. An asymmetric deployment of the left T/R would have resulted in a left roll/yaw. The lack of an airworthy and operable cockpit voice recorder, which was required for the flight, precluded identifying which pilot was performing pilot flying duties, as well as other crew actions and background noises, that would have facilitated the investigation. Postaccident examination of the airplane revealed that it was not equipped, nor was required to be equipped, with a nose landing gear (NLG) ground contact switch intended to preclude in-flight operation of the thrust reverser (T/R). The left T/R door was found unlatched and open, and the right T/R door was found closed and latched. Further, electrical testing of the T/R left and right stow microswitches within the cockpit throttle quadrant revealed that the left stow microswitch did not operate within design specifications. Disassembly of the left and right stow microswitches revealed evidence of arc wear due to aging. Based on this information, it is likely that the airplane’s lack of an NLG ground contact switch and the age-related failure of the stow microswitches resulted in an asymmetric T/R deployment while on approach and a subsequent loss of airplane control. Also, there were additional T/R system components that were found to unairworthy that would have affected the control of the T/R system. Operational testing of the T/R system could not be performed due to the damage the airplane incurred during the accident.

Toxicology testing results of the pilot’s specimens indicated that the pilot had taken diazepam, which is considered impairing at certain levels. However, the detected amounts of both diazepam and its metabolite nordiazepam were at subtherapeutic levels, and given the long half-life of these compounds, it appears that the medication was taken several days before the accident; therefore, it is unlikely that the pilot was impaired at the time of the accident and thus that his use of diazepam was a not factor in the accident.

Probable cause

The airplane’s unairworthy thrust reverser (T/R) system due to inadequate maintenance that resulted in an asymmetric T/R deployment during an approach to the airport and the subsequent loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19FA104
Event ID
20190318X82725
Case number
CEN19FA104
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: f3c72fc86c5752b0f208a323e21c1dba8127ffddd1e0f354ef9f15c4e60d2e3a; retrieved 2026-09-15T06:55:51.404Z.