FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI08IA152 · Eclipse Aviation Corporation EA500

5 Jun 2008 · Chicago, IL, United States

Kiernan Companies Eclipse Aviation Corporation EA500 · Incident: powerplant system/component malfunction/failure on approach

From Cleveland Hopkins International Airport (CLE) to Chicago Midway International Airport (MDW)

Report a problem

Event

NTSB case
CHI08IA152
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
Incident
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
0 · 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

Eclipse Aviation Corporation EA500

Aircraft type
Eclipse EA500
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
N612KB
Onboard fatalities
Unknown
Route
From Cleveland Hopkins International Airport (CLE), Cleveland, OHTo Chicago Midway International Airport (MDW), Chicago, IL
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
Approach · VFR pattern final
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
Powerplant system/component malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft power plant
  • Organizational issues › Development

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

NTSB narrative

The flying pilot of a very light jet airplane encountered windshear and a high sink rate on approach which he arrested by applying engine power. During landing he lightly applied brakes and observed that the airplane was accelerating. The pilot initiated a go-around. The engines were at maximum power and the crew alerting system illuminated left and right engine control failure messages. The automatic power reserve armed light was also illuminated. The crew maneuvered the airplane and troubleshot the engine control fail indication using the quick reference handbook while on downwind. The right engine was shutdown and the left engine would not respond to throttle movements during the remainder of the incident flight. The crew subsequently completed the emergency landing. On scene and subsequent throttle quadrant assembly examinations showed the assembly could produce an out of specified range signal when the throttles had forward force applied to them. Diagnostic storage unit data showed both engines' full authority digital engine control (FADEC)s encountered a fault signal from the engine controls about the time of the pilot's reported application of the throttles in response to the windshear during the incident approach. The airplane's FADEC fault logic was designed to "latch" or hold the last good value when the upper specified parameter limit was exceeded. The data showed the left engine went to flight idle when the right engine was shut down in accordance with the fault logic. The airplane's design was Federal Aviation Administration (FAA) certified with that fault logic. As a result of the investigation, the National Transportation Safety Board issued two urgent recommendations to the FAA. A-08-46 recommended an immediate inspection of all throttle quadrants to ensure that pushing the throttle levers against the maximum power stops will not result in an engine control failure, and further require that any units that fail the inspection be replaced and that the replacement parts be similarly inspected. A-08-47 recommended an immediate emergency procedure for a dual engine control failure on the incident airplane model and incorporate the procedure into the airplane flight manual and quick reference handbook via an airworthiness directive.

Probable cause

The airplane manufacturer's inadequate software design requirements of the engine's full authority digital electronic controls (FADEC) fault logic that resulted in a simultaneous unrecoverable loss of thrust control on both engines when the FADEC's input data values exceeded specified ranges during the approach. Contributing to the incident was the Federal Aviation Administration's failure to recognize and correct this condition during the certification of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08IA152
Event ID
20080612X00845
Case number
CHI08IA152
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, damage. 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: 3bf438bf5c02f8ba88cfcd7416dabe7d3cab4e4395832cd2daf0c4e4bfd1717f; retrieved 2026-09-15T09:45:39.949Z.