Abstract
Current U.S. Air Force targeting doctrine (AFDP 3-60, Targeting) outlines five principles that govern the mechanics of the targeting cycle: objectives-based, effects-based, interdisciplinary, systematic, and estimative. However, this framework fails to capture the most consequential judgment a commander makes in conflict: the deliberate acceptance of uncertainty when employing novel or adapted capabilities. Through a historical case study of the Israeli Air Force’s (IAF) Operation Mole Cricket 19 in the Bekaa Valley in 1982, this article argues for the formal adoption of a sixth targeting principle: calculated risk. While the IAF successfully applied the five existing principles to dismantle a dense Syrian integrated air defense system, their lopsided victory ultimately relied on the willingness to execute an unproven, newly integrated sensor-to-shooter network. By codifying calculated risk, modern targeting doctrine can move beyond a bureaucratic checklist mentality and explicitly empower commanders to accept uncertainty when the operational advantage justifies the consequences of failure.
Air Force Doctrine Publication (AFDP) 3-60, Targeting outlines five core principles of targeting: objectives-based, effects-based, interdisciplinary, systematic, and estimative. Together, they provide a logical framework connecting military action to a commander’s objectives. Yet, while doctrine describes how to construct a targeting process, it fails to capture the most consequential judgment a commander makes in conflict: when to accept the remaining risk of employing a new or adapted capability, method, or concept under combat conditions. Operation Mole Cricket 19 offers a particularly instructive case study.
On June 9, 1982, the Israeli Air Force (IAF) dismantled Syria’s integrated air defense system (IADS) in Lebanon’s Bekaa Valley. The operation combined electronic warfare, unmanned aerial vehicles, real-time intelligence, anti-radiation weapons, precision strike, and air-to-air combat into a coordinated assault. While the campaign illustrates all five principles of AFDP 3-60, it also introduces a sixth: calculated risk.
The IAF’s success depended not just on applying sound targeting tactics, but on a deliberate willingness to accept that a newly integrated combination of capabilities might fail. That disciplined acceptance of risk, not just the ingenuity of the plan, is why the campaign succeeded—and why it deserves formal recognition in modern targeting doctrine. For a targeteer who has never run a campaign like it, Mole Cricket 19 offers an example doctrine alone cannot: a complete story of the failure, adaptation, and execution to draw on before the decision becomes their own.
Failure Before Success
The roots of Mole Cricket 19 lie in the setbacks of the 1973 Yom Kippur War. Soviet-built surface-to-air missile (SAM) systems, particularly the mobile SA-6 “Gainful,” inflicted devastating losses on the IAF, accounting for the majority of the roughly 100 Israeli aircraft lost, epitomized by the failure of Operation Dugman 5 on the Golan Heights, where outdated intelligence on SAM battery locations and a dangerous approach path led Israeli jets into the crosshairs of the Syrian network.
The challenge stemmed from a lack of operational synchronization, not raw technology. A formal IAF lessons-learned document circulated on January 30, 1974, defined the requirement precisely: the response to the SAM threat could not rest on any single weapon but required “a combat system” to integrate intelligence, communications, control, training, and armament. The IAF lacked an integrated system to fuse real-time intelligence, electronic warfare (EW), command and control (C2), and strike assets into a unified system capable of defeating a mobile, dense air defense network. In modern military terms, this is known as the sensor-to-shooter loop or the kill chain.
The cost of that gap was stark. On October 17, 1973, during the Yom Kippur War, the day after Israeli forces crossed the Suez Canal, four aircraft were ordered to attack Syrian SAM batteries using an outdated low-high-low flight profile. Electronic Warfare Division commander Col. Eliahu Yitzhaki warned IAF chief Benny Peled it was a suicide mission; the order stood. All four aircraft were hit, and six airmen were killed or captured. The next day, the IAF grounded its fleet and turned to the Electronic Warfare Division to fix the problem. The result, Operation Nutcracker 23 (Mifetzach 23), flown on October 20, was planned in full synchronization with EW—the aircraft flew high, completed their tasks, and not one was hit. As Yitzhaki put it, the revolution had begun.
The success of Nutcracker 23 was an immediate tactical fix, but the IAF recognized that a sustainable solution required a fundamental, long-term investment in command-and-control architecture. This decade-long effort began with a simple vision. “We’re going to build a command center here for attacking the SAM batteries,” recalled Lt. Col. Amos Amir, then head of operations, telling his team. “All the information about the location of the batteries from all the different sources will flow into this computer in real time—not where they were 10 hours ago. And according to this intel, we will direct our fighter pilots so they can know where to aim.” The resulting command architecture was built to solve the problem of Syrian and Egyptian batteries moving faster than Israel’s targeting cycle could track them.
With initial estimates that the system would take five years to build, the head of the Air Division rejected the proposal. Major Aviem Sela, head of the IAF attack branch, worked around the bureaucracy anyway. They recruited civilian volunteers at the Weizmann Institute, including an ultra-Orthodox programmer who built a working prototype in three weeks.
Over the intervening years, the IAF built specialized units trained in anti-radiation missiles (ARMs), adapted surface-to-surface missiles for anti-SAM roles, expanded EW capabilities, and fielded precision-guided munitions (PGMs). By 1982, the IAF was prepared to test this system. The confrontation came in the skies over Lebanon.
The Bekaa Valley Campaign
Operation Mole Cricket 19 occurred during Operation Peace for Galilee, the Israeli invasion of Lebanon launched on June 6, 1982, in response to the attempted assassination of Israel’s ambassador to the United Kingdom. As Israeli ground forces pushed toward the Jezzine road junction on June 8, a clash with Syrian armor destroyed 32 Syrian tanks and downed four Syrian jets; Damascus responded by moving five additional SA-6 batteries from the Golan Heights into the Bekaa Valley, expanding the network to nineteen batteries. Believing this reinforced air defense network posed an unacceptable threat to ground operations, the Israeli government authorized the IAF to strike on June 9.
The strike opened with a wave of Mastiff and Scout remotely piloted vehicles (RPVs) launched as decoys to draw Syrian fire. Syrian batteries showed poor target discrimination and fired on the drones en masse, revealing their engagement radars. Once a Boeing 707 electronic-intelligence aircraft achieved positive identification of the active SAM engagement radars, the IAF struck in tightly sequenced phases: artillery and ground-launched Ze’ev missiles engaged radars in the southern Bekaa while F-4 Phantoms fired Shrike and Standard ARM missiles at radars farther north, blinding the batteries; F-4s and F-16s then flew low-level, terrain-masking runs to destroy the blinded radar vans and SA-6 launchers with cluster munitions and general-purpose bombs; and when Syria scrambled its fighters to contest the strike, Israeli interceptors—vectored by an E-2C Hawkeye airborne warning and control system (AWACS)—engaged them with zero air-to-air losses.
Accounts differ on the precise details of the initial strike: RAND’s contemporaneous reconstruction puts it at roughly ten minutes and 17 of 19 SA-6 sites destroyed, while a 2016 retrospective citing IAF veterans describe a 110-minute strike that destroyed 15 of 19. All agree, however, that the initial attack rendered most of the Bekaa Valley SAM network ineffective in a remarkably short window, without the loss of a single Israeli aircraft (though several returned with battle damage). The remaining sites and SAM batteries the Syrians moved into the valley overnight were destroyed over the following days.
The air battle that followed was, by many accounts, the largest in the history of Middle East air warfare. F-15 and F-16 combat air patrols had been positioned west of the Bekaa Valley in advance, and an E-2C Hawkeye—its radar able to track Syrian MiGs the moment they left their runways—vectored Israeli fighters onto them while jamming denied Syrian pilots of contact with their ground controllers. At its height, some 90 Israeli and 60 Syrian jets were airborne simultaneously. The mismatch was as much about pilot skill as equipment: Syrian formations, cut off from their controllers, lost all semblance of air discipline, and one Western military attaché who watched part of the battle from the ground recalled Syrian fighters flying aimless “figure-eights” with no apparent plan. The IAF downed 23 Syrian fighters on June 9 and 15 more the following day; by the end of July, it had destroyed 85 Syrian aircraft in the campaign’s cumulative air battles without losing a single aircraft to enemy fighter action.
By the end of September 1982, the IAF had destroyed some 29 SAM sites across seven raids and downed 85 Syrian MiGs, at a cost of two Israeli aircraft—both lost to ground fire, none to Syrian fighters.
The success of the Bekaa Valley campaign was no accident. It was the direct result of a targeting philosophy that, while not formally codified at the time, aligns closely with the principles in modern doctrine. The keys to the IAF’s lopsided victory can be found by analyzing the operation through that lens.
Analyzing the Doctrinal Principles
Operation Mole Cricket 19 illustrates the five principles of targeting currently codified in AFDP 3-60:
- Objectives-Based: The Syrian SAM network, a single target system, was not targeted simply because it could be destroyed, but because it restricted the IAF’s freedom of maneuver. The objective, enabling ground operations, dictated the target list, ensuring that tactical execution remained aligned with operational objectives.
- Effects-Based: Some of the most decisive enabling actions in the Bekaa Valley were non-kinetic. RPV decoys did not destroy targets; they created the cognitive effect of provoking Syrian operators into activating their radars. By targeting the electromagnetic spectrum rather than just physical launchers, the IAF neutralized the entire network’s combat power. In the IAF’s own official retrospective, close to 100 Israeli aircraft took part in the operation carrying no weapons at all; their sole function was to jam and deceive.
- Interdisciplinary: Success required the close integration of RPV operators, EW specialists, intelligence analysts, AWACS battle managers, artillery units, and strike pilots. The output of one discipline (EW/Decoys) directly enabled the next (intelligence localization and strike execution).
- Systematic: The operation followed a highly structured sequence: Deceive, Find, Disrupt, Finish, and Assess. This loop was backed by nearly a decade of rigorous intelligence preparation of the battlefield, engineering, and rehearsal, proving that a systematic process provides order in the fog of war.
- Estimative: Israeli planners accurately anticipated Syrian reactions. They predicted that SAM operators would lock onto the decoys and that Syria would scramble fighters to intercept the strikes. The IAF positioned interceptors in advance and paused operations overnight when Syria altered its deployment, demonstrating an understanding of the adversary as an adaptive system.
The Missing Principle: Calculated Risk
While the five standard principles explain how the targeting process functioned, they do not explain why Israeli commanders were willing to stake the campaign on a concept extensively tested in development and exercises but never fully validated under comparable combat conditions.
That judgment points to a sixth principle: calculated risk. IAF commander David Ivry’s real-time decisions during the operation illustrate what this principle looks like in practice. The Israeli plan relied on a series of nested, unvalidated assumptions. Syrian radar operators had to react to the RPVs. Israeli EW systems had to successfully disrupt Soviet-designed frequencies under combat conditions. C2 networks had to pass target coordinates fast enough to hit mobile launchers before they relocated. Air-to-air assets had to successfully isolate the airspace.
If any of these assumptions failed, Israeli strike forces would have flown directly into an intact, alerted, and highly lethal air defense network—potentially repeating the disaster of 1973.
Israeli commanders accepted that risk anyway, not out of recklessness, but because they judged the potential payoff worth the remaining uncertainty—and because a decade of disciplined preparation had reduced that uncertainty to an acceptable level.
Doctrinal Principle (Proposed)
Targeting should deliberately reduce uncertainty through analysis, experimentation, and rehearsal, then permit commanders to accept the remaining risk when the expected operational advantage justifies the consequences of failure.
Mole Cricket 19 was not a hasty gamble; the IAF spent years engineering solutions, modifying weapons, and practicing concepts. But no amount of rehearsal could eliminate the final uncertainty of combat. At some point, a commander had to decide whether the expected outcome justified the risk of failure.
None of the five existing principles directly forces a commander to answer this ultimate question. Objectives-based targeting defines the goal; effects-based targeting connects actions to outcomes; interdisciplinary targeting fuses capabilities; systematic targeting structures the process; and estimative targeting forecasts adversary behavior. All five inform risk, but none explicitly demands the command decision to accept it.
Mission command and the Joint Risk Analysis Methodology (JRAM) might seem to cover this ground already. They do not, because neither answers the question calculated risk asks.
Mission command governs who decides, decentralizing authority to commanders trusted to exercise initiative. It is silent on what they should decide when the choice is between a proven method that has already failed and an unproven one that might not. It would have given subordinate IAF commanders the authority to choose; it offered no guidance on which way to choose.
JRAM is a mitigation framework: it makes a chosen course of action safer, not whether to choose an unproven course over a safer, proven one. Applied rigorously to Bekaa Valley, JRAM would have flagged the unvalidated sensor-to-shooter architecture as the hazard—and the doctrinally conservative response may have been to fall back on tactics already known to work, however costly they had proven in 1973.
Both principles are content-neutral: they apply the same way whether a commander chooses the boldest option or the safest one. Calculated risk is not. It is a doctrinal expectation that targeting must sometimes bias toward experimentation—that innovation under fire requires preferring the unproven concept over the proven failure, and that doctrine should say so explicitly rather than leave it to individual command temperament.
Although risk is inherent in all military decision-making, it is often treated as a byproduct to be managed under “systematic” or “estimative” targeting, rather than confronted directly.
But a targeting process can be flawless, systematic, and backed by excellent intelligence estimates, yet still carry a high probability of failure. Systematic and estimative targeting manages the knowns and the probabilities; calculated risk addresses how a commander handles the unknowns and the consequences of failure.
That distinction matters most when confronting novel problems where established methods have already failed. Had the IAF refused to employ any concept unproven in combat, it would have been stuck relying on the same tactics that failed in 1973. Innovation requires accepting uncertainty. Codifying calculated risk as a principle of targeting moves doctrine past a checklist mentality and explicitly empowers commanders to adopt creative, non-traditional solutions when the stakes demand them.
Enduring Lessons for Modern War
The tactical hardware of Mole Cricket 19, the F-15s, AGM-45s, and early Scout drones, belongs to a bygone era. The next major targeting challenge will not look like a Syrian SAM network in the Bekaa Valley; it may involve contested electromagnetic environments, hypersonic weapons, artificial intelligence, cyber operations, or capabilities that have not yet reached the battlefield.
Yet, the lessons of the Bekaa Valley endure:
- The objective must dictate the target, not vice versa.
- Non-kinetic effects can create kinetic opportunities.
- The sensor-to-shooter loop must operate in near-real-time.
- Planners must anticipate, rather than merely react to, an adaptive adversary.
But the most critical lesson is that technological and operational innovation will always require stepping into the unknown. No targeting doctrine, no matter how systematic, can eliminate the final margin of uncertainty in war. By adding calculated risk to the principles of targeting, doctrine would acknowledge a reality that no process can eliminate: at some point, a commander must decide whether the potential advantage justifies the consequences of failure. Most targeteers will not get a Bekaa Valley of their own before they are asked to make that call for the first time. Mole Cricket 19 is offered here so that when it comes, the decision is not unfamiliar.
The views expressed in this article are solely those of the author and do not reflect the official policy or position of the U.S. Army Western Hemisphere Command, the Department of the Army, the Department of Defense, or the U.S. Government.
