CE-700 Captain reported several crew alerting system (CAS) messages during cruise flight and again during landing.
Synopsis
CE-700 Captain reported several crew alerting system (CAS) messages during cruise flight and again during landing.
Narrative
On climb out between FL420 and FL430 at approximately 0.83M; while circumventing thunderstorms; we encountered cascading CAS (Crew Alert System) messages. These included the loss of AOA; stick pusher; auto-throttles and GPS. Also; during landing roll other CAS messages are triggered. I later found out that this error was a known issue by Company Maintenance; the Company Director and Textron. It appears like a serious safety issue is being actively hidden from the line pilots. This error causes a serious degradation of capabilities for not an insignificant amount of time. The fact that such a safety of flight known issue was not distributed to the line pilots is a serious safety concern. After landing; I was directed by maintenance to power cycle the plane. I discussed the use of the QRH Power Up Anomalies (On Ground Only) Checklist for this; as it is the closest checklist item I could find. We used it; with the approval of Maintenance; even though we did not just power up the plane. Suggestions: Re-booting the computer after landing is not a fix; it is a Band-Aid covering up a significant problem. The location of this computer glitch; like on short final in IMC near obstacles; could be disastrous. The fleet should be seriously limited in its operations until this problem is fixed. Also; as a known issue; there should be a checklist that directs me to power cycle the plane.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.