Narrative:

[We] were repositioning to bvy. The weather was overcast 500' with adequate visibility. The approach in use at bvy was RNAV 34. Shortly after passing wusup (the FAF) inbound; the aircraft GPS lost all signal and we consequently executed a missed approach. Upon being handed off to boston approach; we were vectored to lwm VOR. During this time; I pulled up the GPS status page to see that the unit wasn't communicating with any satellites. After approximately five minutes at 3000 feet; the unit started to receive signals and it came back online. After assuring we had raim [receiver autonomous integrity monitoring] a second time; we decided to try the approach again and encountered the same problem. For our third approach; we attempted the localizer 16 because I thought there was either a signal issue or something wrong with our GPS. We were unable to complete the approach due to low ceilings. After executing the missed approach for the localizer 16; I decided to return the aircraft to base unable to get into bvy and unaware of the GPS's issue. During these approaches; I did inquire to tower about the GPS signal loss and asked if there were any other reports of a similar issue. Towers response was that we were the first to attempt the approach for the day. It wasn't until swapping airplanes that I learned of the GPS signal issues in the area. There were no notams to this effect. It should also be noted that after swapping airplanes; we did return to bvy and flew the RNAV 16 approach without issue. However; as we were exiting runway 16 at taxiway a; the GPS lost all signal.

Google
 

Original NASA ASRS Text

Title: PC12 Captain experiences the loss of GPS signal; inside the FAF; on two consecutive RNAV 34 approaches to BVY and the flight returns to the departure airport. Although no NOTAMs were in effect; the reporter learned of GPS signal issues in the area.

Narrative: [We] were repositioning to BVY. The weather was overcast 500' with adequate visibility. The approach in use at BVY was RNAV 34. Shortly after passing WUSUP (the FAF) inbound; the aircraft GPS lost all signal and we consequently executed a missed approach. Upon being handed off to Boston Approach; we were vectored to LWM VOR. During this time; I pulled up the GPS Status page to see that the unit wasn't communicating with any satellites. After approximately five minutes at 3000 feet; the unit started to receive signals and it came back online. After assuring we had RAIM [Receiver Autonomous Integrity Monitoring] a second time; we decided to try the approach again and encountered the same problem. For our third approach; we attempted the LOC 16 because I thought there was either a signal issue or something wrong with our GPS. We were unable to complete the approach due to low ceilings. After executing the missed approach for the LOC 16; I decided to return the aircraft to base unable to get into BVY and unaware of the GPS's issue. During these approaches; I did inquire to Tower about the GPS signal loss and asked if there were any other reports of a similar issue. Towers response was that we were the first to attempt the approach for the day. It wasn't until swapping airplanes that I learned of the GPS signal issues in the area. There were no NOTAMs to this effect. It should also be noted that after swapping airplanes; we did return to BVY and flew the RNAV 16 approach without issue. However; as we were exiting Runway 16 at Taxiway A; the GPS lost all signal.

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.