Twelve days separated a parked car on a Kashmir highway from twelve fighter jets crossing into Pakistani airspace, and that compression of time is the entire story of the year India stopped treating the Line of Control as the edge of what it would do. On February 14, 2019, a vehicle packed with explosives tore through a Central Reserve Police Force convoy near Lethpora in Pulwama district, killing forty personnel in the deadliest single strike against Indian security forces in three decades of the Kashmir insurgency. On February 26, the Indian Air Force answered with a bombing run near Balakot in Khyber Pakhtunkhwa, the first occasion since the 1971 war that Indian combat aircraft had struck inside undisputed Pakistani territory. What happened across those twelve days, and in the aerial duel over the Rajouri sector that followed on February 27, did far more than punish a terror group. It dismantled a barrier that had held for forty-eight years, and it set a precedent of barrier-crossing that would shape every confrontation between the two states for the next six years and beyond.

This is one link in a chain that runs from the Kandahar tarmac in 1999 to the missile salvoes of 2025, and it is a link with a particular function. Earlier nodes in the chain established that India would absorb mass-casualty terrorism, then established that India would retaliate, then established that India would retaliate across the Line of Control on the ground. Pulwama and Balakot established something different and more consequential: that the ground was no longer the limit. Once a barrier in this conflict is broken, it is never rebuilt. It becomes the floor for the next response. Understanding why that is true, and what it means for a relationship between two nuclear-armed states, requires walking the twelve days carefully, then stepping back to see the ladder they helped build.

The Preceding Link

To understand why the Balakot airstrike landed the way it did, the analysis has to begin two and a half years earlier, with a different attack and a different response. On September 18, 2016, four heavily armed men crossed the Line of Control and assaulted an Indian Army administrative base near the town of Uri in Jammu and Kashmir’s Baramulla district. They struck before dawn, when much of the camp was asleep in tents, and an early grenade detonated a fuel store. Nineteen soldiers died, most of them burned in the fires that swept the canvas accommodation. It was, at that point, the deadliest attack on the Indian Army in twenty-six years. The men who carried it out belonged to Jaish-e-Mohammed, the same organization whose name would dominate the events of 2019. The pattern of the Uri attack was old and familiar: an infiltration across the de facto border, a high body count, a claim of deniability from Islamabad, and an expectation in Rawalpindi that India would respond with diplomatic protest and little else.

That expectation was wrong. Eleven days after Uri, on the night of September 28 into the morning of September 29, Indian Army special forces crossed the Line of Control at multiple points and struck what New Delhi described as terrorist launch pads on the Pakistani-administered side. The government publicized the operation rather than denying it, and the phrase “surgical strikes” entered the Indian political vocabulary as a permanent fixture. The tactical effect of the 2016 surgical strikes remains contested, as such cross-border raids almost always are, but the tactical effect was never the point. The point was the precedent. For the first time, India had publicly acknowledged sending uniformed soldiers across the Line of Control to conduct an offensive operation, and it had survived the consequences without a war and without nuclear escalation. The fuller account of how that precedent reshaped Indian doctrine belongs to the previous barrier in this chain, but its relevance to Pulwama and Balakot is direct. A barrier had already fallen. The ground crossing of the Line of Control was no longer unthinkable. It had become a known quantity, a tool in the box.

That mattered because barriers in the India-Pakistan relationship do not regenerate. Once New Delhi had crossed the Line of Control on the ground and absorbed the aftermath, the question for any future crisis was no longer whether India would respond inside Pakistani-controlled space. The question had moved on to how far, and by what means. Pakistan’s planners understood this too, which is part of why the strategic environment after 2016 was more brittle, not less. The surgical strikes had not deterred Jaish-e-Mohammed; the organization continued to recruit, train, and operate. What the strikes had done was raise the expected Indian response to the next major attack. Each side now knew that the floor had risen. When the next mass-casualty attack came, India would have to do at least what it had done after Uri, and probably more, or risk appearing to have lost the deterrent value it had spent political capital to build.

It helps to set the surgical strikes against the longer history they broke with. The reference case for Indian restraint is the response to the December 13, 2001, attack on the Indian Parliament, an assault carried out by gunmen linked to Jaish-e-Mohammed and Lashkar-e-Taiba that struck at the symbolic heart of the Indian state. The Indian response was Operation Parakram, a massive mobilization of ground forces along the international border that lasted roughly ten months and that, in the end, was stood down without an offensive being launched. Parakram is the textbook example of the trap that the nuclear overhang created for India: a ground army mobilized at enormous cost, presenting New Delhi with an all-or-nothing choice between a full war that the nuclear dimension made close to unusable and a humiliating demobilization. India chose demobilization. The lesson the Indian security establishment drew over the following years was that conventional ground mobilization was a blunt instrument, slow to assemble, impossible to calibrate, and easy for an adversary to wait out. That lesson is the backdrop against which the turning point at Pathankot and the surgical strikes have to be read.

The years between the 2008 Mumbai attacks and 2016 are sometimes described as India’s decade of strategic restraint, and the description is accurate as far as it goes. India absorbed major attacks during that period and did not respond with offensive military action. What is less often noted is that the restraint was not passive resignation; it was, in part, the period during which the capabilities and the doctrinal thinking that would enable the surgical strikes, Balakot, and the operations beyond were being developed. The 2016 Pathankot airbase attack, in which Jaish-e-Mohammed gunmen infiltrated one of India’s most sensitive military installations and killed seven security personnel over a prolonged siege, came at the end of that decade and immediately preceded Uri. Pathankot demonstrated that engagement with Pakistan, attempted briefly in late 2015, had failed to alter the behavior of militant networks operating from Pakistani soil. By the time Uri occurred in September 2016, the Indian establishment had concluded that the restraint model had run its course and that a more active model was required. The surgical strikes were the first expression of that conclusion, and Balakot was the second.

The intervening years between Uri and Pulwama were not quiet. The Jaish network, rebuilt and protected, kept its operational tempo high in Kashmir. The organization had a particular signature: a willingness to use fidayeen tactics, attackers who expected to die, and an increasing reliance on locally recruited Kashmiri youth rather than infiltrators from across the border. That shift in recruitment is central to the Pulwama story, because the man who drove the explosives-laden vehicle on February 14, 2019, was not a Pakistani who had crossed the Line of Control. He was a young man from Pulwama district itself, radicalized at home, and his profile would complicate every subsequent claim about how the attack should be understood. The organization behind the bombing had learned to fight with local hands while drawing on cross-border resources for the components that local hands could not easily produce, and that hybrid model is what made the attack both possible and, for India, infuriating to attribute cleanly.

By early 2019, then, the preceding link had set three conditions that would govern what came next. The ground barrier was already broken, which meant the next Indian response would have to exceed a ground raid to register as escalation. The Jaish network was intact and operational, which meant another major attack was a matter of timing rather than possibility. And India was four months from a general election, which meant that whatever response New Delhi chose would be made under intense domestic political pressure and intense domestic political scrutiny. Those three conditions did not cause Pulwama. They shaped the corridor through which the response to Pulwama would have to travel.

What Happened

The Convoy on the Jammu-Srinagar Highway

The Jammu-Srinagar National Highway is the single most important road in the Kashmir Valley, the lifeline that connects the region to the rest of India, and on February 14, 2019, it carried an unusually large movement of Central Reserve Police Force personnel. A convoy of seventy-eight vehicles was traveling from the transit camp at Jammu toward Srinagar, carrying roughly twenty-five hundred CRPF personnel who were returning to duty after leave. The size of the movement was itself a vulnerability. Heavy snowfall had closed the highway for two days beforehand, and the backlog of personnel waiting to travel had built up, so the convoy that finally moved was far larger than a routine rotation. A larger convoy meant a longer column, a slower pace, and a more predictable presence on a road that ran for hours through populated districts.

At roughly 3:30 in the afternoon, near the village of Lethpora about thirty kilometers short of Srinagar, a civilian sport utility vehicle pulled alongside one of the buses in the column and detonated. The bus was carrying CRPF personnel, and the explosion destroyed it almost completely. Forty personnel were killed, along with the bomber. Initial assessments concluded the vehicle had carried more than three hundred kilograms of explosive material, including a quantity of the high explosive RDX and a larger mass of ammonium nitrate, the kind of fertilizer-derived charge that has been a staple of vehicle bombs across South Asia and the Middle East. The scale of the charge explains the scale of the casualty count. This was not a small device intended to harass; it was a vehicle-borne improvised explosive device built to destroy a bus and everyone inside it.

