On the afternoon of September 15, 2026, multiple aircraft reported GPS errors to John Wayne Airport (KSNA). Imagine being one of those pilots on the SNA-to-Riverside corridor: your moving map freezes, a flag pops up where your confident little airplane icon used to be, and then your CDI needle goes slack and centers on nothing. No course to follow, no confidence to display.
GA pilots rarely train for this because GPS interference and jamming used to be uncommon. It has become more prevalent in the past few years as the frequency spectrum saturates and GPS jammers proliferate. VFR and IFR pilots alike need to be aware of it and able to fall back on other navigation skills such as pilotage and VOR use. As many pilots in Southern California found out on Tuesday, GPS jamming devices were in use nearby, and as a result they lost the ability to rely on their customary navigation system.
This situation is distinct from other failures on the flight deck because your GPS didn’t hand you a confident, wrong answer. Nothing about your airplane broke. The satellites didn’t move. Your GPS simply stopped answering. That distinction is worth remembering before you read another word: real jamming rarely lies to you with a false position. It goes quiet, unless more sophisticated GPS spoofing is being employed.
Quick answer: GPS jamming is deliberate radio-frequency noise that overpowers real GPS signals, causing your receiver to lose satellite lock and its accuracy to degrade or disappear. It does not display a false position (that’s spoofing). Report it to ATC immediately, cross-check with non-GNSS sources like VOR/DME, ILS, IRS, or pilotage, stop trusting the moving map, and fly the airplane first.
What Is GPS Jamming and Why Should Pilots Care?
GPS jamming is the intentional transmission of radio-frequency noise on or near the GPS frequencies (L1 at 1575.42 MHz and L5 at 1176.45 MHz) at a power level strong enough to bury the real satellite signal your receiver is trying to hear. That real signal arrives at your antenna astonishingly weak, often compared to spotting a dim flashlight from thousands of miles away, so it doesn’t take a large or sophisticated transmitter to drown it out across a wide area. When the noise floor rises above the signal, your receiver can no longer separate satellite data from static and loses lock on some or all satellites.
Here’s a misconception worth correcting immediately, and it’s baked right into a phrase like “the magenta line lies”: jamming does not typically make your GPS display a confident, false position. That’s spoofing, a related but distinct threat covered later in this article. Jamming does something closer to the opposite. It makes your receiver lose the signal entirely, so the moving map goes quiet, flags itself, or blanks out rather than steering you somewhere wrong with a straight face. The distinction matters because your correct response differs depending on which one you’re facing: a silent, flagged GPS is telling you plainly to stop trusting it, while a spoofed GPS may be lying to you while looking perfectly healthy, arguably the more dangerous failure mode.
Pilots should care because modern general aviation and airline flying leans on GPS for far more than the moving map. WAAS approaches, ADS-B position reporting, RNAV routing, and some autopilot and terrain-awareness functions all trace back to the same GPS input. When that input degrades, several systems can misbehave together, often faster than a pilot expects from something billed as reliable.
What’s Actually Happening Near KSNA?
Scheduled military GPS-denial testing occurs at ranges from tens of nautical miles (NM) to well over a hundred NM, which means military GPS-denial activities can inadvertently reach civil traffic, especially aircraft at higher altitudes. The Southern California Aviation Users Working Group (SCAUWG) maintains a public GPS-testing digest specifically because this happens more than many pilots realize.
The key point: a test range doesn’t need to sit close to you to affect you. If you’re flying high enough, or the test’s radiated pattern points your direction, your aircraft can be affected. SCAUWG’s own guidance illustrates the mechanism plainly: testing at Mountain Home, Idaho, can affect the LA Basin at Flight Level 250 and above, while Nevada Test Center testing on similar dates can reach the Basin as low as 4,000 feet. Even though the test dates look similar on paper, the effective times and altitudes differ. SCAUWG explicitly advises pilots to confirm any digest information against current NOTAMs rather than relying on the digest alone.
This kind of leakage into civil airspace has happened before. On the night of January 29, 2026, seven ships approaching the Port of Long Beach reported GPS outages to the Los Angeles/Long Beach Vessel Traffic Service, while aircraft over the Channel Islands reported similar issues via ADS-B and NOAA CORS ground stations recorded anomalies in GPS signal-to-noise ratios. The most likely source was identified as a Point Mugu Sea Range test designated PMSRCA 26-02. If a range test can degrade GPS across a shipping lane and nearby airspace on a January night, a comparable test reaching Class C airspace over Orange County on a September afternoon fits an established pattern, not an anomaly.
For the week surrounding September 15, 2026, reports circulated of three overlapping test windows: one near Twentynine Palms roughly 110 NM east of SNA, one on the Point Mugu Sea Range roughly 80 to 90 NM west-northwest, and one near Edwards Air Force Base. The specific designators and FAASTeam notice numbers attached to those reports should be treated as a starting point for your own preflight check, not the final word. Confirm any test window you’ve heard about against the current FAASTeam advisory and NOTAM record before you brief a flight around it.
How Does GPS Interference Show Up in the Cockpit?
GPS interference shows up as a cluster of related symptoms, not one clean failure light. The FAA’s GNSS Interference Resource Guide, maintained by the Flight Technologies and Procedures Division, catalogs the cockpit cues pilots should watch for: a dropped or collapsing satellite count, a flagged loss of GPS integrity, and moving-map behavior that doesn’t match what you see outside the window or on your other instruments.
On WAAS-capable avionics, your Actual Navigation Performance or Estimated Position Uncertainty value can climb well past what your current flight phase requires, sometimes triggering an “UNABLE RNP” or similar downgrade annunciation mid-approach. ADS-B Out equipped aircraft may show a degraded Navigation Accuracy Category for Position (NACp), visible to controllers and to other properly equipped aircraft, along with position reports stretching from their normal roughly two-second interval toward much longer gaps. Autopilots coupled to GPS navigation may roll into unexpected turns chasing a corrupted or lost course, and TAWS or synthetic vision displays fed by the same degraded position can show your airplane somewhere it isn’t, even though the underlying problem is a weak or absent GPS input, not a database error.
The common thread across all of these cues: when GPS interference is present, multiple independent-seeming systems that quietly share the same GPS input start misbehaving at roughly the same time. That simultaneity is itself a clue worth trusting.
What’s the Difference Between Jamming and Spoofing?
Jamming and spoofing are not the same problem, and treating them as interchangeable is one of the most common mistakes pilots make when briefed on GPS interference. Jamming floods the GPS frequency with noise so your receiver can’t hear the real satellite signal at all. You lose lock, your accuracy figures degrade or disappear, and your system generally knows something is wrong. Spoofing is different, and more dangerous, precisely because it doesn’t announce itself the same way: a spoofer transmits a fake signal engineered to look like a valid, strong GPS signal, so your receiver may report a confident position and time that are simply wrong.
Think of it this way. Jamming is someone broadcasting static loud enough to drown out the real transmission. Spoofing is someone impersonating the tower and calmly issuing instructions you have every reason to believe. A jammed receiver often knows it’s blind. A spoofed receiver often doesn’t know it’s been fooled.
| Interference Type | What Happens to the Signal | Typical Cockpit Cue | Confidence Displayed |
|---|---|---|---|
| Jamming | Noise overpowers the real GPS signal | Loss of satellite lock, dropped satellite count, flagged GPS failure | Low confidence shown; system flags itself |
| Spoofing | Fake signal mimics a valid, strong GPS signal | Position/track disagrees with other sources; possible sudden clock jumps | High confidence shown; system may not flag itself |
| Antenna/wiring fault | No usable signal reaches the receiver | Total GPS dropout, typically isolated to one aircraft | Low confidence, single-aircraft only |
| Ionospheric scintillation | Natural signal distortion, usually near the equator or at high latitude | Intermittent accuracy degradation, regional in scope | Variable; weather- and latitude-correlated |
The FAA’s guidance on this point is direct: after any suspected jamming or spoofing event, cross-check with non-GNSS sources and be cautious about trusting GPS-derived guidance again right away, since effects can persist briefly even after the interfering signal is gone. A ground-based approach is the recommended fallback where one is available.
What Should You Do in Flight When GPS Signal Degrades or Fails?
When GPS signal degrades or fails in flight, fly the airplane first, then work the problem with non-GPS sources while keeping ATC informed. Here’s the sequence:
- Fly the airplane. Maintain attitude, altitude, and heading using your primary flight instruments before you diagnose anything. A confusing GPS display is never a reason to stop flying the aircraft.
- Report it to ATC immediately. Tell the controller what you’re seeing: loss of lock, degraded accuracy, erratic map or autopilot behavior. ATC may already be collecting similar reports, and yours becomes part of the safety record the FAA uses to track these events.
- Switch your cross-check to non-GNSS sources. Use VOR/DME, ILS/localizer, or your IRS/IRU if equipped. VFR pilots should fall back to pilotage and dead reckoning using visible landmarks.
- Stop trusting the moving map’s position, track, and groundspeed until you’ve confirmed them against an independent source.
- Reject GPS-coupled autopilot modes if the autopilot is chasing a corrupted or lost course; hand-fly or revert to heading and altitude hold modes referenced to non-GPS instruments.
- If flying an RNAV approach, be ready to abandon it for a ground-based or visual approach per your personal minimums, consistent with FAA guidance favoring ground-based approaches after suspected interference.
- After landing, file a written anomaly report so the event is documented. This is the same feedback loop that helps the FAA refine interference guidance and future test coordination. NASA’s Aviation Safety Reporting System is a recommended way to file this report.
Different aircraft and avionics suites present GPS failure differently. Always follow your specific AFM/POH and avionics supplement for the exact annunciations and recommended actions for your equipment.
How Do You Prepare for a Flight Through a Published GPS-Test Area?
You prepare by checking advisory sources before you fly, not after you notice a problem in the air. Scheduled GPS testing is published in advance through several channels, and checking them takes a few minutes during normal preflight planning.
| Source | What It Gives You | How to Access |
|---|---|---|
| FAASTeam / SPANS notices | Advance GPS interference test advisories with designator, dates, and area | Subscribe at faasafety.gov |
| NOTAMs | The legal, authoritative record of the test and its published boundaries | Standard preflight NOTAM briefing |
| U.S. Coast Guard NAVCEN | Monthly GPS testing schedules and disruption notices | navcen.uscg.gov, email sign-up |
| GPS.gov | Planned disruptions and overall GPS constellation status | gps.gov |
| SCAUWG GPS-testing digest | A regional Southern California summary flagging cross-basin effects | scauwg.org/gps-testing-so-cal |
Treat digest sites as a heads-up layer and the NOTAM as your legal briefing item; SCAUWG itself advises pilots to confirm digest information against current NOTAMs before relying on it. Build the habit of checking these sources the same way you check winds aloft: every time you plan a flight through a basin known for testing, not only after you’ve heard something secondhand.
What Does This Mean for VFR Pilots vs. IFR Pilots?
VFR pilots should treat GPS interference primarily as a reminder to keep dead-reckoning and pilotage skills sharp, since basic VFR navigation doesn’t depend on GPS working correctly. If a GPS moving map does something strange during a training flight, that’s a real-world illustration of why an instructor still requires cross-countries flown with a sectional, a plotter, and checkpoints visible out the window. Student pilots flying in a known test area should expect to hear about it: if a CFI or dispatcher mentions a GPS test window, ask what it means for that day’s lesson before launching.
IFR pilots carry more risk and responsibility here, because GPS interference can strike during an approach, in weather, when the visual backup a VFR pilot relies on isn’t available. That’s exactly why maintaining proficiency with VOR, DME, and ILS approaches matters even in an increasingly GPS-centric IFR world, and why briefing a ground-based approach as backup before entering a known test area is good practice, not overcaution. Airline and corporate crews flying RNP routes through affected airspace face the same fundamental issue at higher operational stakes and should follow their operator’s specific GPS-interference contingency procedures.
Quick-Reference: GPS Jamming Checklist
| When You Suspect GPS Interference | Action |
|---|---|
| First priority | Fly the airplane on primary instruments |
| Second priority | Report to ATC immediately |
| Cross-check | VOR/DME, ILS, IRS, or pilotage |
| Moving map | Don’t trust displayed position, track, or groundspeed |
| Autopilot | Disengage GPS-coupled nav modes if erratic |
| On an RNAV approach | Be ready to switch to a ground-based or visual approach |
| After landing | File a written anomaly report |
| Before your next flight in the area | Check FAASTeam, NOTAMs, NAVCEN, GPS.gov, and regional digests like SCAUWG |
Frequently Asked Questions
What does GPS jamming actually do to my aircraft’s avionics?
Jamming floods the GPS frequency with noise strong enough to bury the real satellite signal, so your receiver loses lock rather than displaying a false position. Expect a dropped satellite count, a flagged loss of GPS integrity, blanked or frozen groundspeed and track, degraded RNP or ANP figures, and possibly erratic autopilot or moving-map behavior, since several avionics systems all draw from the same weakened GPS input at once.
How do I tell if I’m experiencing GPS jamming versus a simple equipment or antenna failure?
An isolated GPS dropout affecting only your aircraft, with no other symptoms, often points to an antenna or wiring fault. Jamming typically affects multiple aircraft in the same area at the same time, shows up as a regional loss of accuracy on tools like gpsjam.org, and is frequently confirmed when other pilots or ATC report the same problem in the same airspace during the same window. For an excellent video explanation, see the FAA WINGS-credit presentation GPS Spoofing and Jamming in Africa.
Is it safe to fly VFR or IFR through an active GPS-test area like the one near KSNA?
You can generally continue flying, but plan to navigate without relying on GPS for the duration. VFR pilots should be ready to use pilotage and dead reckoning; IFR pilots should have a ground-based approach or non-RNAV alternative briefed in advance. Check current NOTAMs and FAASTeam advisories before you fly, and treat any test window as a reason to brief a specific non-GPS backup plan, not a reason to cancel outright.
Do I need to report GPS interference to ATC, and does the FAA track these events?
Yes. FAA guidance directs pilots to report suspected jamming or spoofing to ATC immediately during the flight and to file a written anomaly report after landing. These reports feed the FAA’s ongoing GNSS Interference Resource Guide updates and help controllers and other pilots understand the scope of a given test or unexpected interference event in real time.
How should student pilots prepare differently than instrument-rated pilots for a known GPS-denial period?
Student pilots should lean on VFR fundamentals (pilotage, dead reckoning, and visual references), since GPS loss doesn’t affect basic VFR navigation. Instrument-rated pilots need a specific non-GPS approach backup briefed in advance (VOR, ILS, or visual), because interference can strike during an approach in weather. Both should check test advisories before flying through a known test area.
Fly Ready for the Real Test, Not Just the Written One
GPS interference testing over Southern California isn’t going away, and neither is your responsibility to brief for it. The pilots who handle a jammed or spoofed GPS signal calmly are the ones who trained their non-GPS navigation skills before they needed them, not mid-approach in weather.
That’s the same philosophy behind everything Gleim Aviation has built since 1980: mastery first, so the test, written or in the air, never catches you off guard. Our Online Ground School and FAA Knowledge Test Prep cover the navigation systems, avionics, and airspace concepts behind scenarios like this one, so you understand not just what to do, but why. Continue your preparation at GleimAviation.com. Onward and upward. The magenta line is a tool, and like any tool, it should be verified.