Corporate jet Captain reported GPS jamming in ZBW airspace. The jamming began as another aircraft passed overhead and lasted approximately five minutes.
Synopsis
Corporate jet Captain reported GPS jamming in ZBW airspace. The jamming began as another aircraft passed overhead and lasted approximately five minutes.
Narrative
We were cruising at FL410 (+/- XA21z) enroute to HYA - ZZZ. Aircraft Y was crossing our path (right to left at at 30*-40* angle at FL430) and just as he crossed directly overhead; the first of many CAS (Crew Alerting System) messages illuminated to include: in order of occurrence: White CAS= Turn Coordinator then AT FAIL; followed by many Amber CAS too many to remember; however I believe Avionics Fail then; GPS Both on 2 on lower left PFD (Primary Flight Display). I notified ATC of the event and asked if there were any other planes reporting GPS jamming event or if any anomalies from military. I was talking to Boston Center VHF. He stated we were the first to report such event; and they were not aware of any issues. I pulled up GPS POSITION DATA and #1 GPS was all blanks. The messages cleared and GPS #1 came back on-line within a few minutes; and we continued flight without incident / or deviation. I quickly selected HDG (Heading) MODE to prevent any issue with possible Spoofing and then re-selected NAV MODE and I asked the FO to hand fly plane during the event. He did a great job maintaining altitude; course; and airspeed. I did also report this to the next ATC frequency; and the supervisor on this freq. asked a few questions for information purposes. I also asked this supervisor if they could tell me if Aircraft Y was a military aircraft...wondering if this plane had caused the event...he could only tell me it was Aircraft Y; unsure of anything else.Suggestions: Event only lasted 3-5 mins; no altitude airspeed or route issues.Upon landing rollout; we did get multiple AT Hold FAIL Red CAS msgs...I pulled the CB (Circuit Breaker) to prevent re-occurrence once we were off the runway.We shut plane down at FBO. No CAS messages were noted on return flight to ZZZ1.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.