Within hours, Jaish-e-Mohammed claimed responsibility and released a video identifying the bomber as Adil Ahmad Dar, a young man from the Gundibagh area of Pulwama district. The pre-recorded statement, a now-familiar genre of militant propaganda, framed the attack in the language of religious war and grievance. Dar’s biography mattered, and it would be argued over for years. He was a local, not an infiltrator. By accounts that emerged afterward, he had left home in early 2018 and joined the militancy, and his family described a young man who had been affected by the violence and humiliations of life under a heavy security presence. None of that biography excuses the attack or diminishes the deliberate cruelty of driving a bomb into a bus of human beings. What it does is establish a fact that complicates the politics: the trigger-puller was a product of Kashmir, even if the explosives, the training, and the organizational direction reached back across the Line of Control.

The intelligence picture in the days before the attack adds a painful layer. Indian agencies had generated multiple warnings in the period leading up to February 14, and reporting after the attack indicated that the security establishment had received numerous intelligence inputs pointing to a possible strike on a convoy. Two days before the bombing, Jaish had circulated a video of a suicide attack carried out in Afghanistan, a piece of propaganda that read in hindsight as a signal of intent. The decision to move the convoy by road rather than by air, despite the option of airlifting personnel and despite the warnings, became a subject of bitter recrimination. The fuller forensic account of the convoy, the route, the device, and the security failures belongs to the dedicated treatment of the attack, but the essential point for the chain is this: a major terror attack with a body count of forty had landed on Indian soil, the organization responsible was Jaish-e-Mohammed, and the country was four months from a national vote. The corridor for the response had just narrowed to a single direction.

The Mirage 2000s and Operation Bandar

For twelve days, India’s response was invisible. There were diplomatic measures, the withdrawal of most-favored-nation trade status, a steep hike in customs duties on Pakistani goods, a dossier handed to Islamabad. There were the expected statements of resolve from the political leadership. What was not visible was the planning underway in the Indian Air Force, which had been tasked with delivering a response that would exceed the surgical strikes in reach and in symbolism.

In the early hours of February 26, that planning produced an operation the Indian side later codenamed Operation Bandar. Indian media, citing official sources, reported that twelve Mirage 2000 fighter jets of the Indian Air Force were used in the strike, supported by an array of force-multiplier aircraft: Sukhoi Su-30MKI fighters flying combat air patrol, an indigenous Netra airborne early warning and control aircraft, an Israeli-built Heron unmanned aerial vehicle for surveillance, and Ilyushin Il-78 tankers for aerial refueling. The strike aircraft were reported to be carrying precision-guided munitions, with Israeli-origin SPICE 2000 standoff bombs the weapon most consistently identified in the reporting. The target was a Jaish-e-Mohammed facility, described by India as a training camp, located on a hilltop near Jaba village, in the vicinity of the town of Balakot in the Mansehra district of Khyber Pakhtunkhwa province.

The geography is the heart of the matter. Balakot is not in Pakistani-administered Kashmir. It sits in Khyber Pakhtunkhwa, in Pakistan proper, well beyond the Line of Control and beyond any territory whose status is disputed. When the Indian aircraft released their weapons in the vicinity of the Jaba hilltop, they did so deep inside undisputed Pakistani sovereign space. That had not happened since the 1971 war. The 2016 surgical strikes had crossed the Line of Control, a contested boundary in a contested region. Balakot crossed an international understanding far older and far more load-bearing: the tacit rule that whatever India and Pakistan did to each other, they did it in or around Kashmir, and Pakistan’s heartland provinces were off the table. The Indian Air Force had just demonstrated that the heartland was no longer off the table. That is the airstrike in its full significance, and it is why the operation belongs in this chain as a barrier-crossing event rather than merely a retaliatory one.

What the bombs actually hit is a separate question, and an honest account has to treat it as genuinely contested. India’s initial characterization, delivered by the Foreign Secretary, described the strike as a preemptive and non-military operation against a terrorist training facility, and Indian political figures and media subsequently circulated figures of a large number of militants killed, with numbers in the range of three hundred to three hundred and fifty appearing in coverage. Pakistan’s account was the mirror opposite. Islamabad, whose military was the first to announce the airstrike on the morning of February 26, said the Indian aircraft had jettisoned their payloads in an uninhabited wooded area on the hilltop and had hit nothing of consequence. In the weeks that followed, satellite imagery analyzed by independent groups, including the Atlantic Council’s Digital Forensic Research Lab, the Australian Strategic Policy Institute, and commercial imaging firms, indicated that the principal structures on the Jaba site were still standing and showed no evidence of having been struck. On April 10, roughly six weeks after the operation, a tightly managed visit by international journalists to the hilltop found the largest building intact and showed no sign of recent damage or rebuilding.

The damage-assessment debate is real and should not be papered over. The most defensible reading of the available evidence is that the tactical results of Balakot were modest at best and quite possibly negligible, and that the casualty figures that circulated in India were not supported by the imagery. That assessment is uncomfortable for the triumphalist version of the story, and it is the version of the story that the comparison with the later 2025 strikes makes unavoidable. But the tactical ambiguity does not erase the strategic fact. Whether or not the bombs killed anyone, the aircraft flew. The barrier was crossed. The map of what India would do had been redrawn, and a redrawn map does not depend on the body count to function.

The Twelve Days Between

The interval between the convoy bombing and the airstrike deserves its own treatment, because the temptation in hindsight is to read those twelve days as a smooth march from outrage to retaliation. They were not smooth. They were a period of intense and partly improvised decision-making under a clock that everyone involved could hear ticking.

The political signal came almost immediately. Within a day of the attack, the Indian leadership made public statements indicating that the security forces had been given a free hand and that those responsible would pay a heavy price. Language of that kind, delivered at the highest level, functions as a commitment device. Once a head of government has told a grieving nation that a heavy response is coming, the space for a purely diplomatic answer has effectively closed. The statements of February 15 and 16 did not specify what the response would be, but they foreclosed the option of no military response at all.

What followed was a planning process inside the Indian Air Force that had to resolve a series of hard questions in a compressed window. The first was target selection. A strike intended to signal reach into Pakistan proper, rather than another raid near the Line of Control, required a target deep enough to make the point and a target with a defensible counter-terrorism rationale. The Jaba hilltop facility near Balakot, associated in Indian assessments with Jaish-e-Mohammed, satisfied both criteria: it sat in Khyber Pakhtunkhwa, unambiguously inside Pakistan, and it could be described as terrorist infrastructure rather than a Pakistani state asset. The second question was the weapon. Precision-guided standoff munitions allowed the strike aircraft to release their payloads without overflying the immediate target area, reducing exposure to Pakistani air defenses, and the SPICE 2000 was the system reported as central to the plan. The third question was the supporting package: the combat air patrol, the early-warning aircraft, the refueling tankers, and the surveillance drone that together made a deep penetration survivable.

There was also a meteorological dimension that is easy to overlook. The operation depended on conditions over the target, and reporting after the fact indicated that weather considerations influenced the timing of the strike within the available window. A deep-penetration night strike is a demanding undertaking, and the planners had to balance the political pressure for speed against the operational requirement for conditions that gave the mission a reasonable chance of success and a reasonable chance of recovering every aircraft. The twelve-day interval was, in this sense, not a delay but a compression: it was about as fast as a strike of that ambition could responsibly be mounted, and the fact that it was mounted that fast is itself a measure of how much the political clock was driving the process.

Through all twelve days, the Indian government also pursued the diplomatic and economic track in parallel, and that parallel track had a purpose beyond its direct effects. By withdrawing most-favored-nation status, raising customs duties, and circulating a dossier internationally, New Delhi was building the documentary and rhetorical case that whatever military action followed would be a response to terrorism rather than an unprovoked act. The diplomatic track was, in part, the preparation of the ground on which the military track would later be defended. When the aircraft flew on February 26, the framing that they had struck a terrorist facility, not the Pakistani state, had already been seeded for twelve days.

The Skies Over Rajouri and the Capture of a Pilot

The Balakot airstrike did not end the crisis. It opened its most dangerous phase. Pakistan, having been struck inside its own heartland, faced its own version of the pressure India had faced after Pulwama: a domestic expectation that the military would answer, and a strategic need to demonstrate that Indian aircraft could not operate over Pakistani territory with impunity. On the morning of February 27, the Pakistan Air Force conducted its own cross-border operation, sending aircraft toward the Indian side in the Rajouri and Naushera sectors of Jammu and Kashmir. Pakistan described the action as a demonstration of capability, a strike near but deliberately not on Indian military targets, intended to show that it could reach across the line as India had.

