EMB-505 / Phenom 300
Flight Crew Air Transport Pilot (ATP)
Troubleshooting; Distraction; Confusion; Workload
Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Aircraft; Airspace Structure; Weather
In level cruise at FL430 the PIC (pilot monitoring) noticed yellow X's over the spoiler & trim indicators. We looked at the QRH; POH & AFM as they were non-CAS message items. We called maintenance on the phone trying to gain any insight or knowledge on the issues. We discussed alternatives and whether to continue or divert and where to divert. Weather at destination was about 4 miles and 1200 ft overcast with temps near freezing and about 55 minutes away. The TAF also showed possible freezing drizzle. We discussed the possibility of ZZZ since it was closer; had better weather; a longer runway; crash-rescue available. If we continued to ZZZ1; we would've had less fuel to work with if we had to divert from ZZZ1 to our filed alternate. About the autopilot started a very mild vertical pitch oscillation and was slowly climbing. I tempered the oscillations with a little forward hand pressure. I suspected the pitch trim was NOT working. At we requested lower altitude to test the trim system. We set FL380; pressed VS (vertical speed) and dialed in a descent. The airplane did not respond. We then agreed to disconnect the autopilot and try the descent. We discovered the primary pitch trim was not working. We switched on the backup trim and that system was working. Leveling at FL380 we tried to re-engage the autopilot and it would not re-engage. At we advised ATC of our inoperative autopilot & primary pitch trim. We requested to exit RVSM airspace and to divert to ZZZ. ATC [offered priority handling and] gave us direct ZZZ and started our descent. They rolled crash-rescue and we were vectored onto ILS at ZZZ with about 2200 ft broken and 10 mile visibility. We landed uneventfully and taxied to [the FBO]. We then wrote up the maintenance issues. We did what we were trained to do. I felt we worked together well as a pilot team. We may not have accomplished every item to the 'T' however; we did expeditiously troubleshoot and then made safe; conservative decisions and choices to get the passengers; crew and plane safely on the ground. We never had any doubt of anything but a safe outcome.
At cruise FL430 received Garmin message 'FAILED PATH; A data path has failed'. Also received a yellow X on the MFD for the spoiler; and a yellow X on the MFD for the pitch control settings. Referred to the QRH and found no guidance. Referred to the POH and found the yellow X displays and decided the problem was sensor related. Call maintenance and was given little guidance for the issue. Maintenance suggested the [Chief Pilot] and transferred us over. [Chief Pilot] found the original message in the Garmin manual and agreed it was most likely a sensor issue. Autopilot was oscillating + - 100ft. We decided to descend to FL380. At that point we realized the primary trim was INOP and reverted to back up trim. Once we leveled FL380 we learned the autopilot was INOP. We then decided to leave RVSM airspace and find a long runway which worked to be ZZZ. [Advised ATC of] flight control malfunctions and landed safely in ZZZ.One of the two FCE (flight control electronics) has failed and caused the failure of the autopilot and primary trim.
Phenom 300 flight crew reported pitch trim and autopilot failures.