FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA300 · Israel Aircraft Industries 1124A

18 Jun 2014 · Huntsville, AL, United States

Synfuels Holdings Finance Israel Aircraft Industries 1124A · Accident during takeoff

From Huntsville International Airport (HSV) to Huntsville International Airport (HSV)

Report a problem

Event

NTSB case
ERA14FA300
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
Visual Meteorological Cond

Israel Aircraft Industries 1124A

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
N793BG
Onboard fatalities
Unknown
Route
From Huntsville International Airport (HSV), Huntsville, ALTo Huntsville International Airport (HSV), Huntsville, AL
Aircraft age
About 31 years (built 1983)
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
Takeoff
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
Miscellaneous/other
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
  • Not determined › Not determined

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

NTSB narrative

A pilot proficiency examiner (PPE) was using the airplane to conduct a pilot-in-command (PIC) proficiency check for two company pilots. Before the accident flight, one of the two company pilots on board received a PIC proficiency check, which terminated with a full-stop landing and reverse thrust application; no discrepancies with either thrust reverser were discussed by either flight crewmember. The pilot being examined then left the cockpit, and the accident pilot positioned himself in the left front seat while the PPE remained in the right front seat. The flight crew then taxied to the approach end of the runway to begin another flight.

Data from the enhanced ground proximity system (EGPWS) revealed that, the flight began the takeoff roll with the flaps retracted, the thrust reversers armed, and both engines stabilized at 96 percent N2. About 2 seconds later, the cockpit voice recorder (CVR) recorded the "V1" call while on the airplane was on the runway; acoustic analysis indicated that the N2 speed of one engine, likely the right, decreased; the N2 speed of the other engine remained constant. This decrease in N2 speed was consistent with the PPE retarding right engine thrust to flight idle with the intent of simulating an engine failure. The takeoff continued, and, while the airplane was in a wings-level climb at an airspeed of 148 knots about 18 ft radar altitude, the CVR recorded the pilot command that the landing gear be retracted. The landing gear remained extended, and, about 1 second after the command to retract the landing gear, or about 3 seconds after becoming airborne, while about 33 ft above the runway and at the highest recorded airspeed of 149 knots, the CVR recorded the beginning of a rattling sound, which was consistent with the deployment of the right thrust reverser, and it continued to the end of the recording.

About 1.5 seconds after the rattling sound began, the CVR recorded the PPE asking, "…what happened," which indicates that the deployment was likely not annunciated in the cockpit. The right engine N2 speed continued to gradually decrease, and the airplane rolled slightly left, back to a wings-level position. The airplane continued climbing with the landing gear extended as pitch changes continued to occur. During this time, the flight crew exchanged comments about their lack of understanding about what was occurring. While flying 10 knots above V2 speed with the left engine N2 speed remaining steady and the right engine N2 speed decreasing at a slightly greater rate than previously, the airplane began a right roll with a corresponding steady decrease in airspeed from about 144 knots. About 9 seconds after the original call to retract the landing gear, the CVR recorded the PPE requesting that the landing gear be retracted, which occurred 1 second later. The airplane then continued in the right turn with the airspeed steadily decreasing, and about 11 seconds after the PPE asked "…what happened", the EGPWS sounded a bank angle alert. At that time, the airplane was in a right roll of about 30 degrees, and the airspeed was about 132 knots. The right roll continued to a maximum value of about 39 degrees, which was the last valid bank angle value recorded.

The airplane impacted the ground off the right side of the runway in a nose- and right-wing-low attitude. The landing gear and flaps were retracted, and there was no evidence of preimpact failure or malfunction of the flight controls for roll, pitch, and yaw; nor was there any evidence of a mechanical failure or malfunction of either engine. A definitive reason for the deployment of the right thrust reverser could not be determined. No previous instances of inadvertent in-flight thrust reverser deployment were documented by the operator of the accident airplane or by the airframe manufacturer for the accident airplane make and model.

Certification flight testing of an airplane with the same thrust reverser system determined that the airplane remained controllable with the right thrust reverser deployed and throttle retarder system functioning. The flight testing also included application of a momentary, peak burst of right engine thrust, again with no controllability issues noted. It was also noted that with the installed throttle retarder system, in the event of inadvertent thrust reverser deployment, that the engine's thrust should have been reduced to idle within 4 to 8 seconds. Acoustic analysis of the accident flight indicated that the lowest recorded N2 rpm value was about 84 percent and that the reduction in rpm occurred over a period of about 8.5 seconds, after the right thrust reverser deployed. No determination could be made as to why the throttle retarder system did not reduce the right engine thrust to flight idle as designed. Additionally, no determination could be made as to why the flight crew was not able to maintain directional control of the airplane following deployment of the right thrust reverser.

Although the PPE had severe coronary artery disease, which placed him at risk for an acute coronary event that would cause symptoms like chest pain, shortness of breath, or sudden unconsciousness, the CVR recorded no evidence of impairment. Neither the heart disease nor the medications he was taking to treat it would have impaired his judgement or physical functioning. Therefore, it is unlikely any medical condition or substance contributed to the PPE's actions. Additionally, there was no evidence that any medical condition would have impaired judgement or physical functioning of the pilot being examined.

Probable cause

The flight crew's inability to maintain airplane control during initial climb following deployment of the right thrust reverser for reasons that could not be determined because postaccident examination of the airframe and engine thrust reverser system did not reveal any anomalies. Contributing to the accident was the excessive thrust from the right engine with the thrust reverser deployed for reasons that could not be determined during postaccident examinations and testing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA300
Event ID
20140618X63251
Case number
ERA14FA300
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. 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: 29cbb0a1fcb444ed0226ce7337295a0c58a78592bd23b742684c690bd4d85f41; retrieved 2026-09-14T17:19:57.903Z.