The Indian Air Force scrambled to intercept, and an aerial engagement developed over the Line of Control. In the course of that engagement, an Indian MiG-21 Bison, an aging but upgraded fighter, was shot down. Its pilot, Wing Commander Abhinandan Varthaman, ejected and came down on the Pakistani-administered side of the Line of Control, where he was captured by Pakistani forces. India claimed that in the same engagement Abhinandan had shot down a Pakistani F-16 before his own aircraft was hit. Pakistan denied losing any aircraft. The F-16 claim became one of the most disputed elements of the entire episode. Independent defense analysts found India’s evidence for the F-16 kill to be circumstantial, and the absence of a confirming announcement from the United States, which as the supplier of the F-16 fleet would have had reason to account for any loss, weighed against the Indian claim. The honest assessment is that the F-16 shootdown was never established to a standard that a neutral analyst would accept.

There was a further loss on the Indian side that received far less attention at the time and that complicates any clean narrative of the day. During the confusion of February 27, an Indian Mi-17 helicopter was brought down near Budgam, and six Indian airmen aboard and one civilian on the ground were killed. The cause was eventually acknowledged to have been friendly fire: Indian air defenses, operating in a high-tension environment with multiple aircraft in the sky, had downed one of their own helicopters. The acknowledgment came only months later. The Budgam incident is a sober reminder of a recurring feature of these escalations: the fog that descends once aircraft are airborne and weapons are released produces casualties that do not fit either side’s preferred story, and those casualties tend to be acknowledged slowly or not at all.

The capture of Abhinandan Varthaman transformed the crisis from a contest of strikes into a hostage situation with a face. Footage of the captured pilot circulated immediately, and his treatment, his composure, and ultimately his fate became the emotional center of the episode for both publics. On February 28, Pakistan’s Prime Minister, Imran Khan, announced that the pilot would be released as what he framed as a gesture of peace. On March 1, Abhinandan walked back across the Wagah border crossing into India. He was later awarded the Vir Chakra, a wartime gallantry decoration. The return of the pilot was the event that allowed both governments to step back from the ledge. It gave Islamabad a way to claim the moral high ground of restraint and gave New Delhi the return of its officer without a humiliating negotiation. But the return also did something more complicated, which the analysis of consequences has to take seriously: it muddied the question of who had won.

Why It Happened

The causal account of the Pulwama-Balakot escalation has to operate at three levels: the level of Jaish-e-Mohammed’s decision to strike, the level of India’s decision to respond with airpower, and the level of the structural pressures that made both decisions feel, to the actors involved, close to inevitable.

Jaish-e-Mohammed’s reasons for the Pulwama attack are the least mysterious. The organization is a militant enterprise whose stated purpose is the violent contestation of Indian control over Kashmir, and a mass-casualty attack on Indian security forces serves that purpose directly. It generates propaganda, it demonstrates relevance to potential recruits and funders, and it imposes a cost on the Indian state. The choice of a vehicle-borne device against a convoy reflected a tactical evolution. Earlier Jaish operations had favored fidayeen assaults on fixed installations, the model used at Uri and at the Pathankot airbase in 2016. The convoy bombing was a different design, requiring a different skill set: the construction of a large, stable vehicle charge, the acquisition of explosive precursors, and the recruitment and preparation of a driver willing to die. The use of a local Kashmiri as the bomber reflected the organization’s adaptation to a security environment in which infiltration across the Line of Control had become harder and in which a homegrown attacker offered both operational convenience and a propaganda narrative of indigenous resistance.

The question of how directly Pakistan’s state apparatus was involved in Pulwama is the genuinely contested causal question, and it deserves to be handled with care rather than asserted. The bomber was local. The organization that claimed the attack, Jaish-e-Mohammed, has a long and well-documented history of operating from Pakistani soil with a degree of freedom that is difficult to explain without at least the tolerance of elements of the Pakistani security establishment. The sophistication of the device, the quantity of military-grade explosive involved, and the organizational coordination required to plan and execute the operation all point toward resources beyond what an isolated local cell would typically command. The most defensible assessment is not that Pulwama was a direct operation run by a Pakistani intelligence officer, and it is not that Pulwama was a purely indigenous act with no external input. It is that the attack sat in the gray zone that has always defined this conflict: an organization sheltered and tolerated on Pakistani territory, drawing on cross-border resources, executing through local hands, in a manner that allowed Islamabad to deny direction while India held it responsible for the shelter. The man who founded and led that organization, whose camps were named as Balakot’s intended target, is profiled in detail as the Jaish founder, and his decades of protected operation are the strongest single piece of evidence in the Indian case.

The radicalization of Adil Ahmad Dar is worth dwelling on, because it is the part of the causal account that is most uncomfortable and most often skipped. Dar was not recruited and dispatched from a camp across the Line of Control. He was a young man from Pulwama district who, by the accounts that emerged after his death, had been drawn into the militancy at home over a period of roughly a year. A security environment characterized by a heavy troop presence, frequent cordon-and-search operations, and the cumulative friction of life in a militarized zone produces a population of young men among whom an organization like Jaish-e-Mohammed can recruit. None of this transfers moral responsibility away from the man who chose to drive a bomb into a bus, and none of it transfers responsibility away from the organization that armed and directed him. But a causal account that ignores the local recruitment pool is an incomplete account, and incomplete accounts produce policy that addresses only the cross-border supply of explosives and not the local supply of willing attackers. The hybrid model that made Pulwama possible, cross-border resources combined with local recruitment, means that an Indian response aimed only at Pakistani territory addresses one half of the machine. The other half sits inside Kashmir, and it is not reachable by an airstrike on a camp in Khyber Pakhtunkhwa.

The intelligence dimension of the causal account is similarly uncomfortable. The reporting that emerged after February 14 indicated that Indian agencies had generated multiple warnings of a possible attack on a security convoy in the days before the bombing. A warning is only useful if it is converted into a protective decision, and the decision to move a very large convoy by road, despite the backlog created by the highway closure and despite the option of airlifting personnel, became a focus of recrimination. The causal chain that produced forty deaths therefore includes a link inside the Indian system itself: a failure to translate available intelligence into a changed convoy posture. Acknowledging that link is not an exercise in blame for its own sake. It matters because it bears on what kind of response is appropriate. A response framed entirely as retaliation against an external enemy implicitly treats the attack as something that could not have been prevented from the Indian side, and that framing forecloses the harder internal conversation about convoy security, intelligence-to-action timelines, and the protection of personnel. Balakot, as a dramatic external strike, absorbed the political energy that the internal conversation also needed.

India’s decision to respond with airpower, rather than with another ground raid or with diplomatic measures alone, is where the structural pressures become decisive. The surgical strikes of 2016 had set the floor. A response to Pulwama that did not exceed a ground raid across the Line of Control would have been read, domestically and by Pakistan, as a step down, an admission that the 2016 model had not deterred and that India had nothing further. The political leadership, four months from a general election in which national security was a central theme, could not afford to be seen taking a smaller step than it had taken after Uri. The logic of escalation in this relationship is partly a logic of audiences. Each response is measured against the last one, and a response that fails to exceed the last one is a defeat regardless of its actual effect.

Airpower offered a specific set of advantages that ground forces did not. A ground raid is slow to mount, difficult to recall once underway, and limited in reach to the immediate vicinity of the Line of Control. Aircraft can strike deep, can be launched and recovered within hours, and can reach targets in Pakistan proper that ground forces could never approach. The Balakot operation allowed India to demonstrate reach into the heartland, a far more dramatic signal than another raid on a launch pad near the line. It also allowed India to frame the strike as targeting terrorist infrastructure rather than the Pakistani state, preserving a thin layer of the deniability-of-intent that both sides use to keep crises below the threshold of declared war. The choice of airpower was, in this sense, a choice for maximum signal at a level of escalation that the planners believed Pakistan could absorb without resorting to a full conventional war.

That belief is the crux, and it is where the analysis of why the escalation happened shades into the analysis of risk. The Indian planners were betting that they could strike inside Pakistan proper and that Pakistan, despite the humiliation, would respond in a calibrated way rather than launching a war. The bet, in the narrow sense, paid off. Pakistan’s response on February 27 was a demonstration strike near, not on, Indian targets, and the crisis was contained by the return of the captured pilot. But the bet was a bet, made under the shadow of two nuclear arsenals, and the fact that it succeeded once does not establish that the same bet would succeed every time. The structural pressure that produced Balakot, the requirement that each response exceed the last, is the same structural pressure that makes the long-term trajectory of this relationship dangerous, and that is the subject the chain has to turn to next.

