When I used to fly in Florida in the 2005-2015ish timeframe, NOTAMs for GPS interference (it didn't say that exactly but that's what it meant) were an everyday occurrence along my path, it became boilerplate. I experienced it a few times. One moment the GPS thinks you're plodding along next to Ocala, next moment it thinks I've teleported a thousand miles away, and then it'd just quit.
But that's what we train for. That's why aircraft and pilots have redundancy to work around any single possible point of failure and why you practice it until it becomes natural. Because of the NOTAM I'd already have a VOR tuned in, and once the GPS went inop I just fine tuned it to get a radial fix on the VOR. Also tried to never lose my bearings with my MK I Eyeballs either. No big deal.
I feel bad for everyone that lost their lives here, but this is why competence is critical. There's a litany of errors the pilots made. And the article tries to pin a bit on the controller, but no, ultimate responsibility is on the pilot in command, FAR/AIM is clear on that.
If these allegedly instrument rated pilots had been properly drilled by their CFI's and properly grilled during reviews and such this should've been an easy flight.
Also, "just ask Kennedy". Wired bringing that into the conversation is perhaps relevant but not in the way I think they intended. JFK Jr lacked basic airmanship skills. His aircraft was 100% functional until the moment it impacted the ocean.
Some professions simply can't be go-along-to-get-along social clubs. Safety culture centered on competence and performance is key.
I guess GPS jamming was not routine for them. Had they been aware of any NOTAM regarding GPS interference, they'd be prepared, and, like you said, would have VOR setup prior to leaving the ground.
I never flew a plane just know enough that a visual approach means “visual” rules. Hitting a mountain at that point is hard to argue for blaming anyone else but the pilot error? Did I get it right?
This is unnecessarily dismissive and pre-judgmental of a situation you can't actually know very much about. Wait for the NTSB report before replying, essentially "get gud"
It's pretty clear they're laying out that this is pilot error, unlike the article's intent to blame parties other than the pilot. The poster is trying to correct that, from an obvious place of knowledge and experience most of us do not have, and isn't being rude about it either.
It's important to understand why things happen in order to prevent them, and to counter the narrative of the opinionated article. And if we should wait for the NTSB report, then so should the article.
> Wait for the NTSB report before replying, essentially "get gud"
The preliminary NTSB report points toward “get gud”. If you request a visual approach and then fly into a mountain getting “gud” will be at top of the list.
Maybe you are just aren't aware that military GPS jamming is extremely routine around the US. It affects airplanes more than cars because the curvature of the earth can not help you and at typical flight altitudes you have easy line of sight to the jammer.
GPS is not essential to air navigation. It’s nice to have, and there are some approaches that legally require it to be operational in order to fly them (IFR procedures) but aviation has other systems in place to guide aircraft under conditions where visual flight navigation is impossible.
In this case, IMHO, the pilots had become complacent and lax in their navigational rigor because of the fact that GPS makes a lot of the slightly less automated systems unnecessary, and people get used to that workflow.
If the flight crew had been looking at their map and using it to inform them about the mountains in their path, fixing position by the VOR and DME, or even just a stopwatch and compass heading, they would have easily known they needed to be at a higher altitude. Not being precisely sure of their exact position, they should have at least been maintaining the minimum safe altitude for the area they knew they were in.
But unfortunately, people get so used to looking at the shiny screen giving them effortless situational awareness that they forget all of the rules and habits that kept pilots alive for the last century before glass cockpits were a thing, and they forget that mountains are the tigers of the air, always waiting to catch pilots unaware.
This is a useful cautionary tale not only for pilots, but increasingly for humans in general as we become accustomed to a new kind of instrument that allows us to offload a great deal of our cognitive focus to a tool that may sometimes fail.
Don't worry, our government is doing their level best to make GPS the only option for air navigation. After all, we all know that technology NEVER fails, and the sooner we can turn off all those big bad old ground radars and navigation aids, the sooner we can sell all that real estate and use the money for things that the American public desperately needs, like more corporate bailouts and bathroom security cameras.
Pilots were so used to "the plane won't make a mistake" that they were not aware/not trained properly about things that are nothing to do with the FMS like frozen pitot tubes and also that the autopilot has a number of "modes" which mean you need to go back to basics like altitude, attitude and air speed.
The animation at the top is worryingly misleading. The airplane that crashed was a Beechcraft twin turboprop, and the plane maneuvered a couple of times before crashing. It had 4 people inside it.
The animation uses what looks like an airliner, and shows the jamming as a sort of bubble that directly sends the airplane into a crash.
I found it disturbing when I looked at it, it does not represent the story well, and I think that's irresponsible.
I actually experienced GPS spoofing while paragliding near Ukraine, luckily in the daytime. I don't even want to imagine it at night on a rescue mission. Condolences to the occupants.
It's quite easy to say "no big deal" while calm in an office, but it's really different when you're busy flying and then there's the extra workload of trying to understand what's happening, attempting to fix it, and so on. Imagine "debug bug in production while driving a car" for a rough comparison, although I guess planes are probably better equipped for loss of GPS?
> At 0000:26, the ARTCC controller advised the flight crew that the airplane was at 13,000 ft msl, 1,000 ft above their assigned altitude. The pilot responded that they were correcting their altitude and that the airplane had lost GPS capability. The pilot stated they would need a heading
> About 0005 the ARTCC operations supervisor contacted [the military] to stop jamming and at 0007:34 ADS-B data recording returned to 2-3 second intervals.
> The flight crew again reported they “[have] a visual on Ruidoso” at 0008:30 and that they could “go visual.”
> About 0010, the ARTCC operations supervisor informed [the military] that the airplane was on a visual approach and that they could resume jamming.
> The airplane impacted terrain about 250 ft southwest of the last recorded data point at an elevation of about 9,950 ft, and about 730 ft east and 230 ft below the Capitan Mountains Summit Radio Facility, located at an elevation of about 10,180 ft.
The image of the map from the report really helps me understand the path. It seems like the aircraft began visual approach and didn't know where it was, or didn't know about the mountain.
The loss is tragic but I’m sorry GPS jamming was not a factor here. There was a NOTAM indicating it’s going on, the pilots should have been aware and it appears when they reached out with a request the jamming was stopped.
It was a visual approach at a moonless night at an airport in high terrain, this was pilot error unfortunately.
We have a competency crisis that will only get worse and worse. I myself am guilty of it. Modern life is too comfortable, there is no need to fight through and put in the hours to be an expert when you can do 50% and get 90% of the paychecke.
Pilots train to navigate without GPS. Or, rather, they should...
It feels like if you know how far away the strip is (sounds like they did), and can get a bearing on it, they should be all set… with no GPS they should presumably have had even stronger eyes on the charts.
Back when i used to sail, taking bearings with a sighting compass on two points on land / two buoys always gave you a fairly accurate position. Not sure if there is a sighting compass equivalent with elevation angle too on planes?
The final information on the crash almost reads like they hit the very top of the mountain - according to NTSB, they were about 200-250 ft from the summit, so it is possible they did still have visual with the airport until right before the impact. Whether or not GPS could've helped with this, I'm not sure - it might've allowed them to see where they were relative to the mountain better, since it was the middle of the night and so they probably couldn't see the mountain very well..
Your GPS enabled flight computer will indeed yell at you VERY LOUDLY if you're about to hit a mountain. It will not allow you to get particularly close to terrain without noticing.
I'm wondering what they could have done differently here. The report said it was a 0% moonlight night, extremely dark. No exact position from GPS, and visuals on the landing strip. That mountain peak would have likely been invisible from the pilot's seat.
What would have been the "skill issue" difference people keep mentioning? It's getting really frustrating how reckless the US military is with the skies. They keep putting people in danger. I can't help but think about the DCA crash due to the continuity of government drills.
There's no reason they should have been flying dark for a drill that night.
GPS NOTAM'd as unreliable on a dark, moonless night?
Fly the ILS approach (or fly a visual approach along the track of the ILS approach backing up your visual with the radio signals). That will give you terrain and obstacle clearance all along the route using locally generated navigation signals that will be entirely unaffected by GPS jamming.
Per other comments the ILS approach was not available due to the local weather service being NOTAM'd as unavailable, couldn't set local altitude. The judgment call was effectively whether to take the flight at all, as there was effectively no instrument approach available and the visual conditions precluded VFR.
The ILS approach being not legally usable due to a missing local altimeter setting does not make it unusable to back up a visual approach [or VFR arrival].
I would 100% (and have) take center's altimeter setting and fly the track of an ILS or localizer rather than "whelp, nothing can be done..." This was VMC; you don't need a local altimeter setting to be safe using the radio navaids; you would need it to legally fly the approach as an ILS approach.
Makes one think about "flying cars". How well designed they will be for losing such system? How reliable any systems would be in such eventuality. For both safety of the craft and anyone near them or on ground... Especially if there is other things going on like weather conditions. Say both heavy fog and rain.
After reading the story, it seems like lack of training. I think training should assume GPS goes out (which it does), in this case they didn’t pull up when they saw “lights going out” as a mountain became between them and the airfield.
Air traffic control have a very specific remit and it isn't as comprehensive as people assume. You can have "no service", "radar service" and "full service" and what they will advise you about is limited, usually, to spacing or procedural errors like "you should be less than 220 knots".
A controller who has the capacity to spot something that seems off like a wrong heading or altitude might ask the plane if they are OK, but unless they are deviating from a flight plan in controlled airspace, they are more likely to assume VFR and pilot knows best.
I have absolutely no love for the US Army under its current Secretary of "war", but here the problem was with the air ambulance pilot(s). Sorry to blame people who died, who do important service for remote places under hard time constraints, but there has been fundamental errors on their side:
I find it a bit shocking they'd be caught by surprise by a planned GPS outage. The exercise happened as intended, and all aircraft in the affected areas should have received warnings BEFORE they even took off. These are not drug smugglers - they filed a flight plan before leaving the ground.
The automated weather service was also out. This made it difficult or impossible to use the ILS because they can't set the local altimeter. This was a swiss cheese chain of events. It was a moonless dark night so the mountains weren't visible.
Would they take off if they knew GPS would be jammed midway through the flight?
Had they known they wouldn't be able to rely on GPS, all that back and forth with ATC would not be needed, and they'd already have a plan B and a plan C for navigating.
It's unfortunately all slices of swiss cheese aligned perfectly, but I'd still blame the military for poking extra holes on the GPS slice.
SRR is serviced by two instrument approaches, the ILS or LOC RWY 24 and the RNAV (GPS)
RWY 24. Both instrument approach plate notes section contain the following statement: “When
local altimeter setting not received, procedure NA (Not Authorized).”
IFR approach was not possible, the flight plan was unrealistic.
When I used to fly in Florida in the 2005-2015ish timeframe, NOTAMs for GPS interference (it didn't say that exactly but that's what it meant) were an everyday occurrence along my path, it became boilerplate. I experienced it a few times. One moment the GPS thinks you're plodding along next to Ocala, next moment it thinks I've teleported a thousand miles away, and then it'd just quit.
But that's what we train for. That's why aircraft and pilots have redundancy to work around any single possible point of failure and why you practice it until it becomes natural. Because of the NOTAM I'd already have a VOR tuned in, and once the GPS went inop I just fine tuned it to get a radial fix on the VOR. Also tried to never lose my bearings with my MK I Eyeballs either. No big deal.
I feel bad for everyone that lost their lives here, but this is why competence is critical. There's a litany of errors the pilots made. And the article tries to pin a bit on the controller, but no, ultimate responsibility is on the pilot in command, FAR/AIM is clear on that.
If these allegedly instrument rated pilots had been properly drilled by their CFI's and properly grilled during reviews and such this should've been an easy flight.
Also, "just ask Kennedy". Wired bringing that into the conversation is perhaps relevant but not in the way I think they intended. JFK Jr lacked basic airmanship skills. His aircraft was 100% functional until the moment it impacted the ocean.
Some professions simply can't be go-along-to-get-along social clubs. Safety culture centered on competence and performance is key.
I guess GPS jamming was not routine for them. Had they been aware of any NOTAM regarding GPS interference, they'd be prepared, and, like you said, would have VOR setup prior to leaving the ground.
Checking NOTAMs is important.
Some of the replies you're getting are ridiculous lol. Anyways thanks for your insight.
HN threads on aviation are always a bit goofy to anyone who's actually flown a plane, yeah.
I never flew a plane just know enough that a visual approach means “visual” rules. Hitting a mountain at that point is hard to argue for blaming anyone else but the pilot error? Did I get it right?
This is unnecessarily dismissive and pre-judgmental of a situation you can't actually know very much about. Wait for the NTSB report before replying, essentially "get gud"
It's pretty clear they're laying out that this is pilot error, unlike the article's intent to blame parties other than the pilot. The poster is trying to correct that, from an obvious place of knowledge and experience most of us do not have, and isn't being rude about it either.
It's important to understand why things happen in order to prevent them, and to counter the narrative of the opinionated article. And if we should wait for the NTSB report, then so should the article.
> Wait for the NTSB report before replying, essentially "get gud"
The preliminary NTSB report points toward “get gud”. If you request a visual approach and then fly into a mountain getting “gud” will be at top of the list.
Pilots complaining about automation: several
Pilots unable to fly with all the bells and whistles and getting their ass handed to them when anything falls out of the ordinary: too many
What do you expect might change between the preliminary and the final report?
[delayed]
Maybe you are just aren't aware that military GPS jamming is extremely routine around the US. It affects airplanes more than cars because the curvature of the earth can not help you and at typical flight altitudes you have easy line of sight to the jammer.
I agree with your perspective re: the tone of the OP. But they hold a perspective that we should also give credence towards.
Your main point is the most valid - wait for the final report. But you should be saying the same to the article as written.
Prelim report: https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/G...
Out of my scope to infer.
GPS is not essential to air navigation. It’s nice to have, and there are some approaches that legally require it to be operational in order to fly them (IFR procedures) but aviation has other systems in place to guide aircraft under conditions where visual flight navigation is impossible.
In this case, IMHO, the pilots had become complacent and lax in their navigational rigor because of the fact that GPS makes a lot of the slightly less automated systems unnecessary, and people get used to that workflow.
If the flight crew had been looking at their map and using it to inform them about the mountains in their path, fixing position by the VOR and DME, or even just a stopwatch and compass heading, they would have easily known they needed to be at a higher altitude. Not being precisely sure of their exact position, they should have at least been maintaining the minimum safe altitude for the area they knew they were in.
But unfortunately, people get so used to looking at the shiny screen giving them effortless situational awareness that they forget all of the rules and habits that kept pilots alive for the last century before glass cockpits were a thing, and they forget that mountains are the tigers of the air, always waiting to catch pilots unaware.
This is a useful cautionary tale not only for pilots, but increasingly for humans in general as we become accustomed to a new kind of instrument that allows us to offload a great deal of our cognitive focus to a tool that may sometimes fail.
Don't worry, our government is doing their level best to make GPS the only option for air navigation. After all, we all know that technology NEVER fails, and the sooner we can turn off all those big bad old ground radars and navigation aids, the sooner we can sell all that real estate and use the money for things that the American public desperately needs, like more corporate bailouts and bathroom security cameras.
This was the partial cause of Air France 447.
Pilots were so used to "the plane won't make a mistake" that they were not aware/not trained properly about things that are nothing to do with the FMS like frozen pitot tubes and also that the autopilot has a number of "modes" which mean you need to go back to basics like altitude, attitude and air speed.
To add to this, there's a good lecture called Children of the Magenta Line that discusses automation dependency: https://www.youtube.com/watch?v=5ESJH1NLMLs
The animation at the top is worryingly misleading. The airplane that crashed was a Beechcraft twin turboprop, and the plane maneuvered a couple of times before crashing. It had 4 people inside it.
The animation uses what looks like an airliner, and shows the jamming as a sort of bubble that directly sends the airplane into a crash.
I found it disturbing when I looked at it, it does not represent the story well, and I think that's irresponsible.
I actually experienced GPS spoofing while paragliding near Ukraine, luckily in the daytime. I don't even want to imagine it at night on a rescue mission. Condolences to the occupants.
It's quite easy to say "no big deal" while calm in an office, but it's really different when you're busy flying and then there's the extra workload of trying to understand what's happening, attempting to fix it, and so on. Imagine "debug bug in production while driving a car" for a rough comparison, although I guess planes are probably better equipped for loss of GPS?
https://blog.emilburzo.com/2026/06/gps-spoofing-teleported-m...
The preliminary NTSB report: https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/G...
> At 0000:26, the ARTCC controller advised the flight crew that the airplane was at 13,000 ft msl, 1,000 ft above their assigned altitude. The pilot responded that they were correcting their altitude and that the airplane had lost GPS capability. The pilot stated they would need a heading
> About 0005 the ARTCC operations supervisor contacted [the military] to stop jamming and at 0007:34 ADS-B data recording returned to 2-3 second intervals.
> The flight crew again reported they “[have] a visual on Ruidoso” at 0008:30 and that they could “go visual.”
> About 0010, the ARTCC operations supervisor informed [the military] that the airplane was on a visual approach and that they could resume jamming.
> The airplane impacted terrain about 250 ft southwest of the last recorded data point at an elevation of about 9,950 ft, and about 730 ft east and 230 ft below the Capitan Mountains Summit Radio Facility, located at an elevation of about 10,180 ft.
The image of the map from the report really helps me understand the path. It seems like the aircraft began visual approach and didn't know where it was, or didn't know about the mountain.
The loss is tragic but I’m sorry GPS jamming was not a factor here. There was a NOTAM indicating it’s going on, the pilots should have been aware and it appears when they reached out with a request the jamming was stopped.
It was a visual approach at a moonless night at an airport in high terrain, this was pilot error unfortunately.
I'll bet that the NTSB will list GPS jamming as a contributing factor. I agree with you that it's not the primary cause of the accident.
We have a competency crisis that will only get worse and worse. I myself am guilty of it. Modern life is too comfortable, there is no need to fight through and put in the hours to be an expert when you can do 50% and get 90% of the paychecke.
Pilots train to navigate without GPS. Or, rather, they should...
It feels like if you know how far away the strip is (sounds like they did), and can get a bearing on it, they should be all set… with no GPS they should presumably have had even stronger eyes on the charts.
Back when i used to sail, taking bearings with a sighting compass on two points on land / two buoys always gave you a fairly accurate position. Not sure if there is a sighting compass equivalent with elevation angle too on planes?
https://archive.ph/CECav
The final information on the crash almost reads like they hit the very top of the mountain - according to NTSB, they were about 200-250 ft from the summit, so it is possible they did still have visual with the airport until right before the impact. Whether or not GPS could've helped with this, I'm not sure - it might've allowed them to see where they were relative to the mountain better, since it was the middle of the night and so they probably couldn't see the mountain very well..
Your GPS enabled flight computer will indeed yell at you VERY LOUDLY if you're about to hit a mountain. It will not allow you to get particularly close to terrain without noticing.
I'm wondering what they could have done differently here. The report said it was a 0% moonlight night, extremely dark. No exact position from GPS, and visuals on the landing strip. That mountain peak would have likely been invisible from the pilot's seat.
What would have been the "skill issue" difference people keep mentioning? It's getting really frustrating how reckless the US military is with the skies. They keep putting people in danger. I can't help but think about the DCA crash due to the continuity of government drills.
There's no reason they should have been flying dark for a drill that night.
This is a judgment issue more than a skill issue.
GPS NOTAM'd as unreliable on a dark, moonless night?
Fly the ILS approach (or fly a visual approach along the track of the ILS approach backing up your visual with the radio signals). That will give you terrain and obstacle clearance all along the route using locally generated navigation signals that will be entirely unaffected by GPS jamming.
https://aeronav.faa.gov/d-tpp/2607/06922IL24.PDF
Per other comments the ILS approach was not available due to the local weather service being NOTAM'd as unavailable, couldn't set local altitude. The judgment call was effectively whether to take the flight at all, as there was effectively no instrument approach available and the visual conditions precluded VFR.
The ILS approach being not legally usable due to a missing local altimeter setting does not make it unusable to back up a visual approach [or VFR arrival].
I would 100% (and have) take center's altimeter setting and fly the track of an ILS or localizer rather than "whelp, nothing can be done..." This was VMC; you don't need a local altimeter setting to be safe using the radio navaids; you would need it to legally fly the approach as an ILS approach.
Makes one think about "flying cars". How well designed they will be for losing such system? How reliable any systems would be in such eventuality. For both safety of the craft and anyone near them or on ground... Especially if there is other things going on like weather conditions. Say both heavy fog and rain.
After reading the story, it seems like lack of training. I think training should assume GPS goes out (which it does), in this case they didn’t pull up when they saw “lights going out” as a mountain became between them and the airfield.
Air traffic control also failed here.
Air traffic control have a very specific remit and it isn't as comprehensive as people assume. You can have "no service", "radar service" and "full service" and what they will advise you about is limited, usually, to spacing or procedural errors like "you should be less than 220 knots".
A controller who has the capacity to spot something that seems off like a wrong heading or altitude might ask the plane if they are OK, but unless they are deviating from a flight plan in controlled airspace, they are more likely to assume VFR and pilot knows best.
I have absolutely no love for the US Army under its current Secretary of "war", but here the problem was with the air ambulance pilot(s). Sorry to blame people who died, who do important service for remote places under hard time constraints, but there has been fundamental errors on their side:
https://bsky.app/profile/mikeblack114.bsky.social/post/3mrux...
I find it a bit shocking they'd be caught by surprise by a planned GPS outage. The exercise happened as intended, and all aircraft in the affected areas should have received warnings BEFORE they even took off. These are not drug smugglers - they filed a flight plan before leaving the ground.
The automated weather service was also out. This made it difficult or impossible to use the ILS because they can't set the local altimeter. This was a swiss cheese chain of events. It was a moonless dark night so the mountains weren't visible.
Would they take off if they knew GPS would be jammed midway through the flight?
Had they known they wouldn't be able to rely on GPS, all that back and forth with ATC would not be needed, and they'd already have a plan B and a plan C for navigating.
It's unfortunately all slices of swiss cheese aligned perfectly, but I'd still blame the military for poking extra holes on the GPS slice.
I too take random's words on socials over the NTSB. /s
In any case the news (and ntsb report) points that they are tied, not responsibility.
They are not in a disagreement. From the report:
SRR is serviced by two instrument approaches, the ILS or LOC RWY 24 and the RNAV (GPS) RWY 24. Both instrument approach plate notes section contain the following statement: “When local altimeter setting not received, procedure NA (Not Authorized).”
IFR approach was not possible, the flight plan was unrealistic.
Trust in governmental institutions is at an all time low.
Questions must be asked about how and why we got here rather appeal to submission.
A rehash of the paywalled Wired article:
* https://futurism.com/science-energy/us-military-gps-jamming-...
Blancolirio (YouTube aviation reporter and commercial pilot) analysis:
https://youtu.be/Dcyup4xVQuM?is=n0w5_tLCxEkYGtt9