The editorial argues that BAE Systems' AN/ALQ-239 EPAWSS was specifically designed to counter modern double-digit SAM threats like those Iran operates, yet the F-15E was sent into Iranian airspace still relying on the legacy AN/ALQ-135 analog-era jammer. The gap between known capability shortfall and actual fielding of the fix is the central failure.
The editorial emphasizes that the F-15E is a 1980s-era platform with a significant radar cross-section, not a stealth aircraft. The mission planning chain and EW suite were expected to compensate for this inherent vulnerability against one of the most heavily defended airspaces on the planet — and they didn't. This represents the first US fixed-wing combat loss to enemy fire in over twenty years.
The editorial details how the ALQ-135 was adequate against single-emitter SAM systems but was a known capability gap against a networked IADS fusing search radars, fire-control radars, passive sensors, and infrared. Iran's air defense network successfully exploited this gap, validating concerns about legacy EW systems facing modern integrated threats.
A US Air Force F-15E Strike Eagle was confirmed shot down over Iranian airspace on April 3, 2026. It is the first US fixed-wing aircraft lost to enemy fire since the early days of the Iraq War — a gap of more than twenty years. Crew status and precise engagement details remain under active reporting.
The F-15E is not a stealth platform. It's a 1980s-era airframe, continuously upgraded, that survives contested airspace through electronic countermeasures, standoff weapons, and mission planning rather than low observability. Sending a non-stealth strike aircraft into one of the most heavily defended airspaces on the planet means the electronic warfare suite and mission planning chain were expected to compensate for the radar cross-section. They didn't.
The F-15E's self-protection stack has three layers, and all three are now under scrutiny.
AN/ALQ-135 (legacy ECM). The Tactical Electronic Warfare System has been the F-15's primary jammer since the late 1980s. Originally built by Northrop Grumman's Sanders lineage, it works in concert with the AN/ALR-56C radar warning receiver to detect, classify, and jam threat emitters. It has been upgraded through Band 1.5 and Band 2 iterations — but its architecture is fundamentally analog-era. Against single-emitter SAM systems, it was adequate. Against a networked IADS fusing data from search radars, fire-control radars, passive sensors, and infrared — the ALQ-135 was a known capability gap.
AN/ALQ-239 EPAWSS (the intended fix). BAE Systems won the ~$2.4 billion Engineering and Manufacturing Development contract around 2016 for the Eagle Passive Active Warning Survivability System. EPAWSS is a full-spectrum digital EW suite: radar warning, geolocation, active and passive jamming, and situational awareness — all on a software-defined, reprogrammable architecture. It is designed to counter exactly the kind of modern double-digit SAM threats Iran operates. The critical question is whether EPAWSS was installed on the downed aircraft. LRIP deliveries began reaching operational units in the 2024-2025 timeframe, but fleet-wide retrofit across ~200 F-15Es is an ongoing process. If this jet was still running the legacy ALQ-135, the loss is a procurement timing failure as much as a tactical one.
Mission Data Files (MDF). Even a capable EW suite is only as good as its threat library. MDFs are the software loads that tell the jammer what signal patterns to look for and how to respond. Generating and validating these files is a massive software effort — thousands of emitter modes, waveform parameters, and response techniques. If Iran deployed a radar mode or waveform variant not in the MDF, the jammer wouldn't recognize the threat until it was too late. MDF generation is handled by Reprogramming Labs at Eglin and Robins AFBs, with contractor support from BAE, L3Harris, and CACI.
Iran's integrated air defense system is not a single weapon. It is a networked kill chain, and that networking is the actual threat.
The S-300PMU-2, delivered by Russia starting in 2016, uses the 48N6E2 missile with engagement ranges around 200 km and altitude coverage to 27 km. The Tombstone engagement radar and Big Bird acquisition radar give it a search-and-fire capability that a single jammer struggles to defeat simultaneously. The Bavar-373, Iran's domestically produced long-range SAM, uses phased-array radar and Sayyad-4 missiles with claimed ranges of 200-300 km. Western analysts discount those claims, but even a 150 km envelope is a problem for a non-stealth platform.
The real upgrade is below the launcher level. Iran's Khatam al-Anbiya Air Defense HQ has spent a decade connecting these systems via fiber-optic command links, redundant radar coverage, and — critically — passive detection. A passive radar doesn't emit; it uses ambient RF energy (broadcast TV, cellular, even the target's own emissions) to triangulate. You cannot jam what doesn't transmit. Iran has also invested in infrared search and track (IRST) capabilities that operate entirely outside the RF spectrum. Against a passive/IR detection layer feeding targeting data to an active SAM battery, the F-15E's RF-centric self-protection suite has a fundamental architectural blind spot.
The Khordad-15 medium-range system, credited with downing a US RQ-4A Global Hawk drone in June 2019, adds another layer at 75-120 km with its own phased-array radar. Tor-M1 short-range systems cover the inner ring. This is defense-in-depth with overlapping kill zones.
For defense-tech developers, this shootdown is a forcing function. The systems that failed — or that might have prevented the loss — are increasingly software problems.
Cognitive EW. DARPA programs like BLADE and others have pushed machine learning into the EW loop: adaptive jamming that responds to novel waveforms in real time rather than relying on pre-loaded threat libraries. If the ALQ-135 couldn't handle an Iranian radar mode it hadn't been programmed for, a cognitive EW system — using ML models trained on signal intelligence — might have adapted. This is the frontier of EW software: real-time signal classification on FPGA hardware, inference at RF timescales (microseconds, not milliseconds), written in VHDL/Verilog with high-level synthesis from C++. BAE, Northrop Grumman, and L3Harris are all hiring aggressively for these roles.
JADC2 and mission planning integration. The Joint All-Domain Command and Control initiative is supposed to connect every sensor to every shooter. In practice, mission planning for F-15E strikes uses JMPS (Joint Mission Planning System) and the newer MPE (Mission Planning Environment) — tools that ingest EW threat data to route aircraft around known SAM envelopes. If the threat picture was wrong — either because Iranian systems were mobile and repositioned, or because passive radar nodes weren't in the database — the mission plan put the aircraft in an engagement zone it thought was clear. ABMS, the Air Force's contribution to JADC2, is supposed to provide real-time threat updates to airborne platforms. Whether that link was active and accurate during this mission is another open question.
The tech stack for practitioners. If you work in defense EW, the immediate impact looks like this: C/C++ for real-time embedded systems on the EW suite itself. FPGA programming (AMD/Xilinx and Intel/Altera) for signal processing at the RF front end. Python and MATLAB for ML model development and signal analysis in the lab. Palantir, Anduril, and the primes for data fusion and C2 integration. Nearly every position requires TS/SCI clearance, which remains the actual bottleneck.
Expect three immediate consequences.
First, EPAWSS retrofit will accelerate. Any F-15E still flying with the legacy ALQ-135 represents an unacceptable risk. BAE Systems' production line in Nashua, NH, is about to get very busy, and their subcontractor base will expand. Second, mission data file generation will get more resources and faster update cycles — the threat library problem is a software velocity problem. Third, the cognitive EW programs that were R&D curiosities last year are now operational necessities.
For defense-tech contractors and the developers they employ, this is not abstract. A twenty-year assumption — that US electronic warfare could reliably defeat integrated air defenses — just broke in the most visible way possible. The software that replaces that assumption is being written now.
So how is this not flagged, whereas this other post lasted literally minutes before being flagged? https://news.ycombinator.com/item?id=4761205375000+ palestinians killed, arguably one of the defining crimes of our age are not worth HN discussion (“politics”) but one F15E shot down in
There’s a lot of speculation about how this was achieved, but little mention of the likely weapon system that was used: https://israel-alma.org/the-growing-air-defense-capabilities...The SA-67 is essentially a hybrid surface-to-air missile and loitering drone that operates like an air
To unpoison y'alls priors, I want to remind HN that in the Kosovo air campaign, the Yugoslavs took out a nighthawk (F117) and an F16. They claimed more nighthawks that limped home.The F117 is a very stealthy plane, given its geometry (flat panels). Yet a 1960s radar with essentially no digital
Military aviators train for this, being alone behind enemy lines (look up SERE school if you’re curious, one of the craziest training courses outside of special forces) and there is a special force just for aviator recovery behind enemy lines, US AirForce Pararescue. Hopefully they’ll get the aviato
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
During the entire gulf war (Iraq, 1990-91), only two F-15s were shot down via surface-to-air engagement. At the time, Baghdad was known to have the highest density of SAM protection out of any city in the world.An F-15 being shot down in Iran after weeks of strategic bombing of their anti-air defens