The Immediate Consequences

The most immediate consequence of the escalation was the safe return of Wing Commander Abhinandan Varthaman on March 1, and that return was both a relief and a problem. It was a relief because a captured pilot is a combustible object in a crisis between nuclear-armed states; his prolonged captivity, or any mistreatment, could have driven the confrontation toward outcomes neither government wanted. His release within roughly sixty hours of his capture removed that combustible object from the board and gave both sides an exit. It was a problem because it scrambled the question of who had prevailed. Imran Khan’s framing of the release as a peace gesture allowed Pakistan to occupy the posture of the responsible, restrained party, the state that had been struck, had demonstrated it could strike back, and had then chosen de-escalation. India had crossed the airspace barrier and recovered its pilot, but it had also lost a MiG-21 and, as later acknowledged, six airmen and a civilian to its own air defenses at Budgam. The episode did not produce a clean victor, and the absence of a clean victor is itself one of its more important consequences, because it left both sides able to tell their domestic audiences a story of success, and stories of success on both sides are what make a precedent comfortable to repeat.

The second immediate consequence was the collapse of the body-count claim under the weight of imagery. In the days after Balakot, the Indian political conversation absorbed figures of hundreds of militants killed at the Jaba camp. Within weeks, satellite analysis from multiple independent sources indicated that the structures on the hilltop were intact. By April, the External Affairs Minister stated that no Pakistani soldiers or civilians had been killed in the strike, a statement that Pakistan’s military spokesman pointedly welcomed as a vindication of its account. The gap between the initial claims and the imagery did not become a major political liability inside India, partly because the strike’s symbolic meaning had already done its work and partly because the general election campaign moved the conversation forward. But the gap matters for the historical record and for the chain. It established a pattern that would recur: in these escalations, the strategic signal travels instantly and the factual assessment travels slowly, and by the time the factual assessment arrives, the signal has already reset the baseline. The next strike would be planned against the precedent of Balakot-the-symbol, not Balakot-the-imagery.

The third immediate consequence was electoral. The Pulwama-Balakot episode unfolded in the direct run-up to India’s 2019 general election, and national security became a dominant theme of the campaign that followed. The governing party’s vote share and seat count rose, and the post-election analysis widely credited the security narrative, with Balakot at its center, as a contributing factor. This is where an honest account has to hold a tension without collapsing it. The security logic of responding forcefully to a mass-casualty attack on security personnel was genuine and would have existed regardless of the electoral calendar. At the same time, the timing meant that the response was made by a government with a powerful incentive to be seen acting decisively, and the response then became campaign material. Both things are true. The electoral context did not manufacture the strike, but it raised the stakes of being seen to under-respond, and it ensured that the strike’s symbolic dimension would be amplified far beyond what its tactical results could support.

The fourth immediate consequence was international, and it was quieter than the others but consequential. The major powers responded to the crisis with calls for restraint and de-escalation rather than with condemnation of the Indian strike. The framing that India had acted against a terrorist target, rather than against the Pakistani state, gained a measure of international acceptance, or at least did not provoke significant international censure. This was not nothing. It signaled that an Indian strike inside Pakistan, if framed as counter-terrorism and kept below the threshold of an attack on Pakistani military or civilian assets, could be conducted without isolating India diplomatically. That signal would compound over time. Each crisis in which India struck and was not punished diplomatically reduced the diplomatic cost of the next strike, and the reduction of diplomatic cost is one of the quieter mechanisms by which the escalation ladder becomes easier to climb.

The fifth consequence was for Jaish-e-Mohammed and for the broader militant ecosystem, and it was ambiguous. In the immediate aftermath, Pakistan announced the detention of dozens of individuals associated with various militant groups, including Jaish, and some of those named had appeared in the dossier India provided after Pulwama. Detentions of this kind have a long history of being temporary and reversible, and the structural relationship between the Pakistani security establishment and the Kashmir-focused militant groups was not transformed by the crisis. What did shift, gradually, was the Indian calculation about how to deal with the network over the longer term. The Balakot model, a single dramatic strike with contested results, had demonstrated reach but had not demonstrably degraded the organization. The lesson that some in the Indian security establishment appear to have drawn, a lesson that becomes visible only further along the chain, was that dramatic strikes generate signal but that the patient, deniable elimination of individuals might generate effect. That divergence between the conventional track and the covert track is a thread that runs forward from 2019 toward the shadow war of the 2020s, and it is one of the most important long-term consequences of the period, even though it was invisible at the time.

The sixth consequence was the emergence of a parallel information conflict that ran alongside the military one, and it set a template that later crises would follow closely. From the morning of February 26 onward, the two governments and their media ecosystems fought to control the meaning of every event. India’s framing emphasized a successful preemptive strike on a terrorist camp with heavy militant casualties. Pakistan’s framing emphasized bombs dropped on empty trees, the downing of an Indian aircraft, and the capture of a pilot. Each side’s domestic media largely amplified its own government’s account, and each side’s social media filled with claims, counterclaims, doctored images, and recycled footage from unrelated events. The independent satellite analysis that eventually clarified the Balakot damage question arrived into an environment where most consumers had already settled on the version their national media had supplied. The episode demonstrated that in a modern India-Pakistan crisis, the contest over perception is not a sideshow to the military events; it is a second front, fought with its own weapons, and the side that loses the kinetic exchange can still win the narrative if it controls the framing. That lesson, absorbed by both establishments after 2019, shaped how the 2025 crisis would be communicated from its first hours.

The seventh consequence was doctrinal and concerned the Indian Air Force itself. Balakot exposed both a capability and a gap. The capability was the ability to plan and execute a deep-penetration strike with a complex supporting package and recover the strike aircraft. The gap was revealed on February 27, when an aging MiG-21 was lost in the air-to-air engagement and questions were raised about the state of the Indian fighter fleet, the slow pace of modernization, and the mix of aircraft available for high-intensity operations against a capable adversary. The post-Balakot conversation about fighter procurement, about the induction of newer platforms, and about the integration of standoff weapons and electronic warfare capability was, in part, a conversation that the events of February 27 forced. By the time of Operation Sindoor in 2025, the Indian Air Force was operating a different and more capable force mix, and some of the impetus for that change traces back to the uncomfortable lessons of the Rajouri engagement.

The Long-Term Chain

The Barrier-Crossing Ladder

The clearest way to see what Pulwama and Balakot did to the India-Pakistan relationship is to lay out the sequence of military barriers India has crossed and to observe that the sequence only moves in one direction. Think of it as a ladder, with each rung a category of action that was once unthinkable and is now established.

The lowest rung is the pre-2016 baseline: India absorbs a major terror attack and responds with diplomacy, dossiers, and the mobilization of international opinion, but does not conduct an offensive military operation across the Line of Control. This was the pattern after the 2001 Parliament attack, after the 2008 Mumbai attacks, and through most of the period that followed. The response stayed on the Indian side of the line.

The second rung is the 2016 surgical strikes. India sends ground forces across the Line of Control to strike launch pads on the Pakistani-administered side, and it publicizes the action. The Line of Control as a one-way barrier, crossable by infiltrators coming in but not by Indian forces going out, ceases to exist. The ground crossing of the line becomes an established option.

The third rung is Balakot in 2019. India sends combat aircraft across the Line of Control and into undisputed Pakistani territory in Khyber Pakhtunkhwa. The barrier of Pakistani airspace, and the deeper barrier of Pakistan’s heartland provinces as a protected zone, ceases to exist. The use of airpower against targets in Pakistan proper becomes an established option.

The fourth rung is Operation Sindoor in May 2025. In response to the Pahalgam attack, India conducts missile and standoff-weapon strikes against multiple sites across Pakistani-administered Kashmir and into Pakistan’s Punjab province, the demographic and political heartland of the country, and the exchange develops into a multi-day conflict involving drones and counter-strikes against military installations. The barrier against missile strikes on the Pakistani heartland, and the barrier against a sustained multi-day conventional exchange, ceases to exist. The fuller account of that operation belongs to the definitive guide to Operation Sindoor, but its place on the ladder is unmistakable.

The structure of the ladder is the analytical point. Every rung, once climbed, became the floor. After 2016, no Indian response to a major attack could credibly stop short of a ground crossing. After 2019, no Indian response could credibly stop short of an air or standoff strike into Pakistani territory. After 2025, the floor has risen again, and the planners of the next crisis will be measured against the precedent of a multi-day conventional exchange. Pulwama and Balakot are the rung that turned the ladder from a two-step affair into a recognizable, repeating structure. The surgical strikes alone might have been read as an exception, a one-time response to an unusually painful attack. Balakot, coming less than three years later and going further, established that the surgical strikes were not an exception but a step in a sequence. Two steps in the same direction make a pattern, and the pattern is the thing that now governs expectations.

