Narrative:

The event occurred on aircraft X from phx to elp. The weather was clear and daytime flying. As the flight entered the elp airspace; ATC reported GPS jamming on the frequency. Runway 22 was closed; so the landing runway was 26L. The 2 approaches for this runway are RNAV(GPS) and the VOR runway 26L. The aircraft was not certified for the rnp approach. We decided on the VOR due to the GPS jamming event. As we approached into elp airspace we received an ECAM message: navigation FM/GPS position disagree. Obviously due to the jamming event. The flight was in visual/daytime conditions; thus confirming position was quickly verified. During the VOR approach; first officer was flying with autopilot on. Approximately 6-8 miles on final I noticed the flight track on captain's nd (navigation display) was starting to wander to the left. The first officer's nd was showing normal indications; but wisely decided to turn off the autopilot and continue visually. At approximately 5 miles on final; we noticed the [VNAV] was commanding a much lower altitude than what was needed to remain on a normal 3 degree flight path to landing. The first officer disregarded the false indications; and again preceded visually 3 to 1 with the VASI to and normal landing. Cause: GPS jamming probably from the whites sands missile range. Suggestions: I would highly recommend alerting crews in advance of these kind of events. This is in addition to ATIS and ATC reporting. I would highly recommend an alternate in the flight plan. If during night/IFR operations and runway 22 closed; the only means to fly an approach would be raw data VOR.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier non flying pilot reported GPS jamming while maneuvering for the arrival. Jamming was reported by ATC.

Narrative: The event occurred on Aircraft X from PHX to ELP. The weather was clear and daytime flying. As the flight entered the ELP airspace; ATC reported GPS jamming on the frequency. Runway 22 was closed; so the landing runway was 26L. The 2 approaches for this runway are RNAV(GPS) and the VOR RWY 26L. The aircraft was not certified for the RNP approach. We decided on the VOR due to the GPS jamming event. As we approached into ELP airspace we received an ECAM message: NAV FM/GPS POS disagree. Obviously due to the jamming event. The flight was in visual/daytime conditions; thus confirming position was quickly verified. During the VOR approach; First Officer was flying with autopilot on. Approximately 6-8 miles on final I noticed the flight track on Captain's ND (NAV Display) was starting to wander to the left. The First Officer's ND was showing normal indications; but wisely decided to turn off the autopilot and continue visually. At approximately 5 miles on final; we noticed the [VNAV] was commanding a much lower altitude than what was needed to remain on a normal 3 degree flight path to landing. The First Officer disregarded the false indications; and again preceded visually 3 to 1 with the VASI to and normal landing. Cause: GPS jamming probably from the Whites Sands missile range. Suggestions: I would highly recommend alerting crews in advance of these kind of events. This is in addition to ATIS and ATC reporting. I would highly recommend an alternate in the flight plan. If during night/IFR operations and Runway 22 closed; the only means to fly an approach would be raw data VOR.

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.