Narrative:

We were climbing through 40;200 feet MSL when the left display unit/ pfd failed; autopilot failed; auto throttles failed; partial failure of mfd information; yaw damp failed; there were no observed cas messages. I was hand flying and waiting to see what the total failures were so I could have the PNF run the checklist. The pilot not flying is brand new to the airplane; and the company; and to me does not and did not have a good grasp of the operations or nuances of the G5000 avionics in this airplane. He keeps believing all the advertised automation and capabilities actually work. I continue to try and mentor him and teach him this aircraft needs to be watched far more than what he is used to flying. His face looked glazed over when all this transpired; he asked me if this was normal. I was trying to get the pilot not flying (PNF) to take pictures of what was going on; knowing I frequently need pictures of the failures to give to cessna to try and come up with fixes as most failures are not able to be duplicated. The PNF could not operate my iphone camera or get the flash off his phone. So I took 3 quick one fingered pictures of what was going on. Approximately 1-2 minutes after the failure started; the left du was rebooting and all the systems were back. I was in rvsm when the failure started and all my systems were back before passing through FL410 to FL430 and ultimately FL450 due to turbulence. I tried to get the co-pilot to look for procedure in the abnormal section of the checklist but he did not understand what I meant. There were no cas messages to look up in the checklist and all systems were back to normal within 1-2 minutes so I continued the flight.this airplane has nuisance cas messages and very short failures on a regular basis that cessna can't find or fix. I feel the aircraft is safe but never trust it. I have never flown an aircraft that I did not trust before; this one is very consistent in that.after everything settled down and got to cruise altitude I sent a message to [operations]. The [group] contacted me about an hour after the event via text. I then called him on the air cell to discuss the event. After this I was reviewing the checklist abnormals. Then the PNF was looking into the paper checklist at cas messages. I believe he was looking at failures and trying to match up to a cas. He then stated he might have seen a gia amber fail and or a terrain fail amber. I asked him if he thought he saw these why did he not mention it; an hour earlier before I talked to dom; after or during the event as I was scanning all three dus for any cas messages to come on and saw none. And he; not being very familiar where to even look. I also asked him if he was sure it was not something he was reading in the checklist. He shut down and would not respond at that point for a while. We continued on uneventfully and finished our trip. The du is going to be replaced. And there is no reason we did not get any cas messages. We did not have a gia failure.

Related reports:

Google
 

Original NASA ASRS Text

Title: CE-680 Captain reported multiple failures in flight involving the MFD and other systems.

Narrative: We were climbing through 40;200 feet MSL when the left Display unit/ PFD failed; autopilot failed; auto throttles failed; partial failure of MFD information; yaw damp failed; there were no observed CAS messages. I was hand flying and waiting to see what the total failures were so I could have the PNF run the checklist. The pilot not flying is brand new to the airplane; and the company; and to me does not and did not have a good grasp of the operations or nuances of the G5000 avionics in this airplane. He keeps believing all the advertised automation and capabilities actually work. I continue to try and mentor him and teach him this aircraft needs to be watched far more than what he is used to flying. His face looked glazed over when all this transpired; he asked me if this was normal. I was trying to get the Pilot Not Flying (PNF) to take pictures of what was going on; knowing I frequently need pictures of the failures to give to Cessna to try and come up with fixes as most failures are not able to be duplicated. The PNF could not operate my iPhone camera or get the flash off his phone. So I took 3 quick one fingered pictures of what was going on. Approximately 1-2 minutes after the failure started; the left DU was rebooting and all the systems were back. I was in RVSM when the failure started and all my systems were back before passing through FL410 to FL430 and ultimately FL450 due to turbulence. I tried to get the co-pilot to look for procedure in the abnormal section of the checklist but he did not understand what I meant. There were no CAS messages to look up in the checklist and all systems were back to normal within 1-2 minutes so I continued the flight.This airplane has nuisance CAS messages and very short failures on a regular basis that Cessna can't find or fix. I feel the aircraft is safe but never trust it. I have never flown an aircraft that I did not trust before; this one is very consistent in that.After everything settled down and got to cruise altitude I sent a message to [operations]. The [group] contacted me about an hour after the event VIA text. I then called him on the air cell to discuss the event. After this I was reviewing the checklist abnormals. Then the PNF was looking into the paper checklist at CAS messages. I believe he was looking at failures and trying to match up to a CAS. He then stated he might have seen a GIA amber fail and or a terrain fail amber. I asked him if he thought he saw these why did he not mention it; an hour earlier before I talked to DOM; after or during the event as I was scanning all three DUs for any CAS messages to come on and saw none. And he; not being very familiar where to even look. I also asked him if he was sure it was not something he was reading in the checklist. He shut down and would not respond at that point for a while. We continued on uneventfully and finished our trip. The DU is going to be replaced. And there is no reason we did not get any CAS messages. We did not have a GIA failure.

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