It is worth being precise about why crossing Pakistani airspace was a larger event than crossing the Line of Control on the ground, because the distinction is doing real work. The Line of Control is a contested boundary in a contested region; both states claim the territory on the other side of it, and incidents along it, including artillery exchanges and small cross-border raids, have been a recurring feature of the relationship for decades. Crossing it, even with a publicized special-forces raid, was an escalation within a category of action that already had a long history. Striking Balakot was different in kind. Balakot is in Khyber Pakhtunkhwa, undisputed Pakistani territory, governed by no ambiguity about sovereignty. To strike there was to say that the protected status of the Pakistani heartland, a status that had held since 1971, was no longer recognized. That is a categorical change, not an incremental one, and it is why the Balakot rung of the ladder is the steepest single step in the sequence.

Each Escalation Becomes the New Baseline

The mechanism by which a crossed barrier becomes a permanent floor deserves to be examined directly, because it is not automatic and it is not magic. It operates through three channels: domestic expectation, mutual learning, and the diplomatic record.

The domestic expectation channel is the most powerful. Once an Indian government has responded to a major attack with a strike inside Pakistan, the Indian public and the Indian political opposition have a reference point. The next attack will be met with the question: will the response match or exceed the last one? A government that responds with less will be accused of weakness, of squandering deterrence, of letting Pakistan off lightly. This is not a partisan dynamic; it operates against whichever party holds power. The 2016 strikes created the expectation that 2019 had to meet, and meeting it required going further. The 2019 strikes created the expectation that 2025 had to meet, and meeting it required going further still. Each climbed rung becomes the floor not because of any treaty or doctrine but because of the political impossibility of being seen to descend.

The mutual learning channel operates on both sides. Each crisis teaches Pakistan something about what India will do and teaches India something about how Pakistan will respond. After Balakot, Pakistan had learned that India would strike its heartland and that the strike, if framed as counter-terrorism, would not trigger automatic international condemnation. Pakistan also learned that it could respond with a calibrated demonstration strike and a captured-pilot release and contain the crisis. India had learned that it could strike the heartland and survive the Pakistani response without a war. Both sides emerged with a revised model of the other’s tolerance, and both revised models pointed in the same direction: the space for military action below the threshold of full war was larger than either side had previously assumed. When both sides conclude that the usable space is larger, the usable space becomes larger, because expectation in this domain is partly self-fulfilling.

The diplomatic record channel is the quietest. Each strike that the international community meets with calls for restraint rather than condemnation establishes, in the accumulated record, that this category of action is tolerable. Balakot did not isolate India. Operation Sindoor, six years later, drew international concern and calls for de-escalation but again did not produce the kind of diplomatic punishment that would raise the cost of the next strike. The analyst Sameer Lalwani, writing on the dynamics of these crises, has emphasized the way each escalation tends to become the new normal, and the diplomatic channel is part of why. Norms are built by precedent, and a precedent that goes unpunished is a norm in the making.

The combined effect of the three channels is a ratchet. The ladder has rungs but no obvious way down, because descending would require an Indian government willing to accept the domestic cost of appearing weaker than its predecessor, a Pakistani establishment willing to forgo the deterrent value of its own demonstrated responses, and an international environment willing to actively reward restraint rather than merely to call for it. None of those three conditions currently holds. The ratchet is the structure, and Pulwama and Balakot are the episode that made the structure visible.

It is worth naming what a way down the ladder would actually require, because naming it clarifies why none of it is close at hand. A genuine descent would need a sustained reduction in the attacks that trigger Indian responses, which depends on a change in the Pakistani establishment’s relationship with militant networks that no current pressure has produced. It would need a domestic Indian environment in which a government could respond to a smaller provocation with a smaller response without being accused of weakness, which depends on a shift in political culture that no party has an incentive to lead. And it would need an international order capable of converting calls for restraint into concrete rewards for restraint, which the diplomacy of both the 2019 and 2025 crises showed to be absent. The ratchet holds not because anyone designed it to hold but because every actor who could loosen it faces costs for doing so and benefits from leaving it in place. That is the most sobering feature of the structure Pulwama and Balakot made visible: it is stable, and its stability is precisely what makes its upward direction dangerous.

What the Ladder Looks Like From Rawalpindi

An account of the escalation ladder that describes only the Indian climb is incomplete, because the ladder is a structure that two states build together. Each Indian rung is met by a Pakistani response, and the Pakistani responses are themselves rungs that shape what India does next. Seeing the ladder from Rawalpindi is necessary to understand why it is so difficult to dismantle.

From the Pakistani military’s vantage point, each Indian escalation creates the same problem that each Pakistani-attributed attack creates for India: a domestic expectation that the institution will not be seen to absorb a blow without answering. The Pakistani military’s standing within Pakistan rests substantially on its claim to be the guarantor of national security against India. An Indian strike inside Pakistani territory that went unanswered would damage that claim. So the February 27, 2019, operation toward the Rajouri sector was not optional for the Pakistani establishment in any meaningful sense; it was the minimum action required to demonstrate that Indian aircraft could not operate over Pakistan without a response. The capture of an Indian pilot then handed Pakistan something valuable: a way to claim both that it had answered and that it was the restrained party, by releasing the pilot as a gesture. Pakistan climbed its rung and then, having climbed it, used the descent to claim the moral high ground.

This mirroring is what makes the ladder a joint construction. India strikes, Pakistan must answer to satisfy its own domestic audience, and Pakistan’s answer then becomes part of the baseline that India must exceed next time. Neither side can unilaterally stop climbing, because stopping is read at home as losing. The Pakistani establishment’s investment in its militant proxies is the original input that keeps generating the attacks that trigger Indian responses, so Pakistan is not a passive victim of an Indian ladder; it is a co-architect, supplying both the provocations at the bottom and the counter-responses at every rung. An honest account assigns the agency where it belongs. India built the response rungs. Pakistan built the provocation that made response rungs necessary, and Pakistan built its own counter-response rungs in turn. The ladder stands because both states keep adding to it.

The nuclear dimension enters the Pakistani calculation in a specific and dangerous way. For decades, Pakistan’s strategic posture relied on what analysts have called the stability-instability paradox: the idea that nuclear weapons, by deterring full-scale conventional war, created space underneath the nuclear threshold for sub-conventional aggression through proxies. Pakistan could support militant operations against India and rely on the nuclear overhang to deter India from a conventional response large enough to be genuinely costly. The entire post-2016 Indian project, from the surgical strikes through Balakot to Operation Sindoor, is an attempt to call that bluff, to demonstrate that India can act militarily inside Pakistan without triggering nuclear escalation, and thereby to shrink the space the stability-instability paradox was supposed to guarantee. Each Indian rung is a message: the sub-conventional space is not as safe for you as you assumed. Pakistan’s responses are the counter-message: we can answer, and we retain escalation options of our own. The exchange of messages is the ladder, and the messages are getting louder.

The Calibration Problem

The maturation reading rests heavily on the claim that India’s newer tools, airpower and standoff weapons, are calibratable in a way that a mobilized ground army is not. That claim is true, and it is important, but it is also incomplete, and the incompleteness is where the danger concentrates.

Standoff weapons genuinely do give political leaders more control than Operation Parakram gave them in 2001-2002. A missile salvo can be sized, a wave of strikes can be followed by a pause, and the decision to escalate or halt can be taken hour by hour rather than being locked in by the inertia of a hundred thousand soldiers in the field. Operation Sindoor demonstrated exactly this property: successive waves, calibrated to a political objective, with the option to stop. The analyst community has noted that this is a real and significant change in the texture of India-Pakistan crises.

But calibration depends on two conditions that cannot be assumed. The first is accurate, shared understanding of where each side’s red lines lie. Calibration is the art of staying below a threshold, and that art requires knowing where the threshold is. In the India-Pakistan case, the thresholds are not published, are deliberately ambiguous, and may not even be fixed; they can move under domestic pressure in the middle of a crisis. A strike calibrated to stay below an adversary’s red line is only as good as the calibrating side’s estimate of where that line sits, and a wrong estimate produces an escalation that neither side intended. The second condition is that the instruments perform as expected and that the fog of a live crisis does not produce accidents. The Budgam friendly-fire incident in 2019 is the standing reminder that it does not always hold. Six airmen and a civilian died because an air defense system, operating in a chaotic environment, misidentified a friendly helicopter. An accident of that kind, occurring at a more sensitive moment or involving a more provocative target, could itself become an escalation trigger that no political leader chose.

