How A Cold War Relic (F-5) Beat The World’s Most Advanced Air Defense Network
An Expert Mission Planner’s Assessment of the Iranian F-5 Strike on Camp Buehring
A note before we begin: I haven’t been a direct mission planner in some time, but I’ve been working in and around this world for roughly 30 years — building technology for the Pentagon and NSA, doing intelligence analysis, and staying current on the technical architecture of systems I spent a career around. For this analysis, I used AI (Claude) to verify facts, cross-check my immediate read against open-source reporting, and ensure my conclusions were grounded — not just in memory and instinct, but in what’s actually confirmed and documented. Most of my initial analysis held up. Where I needed to search for what the ISR picture actually looked like, I relied on my intelligence training, technical background, and advanced radar and avionics experience — cross-referenced against sources available to everyone. I cannot reveal classified information, and I won’t. But I can make educated inferences from that background, and I’ll tell you when I’m doing that versus when I’m citing confirmed reporting. This is my best analytical assessment — not a final verdict. Some of these questions won’t have public answers for years, if ever.
A final note on expertise: I know my stuff. I mission planned the initial bombing runs into Afghanistan in the immediate aftermath of 9/11, and over roughly 30 years participated in multiple combat and training operations across multiple airframes — working alongside global NATO crews and platforms that most analysts never get close to. Advanced radar and avionics training, Red Flag, building technology for the Pentagon and NSA — I’m confident in this analysis. But I want to tip my cap to the USAF Weapons School graduates — the patch wearers — who trained me and who operate at a level most people in this business never reach. My instincts on this came from them. If they ever read this, I hope I got it right. They would know better than anyone if I didn’t.
When NBC News confirmed this week that an Iranian F-5 fighter jet successfully bombed Camp Buehring in Kuwait — penetrating Patriot missile batteries, short-range interceptors, and a layered American air defense architecture — the pundit class reacted with shock. I wasn’t shocked. I was validated.
Here’s why — and here’s what actually happened.
The Aircraft: Don’t Let the Age Fool You
The F-5 Tiger II is a Cold War export fighter. The Shah of Iran bought them from the United States in the early 1970s. After the Islamic Revolution in 1979 and the subsequent arms embargo, Iran was left holding an aging fleet with no spare parts pipeline and no upgrade path. So they built their own.
Over decades of sanctions-driven ingenuity, Iran developed a series of F-5 derivatives — the Azarakhsh, the Saeqeh, and most recently the Kowsar. These aren’t revolutionary aircraft. But they aren’t museum pieces either. Iran’s Saeqeh variant reportedly carries a Phazotron-NIIR N019 “Baaz” radar capable of tracking ten targets and engaging two simultaneously, with a range of roughly 50 miles. The Kowsar has been fitted with a Grifo fire control radar and fourth-generation avionics including a glass cockpit, heads-up display, ballistic computers, and smart mapping systems. An earlier Chinese-assisted modernization program under Project Silk Road II equipped select F-5s with a SY-80 pulse-Doppler radar, radar warning receivers, chaff and flare dispensers, GPS navigation, and TACAN.
This wasn’t a flying antique. It was a small, upgraded, highly familiar aircraft flown by a pilot who almost certainly trained extensively on this mission profile. And Iran knew exactly what it was flying into.
The Penetration: Low, Slow, and Invisible to the Wrong Radar
Here’s my read, as someone who spent years mission planning bombing runs for B-1s, F-15s, and F-16s — including planning against aggressor squadrons that flew F-5s in Red Flag exercises designed to replicate exactly this threat profile.
The Patriot system’s Target Acquisition Radar (TAR) — specifically the AN/MPQ-65 — has a well-documented low-altitude performance limitation. It is optimized for ballistic missiles and medium-to-high altitude cruise missiles. A small aircraft approaching at low altitude, at subsonic or transonic speed, with a minimal radar cross-section, presents a detection challenge that Patriot was simply not designed to prioritize. The system can engage low-altitude targets, but the geometry, the radar’s elevation coverage, and ground clutter combine to create a meaningful seam at very low altitudes and very slow speeds.
The F-5’s profile is almost tailor-made to exploit that seam. It’s small. It’s slow by modern fighter standards. It can fly NOE (nap-of-the-earth) profiles. And critically — the pilot executed what the reporting describes as a “dumb bomb” attack. No missile signature. No radar-emitting munition to track. Just a jet flying low, releasing unguided bombs, and egressing. There was nothing for the missile defense radar to key off of until it may have been too late to engage.
The emergency $8 billion Lower Tier Air and Missile Defense Sensor (LTAMDS) radar sale the U.S. pushed through for Kuwait on March 19 — three weeks after the strike — confirms this analysis. LTAMDS is specifically designed to replace the AN/MPQ-65 and close the low-altitude, 360-degree coverage gaps that Patriot’s current radar leaves open. You don’t approve an emergency $8 billion sale if the existing architecture was working as advertised.
The Real Weapon: Saturation
But the radar vulnerability alone doesn’t explain it. The F-5 didn’t penetrate Camp Buehring’s defenses in a vacuum. It penetrated them during one of the most complex, multi-axis, multi-domain saturation attacks Iran could generate.
On March 1, 2026, Iranian forces were simultaneously launching Shahed-136 kamikaze drones, Fateh-110 solid-fuel ballistic missiles, Su-24 strike aircraft, and cruise missiles across multiple targets in Kuwait, Saudi Arabia, Qatar, Bahrain, and the UAE. Every Patriot battery in the region was engaged in active threat prioritization. Every operator was cycling through engagement decisions at a rate that training environments simply cannot replicate at scale.
This is where my Red Flag experience becomes directly relevant. In training, aggressor squadrons — which flew F-5s — taught us to think about layered, simultaneous threat generation. The whole point is to overwhelm the decision cycle. But Red Flag has a safety envelope. You don’t actually saturate a live Patriot battery with 40 simultaneous inbound targets while jamming the datalink and running a manned aircraft at treetop level from a different vector. Wartime is categorically different.
If Iran had a competent mission planning and intelligence team — and the evidence strongly suggests they did — they studied U.S. air defense doctrine. They calculated, roughly, how American systems would prioritize threats. They knew Patriot operators would sequence engagements. They knew how many interceptors would be expended against ballistic missiles in the first waves. They ran the math on magazine depth and reload timelines. And they timed the F-5 run to hit when the battery operators were deepest in their decision cycle and the short-range interceptors were most committed to other tracks.
That’s not luck. That’s planning.
The Intel Layer: They Knew Where to Go
The post-strike reporting adds another dimension that should alarm every defense analyst. A U.S. Army Central memo reviewed by CBS News found that Iranian intelligence and allied proxy forces had likely tracked the movement of American personnel to dispersed installations in the week before attacks began. GPS transponders attached to balloons and parachutes were found near Patriot systems in the area on March 2. Quadcopter reconnaissance flights were observed over Port Shuaiba in the days preceding the March 1 drone strike that killed six American soldiers from the 103rd Sustainment Command.
If Iran’s ISR picture was that granular at Port Shuaiba, they had comparable visibility on Camp Buehring. They knew the layout. They knew the radar positions. They knew the coverage geometry. And they built a strike profile around it.
What This Means
The F-5 strike on Camp Buehring is not a story about Iranian airpower. It’s a story about three systemic failures converging at the same moment: a low-altitude radar coverage gap in a system optimized for the wrong threat tier, a saturation attack designed to exploit the human decision cycle, and an intelligence failure that allowed Iran to build an accurate enough picture of U.S. defensive architecture to calculate the seam.
I’ve planned missions against air defense networks. I’ve run aggressor scenarios against the very type of aircraft that made this run. The tactics Iran used weren’t exotic. They were textbook. The question that should keep defense planners up at night isn’t how Iran did it. It’s why we didn’t close the gap before the shooting started — and whether we’ve closed it now.
The $8 billion LTAMDS sale suggests we’re trying. But that’s a reactive answer to a vulnerability that was known long before February 28, 2026.
A Cold War relic just embarrassed the world’s most advanced air defense network. That’s not a fluke. That’s a lesson that was available to read, if anyone had been paying attention.
Part II: What the Debrief Will Tell Us — Questions Nobody in the Media Is Asking
I’ve been in a lot of debriefs. Military debriefs after complex missions are brutal, methodical, and unsparing. They exist precisely because the fog of war produces gaps, assumptions, and failures that need to be interrogated before the next fight. The American public and Congress deserve the equivalent of that debrief on the Camp Buehring F-5 strike. Based on everything I’ve seen in the reporting and everything I know from my background, here are the questions that a real debrief would force — and that the media has largely not thought to ask.
The Aircraft: How Many F-5s Were Actually in That Strike Package?
Open source reporting refers to a single F-5. NBC News says “an Iranian F-5.” But in professional mission planning, you don’t send a single asset on a high-value penetration run without either a decoy or a trail aircraft for battle damage assessment. The question for the debrief is: was this a single-ship attack, a two-ship, or part of a larger coordinated package where other aircraft were turned back or shot down before reaching the target? The aviation shootdowns tracker for the 2026 Iran war confirms that on March 1 alone, both an F-5 and an F-4 Phantom were destroyed by Israeli strikes at Tabriz Airport while attempting to scramble — suggesting Iran was attempting to sortie multiple airframes simultaneously. Whether any of those were part of the Buehring mission package is unconfirmed publicly. The debrief will know. We should know too.
ISR: How Did Iran Actually See Camp Buehring?
This is where it gets genuinely alarming, and where I haven’t seen any major outlet connect the dots fully. A Financial Times investigation published April 15, 2026 revealed that Iran had acquired a Chinese-built TEE-01B high-resolution Earth observation satellite from the IRGC Aerospace Force in late 2024 — a $36.6 million contract — and used it to conduct a complete ISR cycle during the March 2026 strikes. That means pre-strike reconnaissance, strike timing coordination, and post-strike damage assessment, all via a foreign-operated sub-meter resolution electro-optical satellite. Camp Buehring was specifically listed among the facilities monitored.
Layer that on top of what we already know: GPS transponders on balloons near Patriot systems, quadcopter reconnaissance flights over Port Shuaiba in the week before attacks, and a U.S. Army Central memo concluding that Iranian intelligence had likely tracked personnel movements to dispersed installations. This was not improvised targeting. Iran had satellite imagery, HUMINT on the ground, and drone-based ISR all feeding the same targeting picture. The debrief question is what U.S. counterintelligence was doing during that same window — and why none of those ISR activities triggered a defensive response before the strike.
The Operators: Average Age, Training Cycle, and Drone-Specific Readiness
This is a question the military will ask internally and that the public deserves an answer to. What was the average age and experience level of the Patriot battery operators at Camp Buehring on the day of the strike? How long had they been in theater? Had they rotated in specifically for the conflict, or were they a standing force? And critically — had they trained against the specific threat profile of a slow, low, small manned aircraft during a simultaneous drone and ballistic missile saturation? Because those are categorically different training scenarios, and most Patriot operator training in recent years has been heavily weighted toward ballistic missile defense. The drone-defeat gap at Port Shuaiba — where troops had “basically no drone defeat capability” despite requests — suggests a broader readiness question about whether the joint force was trained and equipped for the actual threat Iran brought to the fight versus the threat the training program modeled.
The F-5 After the Strike: Did We Get It?
NBC News explicitly noted they could not confirm whether the F-5 was shot down after completing its run. This matters for two reasons. First, if it egressed successfully, that tells you something about both the continued state of the air defense network after the saturation attack and about the vector the aircraft used to exit. Second, if it was engaged and destroyed on egress, that’s an important data point that the Pentagon has not made public — and the question is why. A successful intercept after the fact doesn’t erase the penetration, but it changes the narrative. The debrief will have that answer. The public doesn’t.
The Intelligence Leak Question: Were We Compromised Before the War Started?
The GPS transponders near Patriot systems. The quadcopter recon flights nobody interdicted. The Chinese satellite quietly imaging Camp Buehring weeks before the strikes. The fact that Iranian intelligence appears to have tracked U.S. personnel dispersal in real time. Taken together, these aren’t the hallmarks of an adversary that got lucky. They suggest either a sophisticated and layered collection effort that U.S. counterintelligence failed to detect and disrupt — or something worse. The debrief question I’d want answered as a former intelligence professional is: did we have SIGINT on Iranian planning before February 28 that indicated this level of ISR activity against our bases, and if so, what was the warning that came out of it and to whom?
AI in the Kill Chain: What Enhancements Were in Use?
This question is almost entirely absent from public reporting, and it shouldn’t be. The U.S. military has been integrating AI-assisted threat prioritization and engagement decision support into Patriot battery operations for years. The LTAMDS program itself is designed to work with AI-enabled fire control. The debrief question is whether any AI-assisted systems were active in the Camp Buehring air defense network during the strike, what threat prioritization decisions those systems made or recommended, and whether the F-5’s low-slow profile caused it to be deprioritized algorithmically in favor of the higher-kinetic ballistic missile threats in the engagement queue. If AI-assisted triage sorted the F-5 as a lower-priority track while the operators were managing a ballistic missile engagement, that is an urgent AI doctrine and training problem — not just a radar problem.
Weather: Did Environmental Conditions Affect Detection?
This seems basic. It isn’t. The Kuwaiti desert in late February and early March can produce dust haze, low-visibility conditions, and ground clutter that meaningfully degrades radar performance at low altitudes. Weather at the time of the strike has not been reported publicly. In a real debrief, it would be one of the first data points on the table. Low-altitude radar coverage is already the Patriot system’s weak flank. Weather-induced ground clutter at the time of the strike could have been a compounding factor that made the F-5’s track even harder to separate from background noise.
What Else Got Through at Buehring?
The F-5 story has dominated coverage of the Camp Buehring strike, but the full damage picture suggests it wasn’t the only thing that got through. Open-source analysis confirmed drone strikes on Camp Buehring on both March 1 and March 5. A CH-47F Chinook was destroyed at Camp Buehring by a Shahed-136 drone attack. Satellite imagery from March 31 confirmed destroyed hangars, wrecked military equipment, and damaged personnel shelters at the base. One estimate put the damage at Camp Buehring alone at roughly $1.9 billion in the first four days. The F-5 may have been the most symbolically significant penetration, but the compound effect of multiple successful strikes — drone and manned aircraft — across multiple days tells a story of sustained defensive failure that a single headline about a Cold War fighter doesn’t fully capture.
Part III: What Americans Deserve to Know — and Aren’t Being Told
Why the Delay?
The F-5 strike on Camp Buehring happened in the first days of March. It is now late April. Nearly two months passed before NBC News confirmed it — and only because three U.S. officials, two congressional aides, and another person familiar with internal damage assessments decided the public needed to know. That is not how a government in a functioning democracy should operate. The administration knew. Senior military leadership knew. Congress, to the extent it was briefed in classified sessions, knew. The American people — whose sons and daughters are serving in theater — did not know.
The official explanation will be operational security. There are legitimate OPSEC reasons not to publicize specific defensive vulnerabilities in real time. But we are nearly two months post-strike, the conflict has moved through multiple phases, and the administration is actively discussing a ceasefire. The OPSEC rationale for continued suppression of this information at this point is thin. What isn’t thin is the political rationale — because confirmation that an Iranian F-5 penetrated American air defenses directly contradicts Trump’s repeated public claims that Iran’s military had been “completely obliterated” and had “no anti-aircraft equipment” left.
Can We Trust the Numbers?
The official U.S. casualty count is 13 service members killed and approximately 400 wounded. The Intercept has reported that the actual number may be higher than what the Pentagon has made public. We know from the Port of Shuaiba reporting alone that the initial public figures were dramatically understated — the Pentagon initially described a strike on a “fortified tactical operations center” without disclosing location, weapon type, or the full casualty count, which ultimately reached six killed and more than 60 wounded. If the pattern from Shuaiba held across other strikes, the aggregate numbers deserve independent verification.
The administration also asked commercial satellite companies — including Planet Labs — to impose blackouts on imagery of U.S. bases in the strike zone. Planet Labs disclosed in an April 4 email to customers that its 14-day blackout was being extended. That is an extraordinary suppression of commercially available open-source information, and it should prompt direct questions from Congress about the legal basis, the scope, and who authorized it.
What Is the Total Damage at Camp Buehring?
The honest answer is that no verified, complete public accounting exists. What we know from open source is significant: warehouses destroyed, aircraft hangars hit, fuel tanks obliterated, a CH-47 Chinook destroyed, helicopter facilities wrecked, barracks damaged, radar systems degraded. One estimate placed damage at the base at $1.9 billion in four days. The AEI assessment cited by NBC put the total across all affected bases at over $5 billion. The Pentagon has released no official battle damage assessment publicly, damage figures remain classified, and the administration pressured satellite imagery providers to limit public access to before-and-after comparisons.
That is not a posture consistent with a government that believes it is winning transparently. It is the posture of an administration managing a political narrative. The American people deserve the unvarnished assessment — not because they need to know every classified tactical detail, but because the men and women serving in that theater, and the families of those who were killed and wounded, deserve accountability rather than spin.
The debrief will happen inside classified channels. The question is whether Congress and the American public will ever see its conclusions — or whether this administration will treat a systemic air defense failure as just another inconvenient fact to suppress.
I wish I was in that mission debrief. It’s where most of the truth would come out — and I’ve been in some very confrontational debriefs in my time. I bet that one was.
Denver Riggleman is a former U.S. Representative (Virginia’s 5th Congressional District), Air Force and NSA intelligence veteran, senior technical advisor to the January 6th Select Committee, and CEO of RIIG (Riggleman Information and Intelligence Group). He served as a mission planner for B-1, F-15, and F-16 aircraft and participated in Red Flag exercises against F-5 aggressor squadrons. He is a New York Times bestselling author of The Breach
When I heard it was a F-5, my first thought was the low radar profile. It was about the perfect plane of this strike short of a stealth aircraft. That Iranian pilot carries his balls in a wheelbarrow.
It was probably withheld at least in part because it's so embarrassing to the regime. Hubris was a big part of it. There is an illusion that the US is untouchable, but no military is. There are always little seams to be exploited by a clever and alert enemy.
Never believe your own propaganda.
Denver, you will absolutely never cease to amaze me. Such thorough investigative work. So needed.