Narrative:

A cessna citation X (C750); aircraft X; had a long history of the following message: fadec fail/fault left a/B [left fadec channel a/B fault]. This fault had first showed up after a phase inspection in ZZZ1 in january 2012 and wasn't repaired until may 2012. The message would first appear during landing after the thrust reversers were deployed. They would always deploy with no defects. During the five months the fadec fail /fault message would appear which never resulted in an engine shutdown. One of the main reasons maintenance was not able to duplicate the fault or repair it in a timely manner was the lack of required fault codes needed to find the cause of the issue at hand. The fault codes are only present while the crew alerting system (cas) message is displayed. There were a number of factors that made it difficult for the maintenance controllers to find the appropriate codes; including: new controllers; crewmembers that were unfamiliar with retrieving the codes from the intergrated maintenance computer (IMC) computer; (us) customs (telling crewmember to shut down the aircraft) and message not staying 'latched'. Approximately fifteen maintenance events happened during this time frame; as well as a number of taxi checks; test flights; and maintenance engine run-ups with thrust reversers being deployed. I first became aware of this problem as a maintenance controller in march 2012; when the aircraft broke in ZZZ2. During the following weeks I made it a point to track this aircraft. It was frustrating to hear about missed opportunities of getting the fault codes. After I started tracking this particular aircraft's progress; eight maintenance events followed. Out of those eight events; only three engine codes events were recovered; I was involved in two events. It was my familiarity with the imt which led us to look at other areas. We found that it was a wire harness issue which had been causing the problem. In may 2012; I received a call from the captain on aircraft X; telling me he had a fadec fail l-ab. I asked him if the engine had shutdown. He said; 'no'. Then I replied to him that the message you had must be a fault and he replied; 'no'; it was a fail l-ab. He told me he had to shut down the aircraft. I told him maintenance would not be able to find anything wrong with the aircraft because the message disappeared. He still felt that maintenance needed to inspect the aircraft. They found nothing wrong with the aircraft; and the next day he flew the aircraft to cessna service center. The aircraft was inspected; then taxi checked and flight tested twice with no faults found. Recommend flight crewmembers become familiar with retrieving the fault codes from the imt computer.

Google
 

Original NASA ASRS Text

Title: A Maintenance Controller reports about a design flaw in the Engine FADEC System on Cessna Citation X (C750) aircraft that does not allow 'latching'of FADEC fault messages when aircraft electrical power is removed. Lack of flight crew familiarity retrieving FADEC fault codes prior to removing electrical power limits Maintenance trouble shooting.

Narrative: A Cessna Citation X (C750); Aircraft X; had a long history of the following message: FADEC FAIL/FAULT L A/B [Left Fadec Channel A/B Fault]. This fault had first showed up after a Phase Inspection in ZZZ1 in January 2012 and wasn't repaired until May 2012. The message would first appear during landing after the thrust reversers were deployed. They would always deploy with no defects. During the five months the FADEC Fail /Fault message would appear which never resulted in an engine shutdown. One of the main reasons Maintenance was not able to duplicate the fault or repair it in a timely manner was the lack of required fault codes needed to find the cause of the issue at hand. The fault codes are only present while the Crew Alerting System (CAS) message is displayed. There were a number of factors that made it difficult for the Maintenance Controllers to find the appropriate codes; including: new Controllers; Crewmembers that were unfamiliar with retrieving the codes from the Intergrated Maintenance Computer (IMC) computer; (US) Customs (telling Crewmember to shut down the aircraft) and message not staying 'latched'. Approximately fifteen Maintenance events happened during this time frame; as well as a number of taxi checks; test flights; and maintenance engine run-ups with thrust reversers being deployed. I first became aware of this problem as a Maintenance Controller in March 2012; when the aircraft broke in ZZZ2. During the following weeks I made it a point to track this aircraft. It was frustrating to hear about missed opportunities of getting the fault codes. After I started tracking this particular aircraft's progress; eight maintenance events followed. Out of those eight events; only three engine codes events were recovered; I was involved in two events. It was my familiarity with the IMT which led us to look at other areas. We found that it was a wire harness issue which had been causing the problem. In May 2012; I received a call from the Captain on Aircraft X; telling me he had a FADEC Fail L-AB. I asked him if the engine had shutdown. He said; 'No'. Then I replied to him that the message you had must be a fault and he replied; 'No'; it was a fail L-AB. He told me he had to shut down the aircraft. I told him Maintenance would not be able to find anything wrong with the aircraft because the message disappeared. He still felt that Maintenance needed to inspect the aircraft. They found nothing wrong with the aircraft; and the next day he flew the aircraft to Cessna Service Center. The aircraft was inspected; then taxi checked and flight tested twice with no faults found. Recommend flight crewmembers become familiar with retrieving the fault codes from the IMT computer.

Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.