The calibration problem is why the maturation and spiral readings are not as far apart as they first appear. The maturation reading is correct that India has built more controllable tools. The spiral reading is correct that more controllable tools, deployed up a rising ladder against an adversary whose red lines are ambiguous and movable, do not guarantee control. A tool can be calibratable in principle and still be used in a situation where calibration fails. The honest synthesis is that India has reduced one category of risk, the all-or-nothing trap of ground mobilization, and has done so by entering a different category of risk, the repeated testing of ambiguous nuclear thresholds with flexible weapons up an escalation ladder that keeps getting taller. Whether that trade is favorable depends on judgments about probability that no analyst can make with confidence, and the absence of confidence is itself the most important thing to be honest about.

Maturation or Spiral

This brings the analysis to the genuine disagreement at the center of the G8 brief, the disagreement that an honest treatment cannot resolve by assertion. Is the ever-expanding Indian repertoire a sign of strategic maturation, of a state developing a graduated and credible set of responses to terrorism, or is it a dangerous escalation spiral that will eventually reach the nuclear threshold? Two serious readings exist, and the responsible course is to give each its strongest form before adjudicating.

The maturation reading runs as follows. For decades, India faced terrorism emanating from Pakistani soil and had effectively two options: absorb the attack and respond with diplomacy, or threaten a full conventional war that the nuclear overhang made close to unusable. The 2001 Parliament attack produced exactly this trap, a year-long mobilization of ground forces that gave New Delhi an all-or-nothing choice and that it ultimately could not convert into action. The development since 2016, on this reading, is the construction of a middle band. The surgical strikes, Balakot, and the standoff-weapon strikes of Operation Sindoor are graduated options that allow India to impose a cost and demonstrate resolve without committing to a war that cannot be controlled. Standoff weapons and aircraft, unlike a mobilized ground army, can be launched and recalled, can be calibrated wave by wave, and give political leaders the flexibility to escalate or de-escalate as a crisis develops. On this reading, India has matured from a state with no usable response into a state with a credible graduated ladder, and a credible graduated ladder is a contribution to deterrence stability, not a threat to it.

The spiral reading runs as follows. Every one of those graduated options is also a barrier crossed, and every barrier crossed lowers the threshold for the next crossing. The middle band that the maturation reading celebrates is not a stable plateau; it is a slope. Each crisis has gone further than the last, from a ground raid, to an airstrike on the heartland, to missile strikes and a multi-day conventional exchange. The analyst Vipin Narang, writing on escalation dynamics in nuclear contexts, has drawn attention to the danger inherent in barrier-crossing between nuclear-armed states: each crossed barrier removes a firebreak, a natural stopping point, and a relationship with fewer firebreaks is a relationship in which a future crisis has fewer places to halt before it reaches the level where nuclear use becomes conceivable. The spiral reading does not claim that nuclear war is imminent. It claims that the trend line, the steady removal of barriers, is moving in a direction that reduces the number of safe stopping points, and that a relationship with fewer safe stopping points is more dangerous even if each individual crisis is contained.

Adjudicating between the two readings requires resisting the temptation to choose the comfortable one. The maturation reading is comfortable because it tells a story of competent statecraft. The spiral reading is uncomfortable because it offers no reassuring endpoint. The most defensible assessment is that both readings describe real features of the same process, and that which one dominates depends on a variable that is genuinely uncertain: whether the calibration tools that make the middle band usable are reliable enough to keep each crisis contained as the floor keeps rising. The 2019 episode contained itself, but it did so partly through luck, through the friendly-fire deaths at Budgam, through the captured pilot whose release happened to give both sides an exit. The 2025 episode contained itself, but the four-day exchange was larger and more dangerous than 2019, and it was halted in significant part through external diplomatic intervention rather than through the internal logic of either side’s restraint. The trend is that each crisis is contained, and the trend is also that each crisis is larger and that the margin of containment is being tested harder each time. A process can be both maturation and spiral at once: a state can be developing genuinely more sophisticated graduated options while those very options are eroding the firebreaks that would stop a graduated process from running past its intended limit. That is the honest answer, and it is uncomfortable precisely because it is honest.

What Pulwama and Balakot contribute to this question is the proof of concept for the slope. Before 2019, an optimist could argue that the 2016 surgical strikes were a one-time response and that India would not necessarily go further. Balakot ended that argument. It established that the floor rises, that each crisis builds on the last, and that the relationship has a directional momentum. The nuclear dimension of these escalations is the reason the directional momentum matters more here than it would between two conventionally armed states. A spiral between two conventional powers terminates in a conventional war, which is catastrophic but bounded. A spiral between two nuclear powers has a terminal rung that is not bounded, and the function of firebreaks is to ensure the spiral stops well before that rung. Every barrier Balakot helped normalize is a firebreak that a future crisis will not have.

The Two Tracks Diverge

There is a further long-term consequence of the 2019 episode that becomes legible only when the chain is viewed as a whole, and it concerns the relationship between India’s conventional military track and its covert track. Balakot was a conventional, overt, attributed operation. India announced it, claimed it, and built a political narrative around it. Its tactical results, as the imagery showed, were modest. The lesson available to draw from that mismatch, between the size of the signal and the size of the effect, was that the overt conventional strike is excellent at signaling and poor at degrading.

In the years after 2019, a second track became increasingly visible: a pattern of targeted killings of individuals associated with militant organizations, occurring on Pakistani soil, attributed by Pakistan to India and denied by New Delhi. That covert track has the opposite profile from Balakot. It generates almost no signal, because India does not claim it, and it is designed to generate effect, the removal of specific operatives whose skills and networks are difficult to replace. The divergence of the two tracks, the loud conventional track for signaling and the quiet covert track for effect, is one of the defining strategic developments of the period that follows 2019, and the contrast was sharpened by Balakot’s demonstration of what a loud strike can and cannot achieve. The episode covered here is therefore not only a rung on the conventional ladder. It is also part of the reason the covert ladder began to be climbed in parallel, and the convergence of those two tracks is a story the chain tells in its later links.

There is a deeper logic to the divergence that is worth making explicit. An overt strike like Balakot is, by design, a communication. Its primary product is a message addressed to multiple audiences at once: a message to the Pakistani establishment that India will reach into its heartland, a message to the Indian public that the government has answered, and a message to the wider world about India’s resolve. A communication of that kind succeeds or fails on whether the message is received, not on whether a particular building was destroyed, which is why Balakot could be a strategic success and a tactical near-miss at the same time. A covert elimination is the inverse. It is not addressed to an audience at all; it is addressed to a problem. Its product is not a message but a subtraction, the removal of a person whose continued work the Indian system has assessed as costly. Because it carries no public claim, it generates no escalation pressure on Pakistan to respond in kind, and because it is precise, its effect is concrete rather than symbolic. The Indian security establishment, having watched Balakot generate maximum signal and minimal subtraction, had in front of it a natural complement: a method that generated minimal signal and maximal subtraction. The two methods are not competitors. They are a division of labor, and the division of labor is one of the most important things the post-2019 period reveals. The conventional ladder and the covert ladder are climbed in parallel because each does what the other cannot, and a state that possesses both has a wider menu than a state that possesses only one.

What this means for the chain is that Balakot should not be read solely as a conventional-military event. It is also a hinge in the development of India’s covert posture, because it clarified, by negative example, what the covert posture would be for. The loud strike taught the lesson; the quiet campaign applied it. That is why the period running forward from 2019 is best understood not as a conventional story with a covert subplot, but as the parallel development of two tracks that would, in the crisis of 2025, finally be used in the same window of time against the same adversary.

The Next Link

The Pulwama-Balakot escalation closed with the return of a pilot and the gradual fading of a crisis from the front pages, but the chain it belonged to did not pause. Within months, the conditions that the episode had set, the rising floor, the demonstrated reach into Pakistani territory, the revised mutual models of tolerance, became the backdrop for the next decisive move, and that move was not a strike at all. It was a constitutional act.

On August 5, 2019, a little over five months after Abhinandan Varthaman walked back across the Wagah border, the Indian government revoked the special constitutional status that Jammu and Kashmir had held under Article 370. The revocation was not a military operation, but it had military and strategic consequences that flowed directly from the environment Balakot had helped create. It hardened India’s position that Kashmir was an entirely internal matter, it reshaped the political and security landscape of the region, and it altered the terms on which Pakistan could press its claims. The revocation of Article 370 is the next link in this chain, and it is the link that converts a series of crisis responses into a settled change in the underlying dispute.

