Flight crew reported concerns over maintenance practices during an engine parameter exceedance event.

Date: 2002-06 · Aircraft: Falcon 7X · Phase: ground

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-maintenance|deviation-discrepancy-procedural-published-material-policy

Synopsis

Flight crew reported concerns over maintenance practices during an engine parameter exceedance event.

Narrative

During climb out from ZZZZ-ZZZ; CAS (Crew Alert System) message ENG2: PARAM EXCEED annunciation came on; Immediately reduced power and accomplished abnormal checklist; continued to destination because checklist stated no further action required as all parameters were returned to normal. After arrival in ZZZ; contacted Company Maintenance and advised of occurrence. After discussion of issue with Maintenance on phone and other pilot it was decided that since there were no faults recorded in the CMC; no log book discrepancy write up or Maintenance would be required prior to next flight. While investigating a separate aircraft discrepancy that occurred on flight ZZZ-ZZZ1. Company Mechanic advised me that a write up is required for the ENG2: PARAM EXCEED. We then contacted NAME and NAME1 to discuss issue. Aircraft was taken out of service; discrepancies were written up and maintenance arrangements were made. Subsequent investigation revealed that the exceedance is within the transient limit and no maintenance action is required.There should be a CAS amber warning prior to reaching limits not after. A call out and response for power reduction after flaps clean up. If foreseen; pre takeoff brief to include possible distractions at low altitudes during climb out and actions to counter. Example; avoiding Towering Cumulus or VFR traffic.

Second reporter narrative

I was the SIC (Second in Command) PM (Pilot Monitoring) departed ZZZZ initial climb; ENG 2: PARAM EXCEED CAS (Crew Alert System) displayed for about 1 second during climb. PF (Pilot Flying) commented that power levers were in TO and promptly set climb thrust. Performed checklist for ENG 2 PARAM EXCEED. Checklist stated NO FURTHER ACTION REQUIRED. Normal flight and landing at ZZZ; called Company Maintenance tech assigned this aircraft. I thought that ENG 2: PARAM EXCEED CAS was related to 5 minutes TO thrust limitation and believed that to be a PWC ESP warranty issue. I communicated my thought to MX (Maintenance) Tech and PIC (Pilot-in-Command). CMC was checked and found to be clear. PIC and MX concurred that aircraft was good to dispatch; continued with 91 repositioning flight to ZZZ1 for tail end of charter planned in two days. On approach to ZZZ1; ENG 3: OIL CHIP fault message appeared. Reported ENG 3 fault to MX Tech and following research of ENG 3 discrepancy; MX Tech called back to say that the ENG 2: PARAM EXCEED fault also required maintenance. MX Tech conference called Company MX Director NAME and we discussed issue. Pilots tried Company Chief Pilot first and then Company Assistant Supervisor NAME1; discussed issue. PIC entered discrepancies into FML and aircraft removed from service for MX. Dassault should change checklist to avoid statement like NO FURTHER ACTION REQUIRED. MX and flight crew will reference E-DG for all fault messages for dispatch decision.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.