Narrative:

While pushing the power up on the takeoff both engines went into reversionary mode when two of the four fadec computers dropped off line. The EICAS 'fadec rev air data computer l-r' messages came up and I aborted the takeoff. I pulled off the runway; stopped the aircraft and performed the checklist. The checklist had me reset the fadecs and the fadecs came back on line. Not knowing what caused the engine computers to malfunction; I taxied in and informed the passengers the aircraft was down for maintenance. When I called in the write up the maintenance controller answered the phone. I informed him that 'I needed to write it up and have somebody look at it.' in an attempt to pressure me to fly the aircraft; he responded; 'not if you do a reboot on it and everything is working fine.' I emphatically told him that I was not going to abort a takeoff with engine problems without having a mechanic look at the airplane and assured him that the problem was not deferrable per the MEL. He continued to pressure me in an attempt to countermand my PIC authority by stating; 'go out and try it again and it works fine; you'll be good to go.' I responded; 'sorry; I'm not going to do that.' only then did he begrudgingly acknowledge that he was going to receive my write up. I then contacted the union to file a complaint. This is the second event I have filed a report on in less than six months. I feel that the FAA should pursue enforcement action against this maintenance controller and the company for pushing pilots to violate fars by carrying non-airworthy maintenance write ups.

Google
 

Original NASA ASRS Text

Title: A CE-750 Captain complained of pressure from maintenance to accept;without a maintenance evaluation; an aircraft which had suffered a rejected takeoff due to a dual FADEC failure on the initial takeoff attempt .

Narrative: While pushing the power up on the takeoff both engines went into reversionary mode when two of the four FADEC Computers dropped off line. The EICAS 'FADEC REV ADC L-R' messages came up and I aborted the takeoff. I pulled off the runway; stopped the aircraft and performed the checklist. The checklist had me reset the FADECs and the FADECs came back on line. Not knowing what caused the engine computers to malfunction; I taxied in and informed the passengers the aircraft was down for maintenance. When I called in the write up the Maintenance Controller answered the phone. I informed him that 'I needed to write it up and have somebody look at it.' In an attempt to pressure me to fly the aircraft; he responded; 'Not if you do a reboot on it and everything is working fine.' I emphatically told him that I was not going to abort a takeoff with engine problems without having a mechanic look at the airplane and assured him that the problem was not deferrable per the MEL. He continued to pressure me in an attempt to countermand my PIC authority by stating; 'go out and try it again and it works fine; you'll be good to go.' I responded; 'Sorry; I'm not going to do that.' Only then did he begrudgingly acknowledge that he was going to receive my write up. I then contacted the Union to file a complaint. This is the second event I have filed a report on in less than six months. I feel that the FAA should pursue enforcement action against this Maintenance Controller and the company for pushing pilots to violate FARs by carrying non-airworthy maintenance write ups.

Data retrieved from NASA's ASRS site as of April 2012 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.