From there the chain runs toward its most consequential modern node. The hardened post-2019 environment, the rising escalation floor, and the unresolved presence of militant networks on Pakistani soil set the stage for the attack at Pahalgam in April 2025, in which twenty-six people, most of them tourists, were killed in Kashmir. That attack functioned as Pulwama had functioned six years earlier: as a trigger that the established escalation ladder obliged India to answer, and to answer at a rung above the last one. The response, Operation Sindoor, took the repertoire from an airstrike on a single camp to missile strikes on multiple sites and a multi-day conventional exchange. The line from the convoy at Lethpora to the missile salvoes of 2025 runs straight through Balakot, and the Pahalgam attack as the trigger event is the link where the ladder Balakot helped build is climbed to its highest rung yet. Every barrier the 2019 episode normalized was a barrier that the planners of 2025 no longer had to think about crossing, because it had already been crossed. That is what it means to be a link in this chain: the episode is finished, but the floor it raised is permanent, and the next crisis begins from the height where this one ended.

Frequently Asked Questions

Q: How did the Pulwama attack lead to the Balakot airstrike?

The Pulwama attack on February 14, 2019, killed forty Central Reserve Police Force personnel when a vehicle-borne suicide bomber struck their convoy near Lethpora on the Jammu-Srinagar National Highway, and Jaish-e-Mohammed claimed responsibility. The scale of the casualties, the identity of the organization, and the proximity of a national election created intense pressure on the Indian government to respond with a military operation that would exceed the 2016 surgical strikes. Twelve days later, on February 26, the Indian Air Force conducted a strike near Balakot in Khyber Pakhtunkhwa against a facility India described as a Jaish-e-Mohammed training camp. The airstrike was the chosen response because airpower could reach deep into Pakistani territory in a way ground forces could not, allowing India to demonstrate reach into the Pakistani heartland while framing the strike as a counter-terrorism action rather than an attack on the Pakistani state.

Q: What barrier did Balakot break that the surgical strikes did not?

The 2016 surgical strikes crossed the Line of Control, the contested de facto boundary in the disputed region of Kashmir, where cross-border incidents had a long history. Balakot crossed something more fundamental: the boundary of undisputed Pakistani territory. Balakot lies in Khyber Pakhtunkhwa province, in Pakistan proper, well beyond any disputed area. When Indian aircraft struck there, they ended the tacit understanding, holding since the 1971 war, that the Pakistani heartland was a protected zone off-limits to Indian military action. The surgical strikes escalated within a familiar category of action along a contested line. Balakot opened an entirely new category by treating Pakistan’s sovereign heartland as a legitimate target, which is why it stands as the steepest single step in the escalation sequence.

Q: Why was crossing Pakistani airspace more significant than crossing the Line of Control?

Crossing the Line of Control, even with a publicized raid, was an escalation within a category that already existed, because the line is a contested boundary and incidents along it have recurred for decades. Crossing into Pakistani airspace over Khyber Pakhtunkhwa was different in kind. It signaled that the protected status of Pakistan’s undisputed heartland no longer held, a status that had survived since 1971. A categorical change reshapes expectations far more than an incremental one. After Balakot, the question in any future crisis was no longer whether India would act inside Pakistani-controlled space but how deep and by what means, and that shift in the baseline question is what makes the airspace crossing the more consequential event.

Q: What was the twelve-day timeline from the Pulwama attack to the Balakot airstrike?

The Pulwama attack occurred on February 14, 2019. The Balakot airstrike was conducted in the early hours of February 26, 2019, twelve days later. During the intervening period, India announced diplomatic and economic measures, including the withdrawal of most-favored-nation trade status and a sharp increase in customs duties on Pakistani goods, and handed Islamabad a dossier on the attack. Behind the visible measures, the Indian Air Force planned the operation later codenamed Operation Bandar. The twelve-day window reflected the time needed to plan a deep strike, position force-multiplier aircraft, and select a target, balanced against the political pressure to respond before the momentum of public anger dissipated.

Q: What was the Abhinandan episode?

On February 27, 2019, the day after the Balakot airstrike, the Pakistan Air Force conducted a cross-border operation toward Indian targets in the Rajouri sector, and an aerial engagement developed over the Line of Control. An Indian MiG-21 Bison flown by Wing Commander Abhinandan Varthaman was shot down, and the pilot ejected over Pakistani-administered territory, where he was captured. India claimed Abhinandan had downed a Pakistani F-16 before being hit, a claim that independent analysts found unsupported. Pakistan’s Prime Minister announced the pilot’s release on February 28, and Abhinandan crossed back into India at the Wagah border on March 1. His capture and return became the emotional center of the crisis and gave both governments a way to step back from further escalation.

Q: Did the Balakot airstrike actually destroy a Jaish-e-Mohammed camp?

The tactical results of the Balakot airstrike are genuinely contested, and the most defensible assessment is that they were modest at best. India initially described the strike as having killed a large number of militants, with figures of three hundred or more circulating in Indian coverage. Pakistan said the bombs hit an uninhabited wooded hilltop. Satellite imagery analyzed by independent groups, including the Atlantic Council’s Digital Forensic Research Lab and the Australian Strategic Policy Institute, indicated that the principal structures on the Jaba hilltop site remained standing. A managed visit by international journalists in April found the largest building intact. The strategic significance of Balakot, the crossing of the airspace barrier, did not depend on the body count, but the high casualty claims were not supported by the available evidence.

Q: Why did the Budgam helicopter crash happen during the crisis?

During the high-tension aerial activity on February 27, 2019, an Indian Mi-17 helicopter was brought down near Budgam in Kashmir, killing six Indian airmen aboard and one civilian on the ground. The cause was later acknowledged to have been friendly fire: Indian air defenses, operating amid multiple aircraft and a chaotic threat environment, downed one of their own helicopters. The acknowledgment came months after the incident. The Budgam crash is a reminder that once aircraft are airborne and air defenses are active in a crisis, the resulting confusion produces casualties that fit neither side’s preferred narrative, and that such casualties are often acknowledged slowly.

Q: Is India’s escalation ladder sustainable?

The escalation ladder is sustainable in the narrow sense that each crisis so far has been contained below the threshold of full war, but its sustainability over the long term is the central uncertainty. The ladder moves in only one direction: each crisis has gone further than the last, from a ground raid in 2016, to an airstrike on the Pakistani heartland in 2019, to missile strikes and a multi-day conventional exchange in 2025. Each climbed rung becomes the floor for the next response because of domestic political expectation. The danger is that a ladder with no descent and steadily rising rungs reduces the number of natural stopping points in a future crisis, and between two nuclear-armed states, the erosion of stopping points is the principal long-term risk.

Q: Does each escalation become the new baseline?

Yes, and the mechanism operates through three channels. Domestic expectation makes it politically impossible for an Indian government to respond to a major attack with less than its predecessor did, so each response must match or exceed the last. Mutual learning means each crisis revises both sides’ models of the other’s tolerance, and the revised models consistently conclude that the space for military action below full war is larger than previously assumed. The diplomatic record means that each strike met with calls for restraint rather than condemnation establishes that the category of action is tolerable. Together these channels form a ratchet: the floor rises with each crisis and does not fall.

Q: Could the escalation ladder reach the nuclear threshold?

No analyst can responsibly claim that nuclear use is imminent, but the structural concern is real. The escalation ladder removes firebreaks, the natural stopping points where a crisis can halt. Each crossed barrier, from the Line of Control to Pakistani airspace to missile strikes on the heartland, is a firebreak that a future crisis will not have. A relationship with fewer firebreaks is one in which a future crisis has fewer places to stop before reaching levels where nuclear use becomes conceivable. The 2019 and 2025 episodes were both contained, but each was larger than the last and the margin of containment is being tested harder each time. The risk is not a single decision to use nuclear weapons but a process that runs past its intended limits because the stopping points have been removed.

Q: Was the Pulwama attack carried out by a local Kashmiri or an infiltrator?

The suicide bomber, Adil Ahmad Dar, was a local Kashmiri youth from the Gundibagh area of Pulwama district, not an infiltrator who had crossed the Line of Control. He had reportedly left home in early 2018 to join the militancy. His local origin reflects an operational evolution by Jaish-e-Mohammed toward recruiting Kashmiri youth rather than relying solely on cross-border infiltration, both because infiltration had become harder and because a local attacker supported a propaganda narrative of indigenous resistance. The local identity of the bomber complicated the politics of attribution, even though the explosives, training, and organizational direction reached back across the border.

