Eclipse EA500 N612KB

Summary

On 5 June 2008 at about 18:00 local time, a Eclipse EA500 registered N612KB, operated by Kiernan Companies LLC, was involved in an incident near Chicago, Illinois, United States. 4 people were on board and nobody was injured. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

5 June 2008 at 18:00

Classification

Incident

Location

Chicago, Illinois, United States

Nearest airport

Chicago Midway International (MDW)

Coordinates

41.7858, -87.7525

Aircraft

Eclipse EA500

Registration

N612KB

Category

Airplane

Engines

2

Operator

Kiernan Companies LLC

Operating rule

Part 91: General Aviation

Purpose of flight

Business

Phase of flight

Not recorded

Route

Cleveland → Chicago

Aircraft damage

Not recorded

Weather

VMC

Light

Day

NTSB number

CHI08IA152

Nobody was injured.

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full 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.

Quoted verbatim from the NTSB record.