Challenger 350
Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Diverted
Aircraft; Company Policy
While at cruise Altitude of FL400 ATC requested us to descend to FL380 for traffic and in preparation of descent for STAR crossing Alt. Shortly after reaching new assigned altitude we had an autopilot and transponder failure. We notified ATC that we needed to leave RVSM airspace due to these failures. They cleared us to FL280. Upon descent approximately FL340 we started having intermittent other failures; Including Stab trim fail; FLT Spoilers Fault; flaps fault; engine thrust fault; engine fault; rudder limit fault; and xpdr standby CAS. Also the Comms and all Navs were intermittent failed and yellow in color. We discussed declaring an emergency but at that point it was just autopilot inop and intermittent loss of transponder and primarily COM 2. We alerted ATC of all that was going on and that although we could communicate fine with them; that changing frequencies was an issue. Through trouble shooting we realized we could alternate between com 1 and com 2 so we continued. (All the CAS msgs seemed to be nuisance and not actual failures accept AP and COMMs as described above. At some point [my FO (First Officer)] told ATC (while I was coordinating with OPS and the owner) that we were having navigation issues so they started giving us headings (actually the Pilot side of Long Range Navs were working fine). We were given a series of headings and reported our altitude every time we were giving a change. We were in contact with our ops and maintenance and decided to change destination. We made the change with ATC then were given a new arrival; after putting STAR in FMS we were asked if we could navigate to a fix; we said yes and did so. By now both comms were almost unusable; ATC [coordinated handling with us]; we agreed and gave them our Cell #. We could not locate the SAT phone # and it was getting too busy to continue to search for it. ATC vectored us to the runway where we were able to contact tower and were cleared to land. All systems before landing seemed to work fine except flight spoilers and comms. We ran all the checklists we could think of and discussed possible failures upon landing (primarily ground spoilers and brakes). Upon landing the ground spoilers did not deploy. I told PF (Pilot Flying) that they did not deploy and to wait on brakes. I applied forward pressure on controls and moved spoilers to EMER position to get some weight on wheels while PF deployed TR's (Thrust Reversers) and eventually applied brakes. After landing we were given taxi instructions from Tower and were able to taxi to parking with no other issues. The issues we had showed themselves while on the ground prior to departure. We talked to our Maintenance department and tried the Ctrl/Alt/Delete approach to clearing these messages; along with some other suggestions. There were no items in the current Fault before or after rebooting plane. In discussions with MX they said if there is no current fault page or CAS MSG they would just have to say could not duplicate and dispatch anyway if it didn't happen while they were looking at it. Looking back we had to do this 'reset' more than one time to clear the CAS messages. I understand the 300/350 has some issues with needing to clear 'nuisance msgs' My suggestion would be that if you have to 'REBOOT' more than once the plane should be downed until it can be investigated more thoroughly.
Challenger-350 Captain reported experiencing multiple flight display; cockpit instrumentation and navigation malfunctions during cruise flight.