Q: How does Balakot compare to Operation Sindoor in 2025?

Balakot in 2019 was a single airstrike against one facility, conducted by Mirage 2000 jets, with contested and likely modest tactical results, and the crisis was contained within days. Operation Sindoor in May 2025 was a substantially larger operation: missile and standoff-weapon strikes against multiple sites across Pakistani-administered Kashmir and into Pakistan’s Punjab heartland, followed by a multi-day exchange involving drones and counter-strikes on military installations. Sindoor sits one rung above Balakot on the escalation ladder, using more force, more weapon types, and a wider target set. Balakot established that India would strike the Pakistani heartland from the air; Sindoor established that India would do so with missiles and would sustain a multi-day conventional conflict.

Q: What was Operation Bandar?

Operation Bandar was the Indian codename for the Balakot airstrike conducted on February 26, 2019. The operation reportedly involved twelve Mirage 2000 fighter jets carrying precision-guided munitions, supported by Su-30MKI fighters flying combat air patrol, a Netra airborne early warning aircraft, a Heron surveillance drone, and Il-78 aerial refueling tankers. The codename, drawn from the Hindi word for monkey, was assigned for operational secrecy. The operation’s purpose was to strike a Jaish-e-Mohammed facility near Balakot and recover all aircraft safely, demonstrating that the Indian Air Force could reach deep into Pakistani territory and return.

Q: Did the Balakot airstrike isolate India diplomatically?

No. The major powers responded to the 2019 crisis with calls for restraint and de-escalation rather than condemnation of the Indian strike. India’s framing of the operation as a counter-terrorism action against a militant target, rather than an attack on the Pakistani state, gained a measure of international acceptance. This was a consequential outcome: it signaled that an Indian strike inside Pakistan, if framed as counter-terrorism and kept below the threshold of an attack on Pakistani military or civilian assets, could be conducted without significant diplomatic cost. Each such episode reduces the diplomatic cost of the next strike, which is one of the quieter mechanisms by which the escalation ladder becomes easier to climb.

Q: Why does the Pulwama-Balakot episode matter in the larger India-Pakistan story?

The episode matters because it converted a two-step sequence into a recognizable, repeating pattern. The 2016 surgical strikes alone could have been read as a one-time exception. Balakot, coming less than three years later and going further by striking the Pakistani heartland from the air, established that the surgical strikes were a step in a sequence rather than an exception. Two steps in the same direction create a pattern, and the pattern, the rising escalation floor, now governs expectations for every India-Pakistan crisis. The episode is also the proof of concept for the barrier-crossing dynamic in which each crossed barrier becomes the permanent floor for the next response.

Q: What happened to the F-16 that India claimed it shot down?

India claimed that during the aerial engagement on February 27, 2019, Wing Commander Abhinandan Varthaman shot down a Pakistani F-16 before his own MiG-21 was hit. Pakistan denied losing any aircraft. The claim became one of the most disputed elements of the crisis. Independent defense analysts found India’s evidence to be circumstantial, and the absence of a confirming announcement from the United States, the supplier of Pakistan’s F-16 fleet, weighed against the claim. The honest assessment is that the F-16 shootdown was never established to a standard a neutral analyst would accept, and the dispute illustrates the wider pattern in these crises of competing claims that the available evidence cannot fully resolve.

Q: How did the 2019 election affect India’s response to Pulwama?

The Pulwama-Balakot episode unfolded directly before India’s 2019 general election, and national security became a dominant theme of the campaign that followed, with the Balakot airstrike at its center. The security logic of responding forcefully to a mass-casualty attack would have existed regardless of the electoral calendar, so the election did not manufacture the strike. But the timing raised the political stakes of being seen to under-respond and ensured that the strike’s symbolic dimension would be amplified well beyond what its contested tactical results could support. The post-election analysis widely credited the security narrative as a contributing factor in the governing party’s strong performance. Both the genuine security logic and the electoral incentive were real, and an honest account holds them together rather than collapsing one into the other.

Q: Was the Pulwama attack directed by Pakistan’s intelligence services?

The question of direct state direction is the genuinely contested issue, and it should not be answered with false certainty. The bomber was a local Kashmiri, and Jaish-e-Mohammed claimed the attack. The most defensible assessment is that Pulwama sat in the gray zone that has defined this conflict for decades: an organization sheltered and tolerated on Pakistani soil, drawing on cross-border resources for the explosives and the expertise that a local cell could not easily produce, executing through local hands in a manner that allowed Islamabad to deny operational direction while India held it responsible for providing the shelter. The sophistication of the device and the quantity of military-grade explosive point to resources beyond an isolated cell, but the available open-source evidence does not establish a direct intelligence-officer-run operation. The honest position is that the shelter and tolerance are well documented while specific operational direction is not, and the Indian case rests primarily on the former.

Q: Why did India choose airpower instead of another ground raid?

By 2019, a ground raid across the Line of Control was no longer an escalation; it was the established 2016 baseline, and matching the baseline would have been read as a step down. Airpower offered three advantages a ground raid could not. It could reach deep into Pakistan proper, allowing India to strike the heartland rather than launch pads near the line. It was fast to launch and recover, executable within hours rather than requiring the slow buildup of a ground operation. And it allowed the strike to be framed as targeting terrorist infrastructure rather than the Pakistani state, preserving a thin layer of deniability of intent that helped keep the crisis below the threshold of declared war. The choice of airpower was a choice for maximum signal at a level of escalation the planners believed Pakistan could absorb without launching a full conventional war.

Q: What is the stability-instability paradox and how does Balakot relate to it?

The stability-instability paradox is the idea that nuclear weapons, by deterring full-scale conventional war between two nuclear-armed states, create space below the nuclear threshold for lower-level aggression. Pakistan’s strategic posture relied on a version of this logic: it could support militant operations against India and count on the nuclear overhang to deter India from a conventional response large enough to be genuinely costly. The post-2016 Indian project, including Balakot, is an effort to call that bluff by demonstrating that India can conduct military operations inside Pakistan without triggering nuclear escalation, thereby shrinking the space the paradox was supposed to guarantee. Balakot was a message that the sub-conventional space is not as safe for Pakistan as its posture assumed. The risk is that repeatedly testing the boundary of that space, against ambiguous and movable nuclear red lines, is inherently dangerous even when each individual test is survived.

Q: Did the Pulwama-Balakot crisis change the Indian Air Force?

Yes, in the sense that it exposed both a capability and a gap. The capability was the ability to plan and execute a deep-penetration strike with a complex supporting package of fighters, early-warning aircraft, tankers, and surveillance drones, and to recover the strike aircraft. The gap was revealed on February 27, 2019, when an aging MiG-21 was lost in the air-to-air engagement, prompting questions about the state of the fighter fleet and the pace of modernization. The post-Balakot conversation about fighter procurement, the induction of newer platforms, and the integration of standoff weapons and electronic warfare capability was driven in part by the uncomfortable lessons of the Rajouri engagement. By the time of Operation Sindoor in 2025, the Indian Air Force operated a different and more capable force mix.

Q: Is the Pulwama-Balakot escalation finished, or is it still continuing?

The episode itself concluded in March 2019 with the return of the captured pilot and the fading of the crisis, but the chain it belongs to is not finished, and the floor it raised is permanent. Balakot established that India would strike the Pakistani heartland from the air, and that establishment did not expire when the crisis ended. It became the baseline that the 2025 Pahalgam attack and Operation Sindoor were measured against, and Sindoor in turn raised the floor again. The escalation ladder Balakot helped build continues to stand, and each future crisis will begin from the height where the last one ended. In that sense the episode is over but its consequences are ongoing, which is precisely what it means to be a link in a chain rather than an isolated event.

Q: What does the Pulwama-Balakot episode reveal about the larger shadow war?

The episode reveals the limits of the loud, attributed, conventional strike and helps explain why a quieter track developed alongside it. Balakot generated an enormous signal, the crossing of the airspace barrier, but its tactical effect on Jaish-e-Mohammed, as the satellite imagery indicated, was modest. The mismatch between the size of the signal and the size of the effect pointed toward a lesson: overt conventional strikes are excellent at demonstrating resolve and poor at degrading a network. In the years after 2019, a covert track of targeted killings on Pakistani soil became increasingly visible, with the opposite profile, almost no signal and a design aimed at concrete effect. The divergence of the loud conventional track and the quiet covert track is one of the defining strategic developments of the period, and Balakot’s demonstration of what a loud strike can and cannot achieve is part of the reason the covert track began to be developed in parallel.