Narrative:

I had to get a new mfd in the aircraft. After installation; the shop was reprogramming the G1000; I got the paperwork and everything appeared to be working during preflight. On an IFR clearance flying my mooney; with autopilot engaged at 8000 MSL near forss transition; I saw a conflict glider not moving in the windscreen but getting larger; on a collision course from my 11 o'clock. He was at 8000; and if I had not deviated; I would have certainly had a mid-air collision. The glider never saw me and was not talking to anyone that I'm aware of. I had no indication in the cockpit. I reported the near miss with the glider and the corresponding altitude dev. I did not hear any warning from ATC that I was in an active glider area; nor did I see any depiction on the VFR sectional in jeppesen app on my ipad. Probably missed the glider by 500 ft after taking evasive action. My concern is to keep a similar incident from occurring again. If I was heads down; I may not have been here to write this report. It would have been very valuable to get a heads up from ATC that I was in an active glider zone. I leveled back at 8000 and re-engaged the autopilot. Shortly after forss; I noticed an error with my G1000 GPS; I was stuck in GPS terminal mode instead of enroute. Then I noticed the gnss fail message on the stec autopilot. I began to troubleshoot and the autopilot decoupled from the nav mode and went into a heading mode. When I pulled out the chart I realized I was east of where I was cleared; proceeding on a 020 heading; but my clearance was [elsewhere]. I fessed up to the navigation error; and ATC gave me present position direct to zzzzz for the rest of the arrival. The rest of the flight was uneventful. My G1000 needs further programming I am now aware to prevent a similar occurrence. Now that I am aware of how this system behaves; I will know what to watch for in the future to prevent this from happening again.

Related reports:

Google
 

Original NASA ASRS Text

Title: M20 pilot reported a NMAC with a glider; followed by a G1000 malfunction.

Narrative: I had to get a new MFD in the aircraft. After installation; the shop was reprogramming the G1000; I got the paperwork and everything appeared to be working during preflight. On an IFR clearance flying my Mooney; with autopilot engaged at 8000 MSL near FORSS transition; I saw a conflict glider not moving in the windscreen but getting larger; on a collision course from my 11 o'clock. He was at 8000; and if I had not deviated; I would have certainly had a mid-air collision. The glider never saw me and was not talking to anyone that I'm aware of. I had no indication in the cockpit. I reported the near miss with the glider and the corresponding altitude dev. I did not hear any warning from ATC that I was in an active glider area; nor did I see any depiction on the VFR sectional in Jeppesen app on my iPad. Probably missed the glider by 500 ft after taking evasive action. My concern is to keep a similar incident from occurring again. If I was heads down; I may not have been here to write this report. It would have been very valuable to get a heads up from ATC that I was in an active glider zone. I leveled back at 8000 and re-engaged the autopilot. Shortly after FORSS; I noticed an error with my G1000 GPS; I was stuck in GPS Terminal Mode instead of Enroute. Then I noticed the GNSS fail message on the STEC autopilot. I began to troubleshoot and the autopilot decoupled from the nav mode and went into a heading mode. When I pulled out the chart I realized I was east of where I was cleared; proceeding on a 020 heading; but my clearance was [elsewhere]. I fessed up to the navigation error; and ATC gave me present position direct to ZZZZZ for the rest of the arrival. The rest of the flight was uneventful. My G1000 needs further programming I am now aware to prevent a similar occurrence. Now that I am aware of how this system behaves; I will know what to watch for in the future to prevent this from happening again.

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.