At 3:15 in the afternoon on February 14, 2019, a Mahindra Scorpio carrying somewhere between 200 and 350 kilograms of explosive material slammed into the side of a Central Reserve Police Force bus on the Srinagar-Jammu National Highway near Lethpora village, about twenty kilometres south of Srinagar in Pulwama district. Forty CRPF personnel died. Five more were grievously wounded. The convoy of seventy-eight vehicles, carrying 2,547 personnel back to Kashmir after leave on the mainland, had been deliberately targeted at a stretch where the four-lane highway narrows and where civilian traffic mixes with military movement. The Mahindra had pulled out of a side road, accelerated alongside the bus, and detonated. The blast was heard fifteen kilometres away.
What happened in the next twelve days reshaped India’s military doctrine permanently. New Delhi did not wait. New Delhi did not consult. New Delhi did not engage Islamabad through the diplomatic channels that had absorbed every previous attack since the 1999 Kandahar hijacking. On February 26, in the pre-dawn hours, twelve Mirage 2000 jets of the Indian Air Force crossed the international boundary, penetrated thirty kilometres into Pakistani territory proper, and dropped SPICE 2000 precision-guided bombs on what India identified as a Jaish-e-Mohammed seminary at Balakot in Khyber Pakhtunkhwa. For forty-eight years, since the 1971 war that produced Bangladesh, India had not struck inside undisputed Pakistani soil. The bombing of a CRPF convoy on a Kashmir highway broke that line. The decision to break it was made in twelve days.
This article reconstructs the convoy bombing forensically, walks through the twelve-day decision chain that produced Balakot, names the figures whose actions and choices shaped both the attack and the response, and adjudicates the analytical debates that have surrounded the incident since: was the operation purely a Jaish-e-Mohammed operation, or was it directed by Pakistan’s Inter-Services Intelligence; did the explosive payload come from local Kashmiri stockpiles or from across the Line of Control; was the Indian response strategically optimal or shaped by the looming general elections; and did the Balakot airstrike actually destroy what India claimed it destroyed. The Pulwama attack of 2019 produced more consequences than any single incident in India-Pakistan relations since 1999. Understanding what happened, in granular detail, is the prerequisite for understanding everything that came after, including the 2025 Pahalgam massacre and Operation Sindoor.
Background and Triggers
Kashmir in early 2019 was a security environment that had been deteriorating for nearly a decade. Burhan Wani, the young Hizbul Mujahideen commander whose 2016 elimination triggered months of unrest in the Valley, had become a martyrdom figure for a generation of Kashmiri youth radicalised online and recruited locally. Indian security agencies tracked a steady rise in homegrown militancy: by 2018, recruitment into Jaish-e-Mohammed and Hizbul Mujahideen of Kashmiri-origin fighters had outpaced infiltration from across the Line of Control for the first time in decades. The local turn meant that Pakistani-trained handlers no longer had to smuggle operatives into Kashmir; instead, they could radicalise and equip Kashmiris already living there.
Convoy security on the Srinagar-Jammu National Highway followed protocols established after a string of ambush attempts in the 1990s. CRPF and J&K Police escorts moved in convoys of fifty to one hundred vehicles, with security halts at predesignated points, advance scouts, road sanitisation, and a rolling civilian-traffic clearance. The highway itself winds through forested foothills, mixed-population villages, and apple orchards. Civilian traffic remained on the road during convoy movement, a longstanding compromise between security needs and the practical impossibility of shutting down the only year-round road link between Kashmir and the rest of India. Lethpora, where the bombing occurred, sat on a stretch where the four-lane highway narrows briefly to two lanes, where roadside foliage limited sight lines, and where a service road allowed civilian vehicles to merge with the main carriageway at unmanned points.
Three weeks before February 14, the convoy that became the target was already in planning. Heavy snowfall had closed the highway for several days, producing a backlog of personnel who needed to return from leave. By the second week of February, that backlog had grown to over 2,500 personnel, requiring an unusually large convoy of seventy-eight vehicles, far above the standard size. Police and intelligence officials would later acknowledge that the backlog itself, the size of the resulting convoy, and the specific date of movement were all foreseeable by anyone monitoring CRPF rotation patterns. Kashmir-based handlers monitored such patterns continuously.
The convoy logistics in early February 2019 illustrate the operational tension that had been built into Kashmir security routines over decades. A force of approximately 60,000 CRPF personnel rotated periodically between Kashmir deployment and leave on the Indian mainland, with rotations clustered to align with seasonal accessibility, training cycles, and logistical capacity at the Jammu transit camp. The use of road movement rather than air movement for the bulk of these rotations reflected practical economics: air movement of personnel at this scale would have required dedicated aviation capacity that did not exist. Road movement on the Srinagar-Jammu National Highway, the only year-round route, was therefore the operational baseline. The vulnerability of road convoys to ambush had been managed, since the early 1990s, through the convoy-protocol system that mixed military-grade security measures (escort vehicles, advance scouts, road sanitisation) with practical compromises (continued civilian traffic, predictable routing, daylight movement). Each compromise had a defensible operational reason, and the cumulative compromise had functioned without major incident for over two decades. Pulwama was, in that sense, the failure point of an operational system whose individual components had each been judged acceptable.
Jaish-e-Mohammed had been in operational preparation throughout late 2018 and early 2019. Indian intelligence later assembled, through interrogation of captured handlers and analysis of communications intercepts, a picture of a multi-month effort that included reconnaissance of multiple convoy routes, identification of a Kashmiri suicide volunteer, sourcing of explosive material in quantities far exceeding what local stockpiles typically held, and selection of a vehicle that could carry the payload without raising suspicion. The handler chain ran from Pakistan-based Jaish operatives through cross-border couriers into a small Kashmir-based cell. Adil Ahmad Dar, a twenty-year-old from Kakapora village in Pulwama district, had been radicalised, recruited, indoctrinated, and trained over a period of about a year. His family later said he had left home in March 2018 after a confrontation with a soldier at a security checkpoint. By February 2019 he was living in safe houses around Pulwama, waiting for the operation that would kill him and forty CRPF personnel.
The political context that shaped the Indian response was unusual. General elections to the Lok Sabha were scheduled for April and May 2019. The Bharatiya Janata Party government of Prime Minister Narendra Modi was campaigning on a national-security platform that emphasised the 2016 surgical strikes after the Uri attack as proof of doctrinal change. A major terror attack in this environment was not absorbable in the way previous attacks had been: domestic political pressure for a visible, kinetic response was already at maximum before the bombing occurred, simply because the precedent of Uri had reset public expectations of what an Indian government should do after a major attack on security personnel. That political fact does not by itself determine what happened next; it does mean that the decision space available to New Delhi after Pulwama was narrower than it had been after Pathankot or after the 2008 Mumbai attacks.
Pakistan in February 2019 was governed by Prime Minister Imran Khan, in office since August 2018, with Army Chief Qamar Javed Bajwa exercising the actual control over national-security policy that has been the norm since the country’s founding. Bajwa had made overtures toward de-escalation with India during 2018, and Khan had spoken publicly about wanting dialogue. None of this had translated into operational change on the ground: Jaish-e-Mohammed continued to function from its Bahawalpur headquarters, training camps continued to operate in Khyber Pakhtunkhwa, and the Inter-Services Intelligence Directorate continued its longstanding relationship with the organisation Masood Azhar had founded in early 2000 after his release from Indian custody during the IC-814 hijacking. Whether the Pakistani civilian government had any meaningful awareness of what was being prepared in Kashmir is a question to which the available evidence gives an unambiguous answer: it did not, because civilian governments in Pakistan have never had operational visibility into what the security establishment does on Kashmir.
The international environment in early 2019 was unusually permissive for Indian military action. The United States had been progressively tightening pressure on Pakistan over its tolerance of militant safe havens, with President Trump publicly accusing Pakistan in 2018 of giving the United States nothing but lies and deceit and suspending most security assistance. The Financial Action Task Force had placed Pakistan on its grey list in June 2018, with explicit benchmarks tied to action against UN-designated terror groups. France, the United Kingdom, and several other European partners had aligned their public messaging with the broader pressure campaign. China, Pakistan’s most important diplomatic patron, was preoccupied with trade tensions with Washington and the early phase of what would become the Belt and Road expansion in Central Asia. Saudi Arabia, traditionally a Pakistani ally, was navigating the post-Khashoggi diplomatic environment and looking to broaden Indian engagement. Russia, on its post-Crimea trajectory, was deepening defence cooperation with India that had begun under previous administrations. The cumulative effect was an environment in which a sharp Indian response to a major Pakistan-linked terror attack would face less international friction than it would have faced a decade earlier.
The intelligence environment inside Kashmir at the start of 2019 was deteriorating in ways that subsequent reviews would identify as contributing to the Pulwama failure. Local intelligence networks that had been built over decades, relying on community sources, informant relationships, and covert agent placement within militant groups, had been disrupted by the post-2016 unrest. The shift toward locally radicalised Kashmiris reduced the value of cross-border surveillance that had previously detected infiltration attempts. The shift toward suicide attacks, rare in Kashmir before 2019, did not have an established intelligence template comparable to the fidayeen-attack template that had been built over the previous two decades. The specific failure to detect a multi-month preparation involving a vehicle, a payload, a bomber, and multiple safe houses was a failure of the kind that intelligence services everywhere experience periodically when adversary methods shift faster than detection methods, but it was a failure all the same. The post-Pulwama intelligence reforms within Indian agencies have addressed parts of this gap; whether they have addressed it completely remains to be tested by the next major attack.
The Convoy and the Highway
The convoy that left the Jammu transit camp at 3:30 a.m. on February 14, 2019, comprised seventy-eight vehicles. Most were standard CRPF buses, each holding between thirty-five and forty-five personnel. A smaller number of trucks carried equipment and supplies. Escort vehicles, lighter and faster, ran ahead of and behind the main column. The total personnel count was 2,547, drawn from multiple CRPF battalions returning to deployment in Kashmir after leave. Many of those personnel had already spent more than thirty hours travelling, having boarded at Delhi and Lucknow and other cities across northern India before reaching the Jammu transit point.
The convoy moved through the Banihal tunnel and onto the Kashmir Valley road by mid-morning. By 2:00 p.m., it was passing through Anantnag district. The standard procedure called for civilian traffic to be cleared from the highway during convoy movement, but the practical reality was different. Civilian buses, trucks, cars, and motorcycles continued to move on the highway, sometimes ahead of the convoy, sometimes alongside it, sometimes merging from side roads. Police personnel at intersections held back civilian traffic when possible but could not maintain a sterile corridor over the full 270-kilometre route. Intelligence officials had warned about this gap repeatedly. After Pulwama, that warning would acquire retrospective force.
The Mahindra Scorpio had been bought used in late 2018. Indian National Investigation Agency investigators would later trace its purchase, registration, and movement through a chain of intermediaries who had no idea what the vehicle would be used for. The explosive payload was assembled over multiple days at a safe house in Pulwama district. The composition was a mix of ammonium nitrate, RDX, and gelatine sticks. The total weight is contested in different reports, with figures ranging from 200 kilograms (the lower end of NIA estimates) to 350 kilograms (the higher figure cited in initial media reporting based on blast-pattern analysis). The lower figure is more consistent with subsequent NIA charge-sheet documentation; the upper figure remains in circulation because of how widely it was reported in the immediate aftermath. Either figure represented an order of magnitude more explosive than any previous Kashmir VBIED.
At approximately 2:55 p.m., Adil Ahmad Dar drove the Scorpio out of a service road near Lethpora and onto the highway. He pulled alongside the convoy. The convoy was moving at the speed dictated by its slowest vehicle, perhaps forty-five kilometres per hour. Dar accelerated to match. He picked the bus he wanted, a vehicle of the 76th Battalion CRPF carrying personnel of multiple ranks who had just completed leave. He drove the Scorpio into the bus’s left side at an angle that maximised the contact area between the explosive load and the bus’s structure.
The detonation occurred at 3:15 p.m. The blast destroyed the targeted bus completely, killing every CRPF passenger inside it. Adjacent vehicles in the convoy were thrown off the road, mangled, or partially destroyed. The blast crater on the highway was approximately one and a half metres deep and three metres across. Bodies and bus debris were scattered across a radius of about a hundred metres. Within ninety minutes, photographs of the scene began circulating on Indian social media, faster than any official statement. By 5:00 p.m., the death toll was being reported as twenty. By 7:00 p.m., it had risen to thirty. By the following morning, the final figure of forty CRPF personnel killed had stabilised, with five more grievously wounded who would require months of medical care. The 76th Battalion CRPF had lost almost an entire platoon in a single incident.
The Vehicle and the Bomber
Adil Ahmad Dar’s path from Pulwama schoolboy to Lethpora suicide bomber is among the most thoroughly documented radicalisation cases in recent Kashmir history. He was born in March 1998 in Kakapora village, the son of a small-scale shawl trader. He attended local schools through Class 10. By his family’s account, he was an ordinary teenager who played cricket, helped at his father’s shop, and showed no early indication of religious or political extremism. The first inflection point came in 2016, during the unrest that followed Burhan Wani’s killing. Dar, then eighteen, was reportedly stopped at a security checkpoint and forced to rub his nose on the ground in front of his peers. The humiliation, his family said later, changed him.
Between 2016 and early 2018, Dar attended a series of religious gatherings in Pulwama district, where Jaish-e-Mohammed had cultivated a small but committed presence among locally radicalised youth. By the family’s account, he became progressively more withdrawn, more religious, more interested in Kashmir’s political situation, and less interested in school. In March 2018, after another reported confrontation with security personnel, he disappeared from home. His family registered a missing-persons report. Within weeks, Indian intelligence had identified him as having joined Jaish-e-Mohammed under the guidance of handlers based in southern Kashmir.
For approximately ten months between March 2018 and February 2019, Dar moved between safe houses in Pulwama and Anantnag districts. Indian intelligence later traced him through phone records, family contacts, and the testimony of arrested handlers. His training, by NIA accounts, included weapons familiarisation, basic explosives handling, and ideological indoctrination. The most operationally significant phase came in the final two months before the attack, when he was paired with the explosive payload, the vehicle, and the operational plan. By February 10, four days before the attack, he had recorded the so-called martyrdom video that Jaish-e-Mohammed would release on the day of the bombing. In the video, he wears a vest, carries an assault rifle, and speaks in Kashmiri-accented Urdu about his decision to give his life for what he describes as the liberation of Kashmir.
The Mahindra Scorpio had a registration history that connected it back to a chain of small dealers and intermediary owners across Kashmir. None of those individuals had any awareness of the vehicle’s eventual use. The most direct chain was through Sajjad Ahmad Bhat, a young man from Anantnag who had been recruited into the Jaish cell some months earlier. Bhat purchased the Scorpio from a dealer, drove it for several weeks to establish ordinary use patterns, and then turned it over to the bomb-making team in Pulwama. Bhat himself was killed in a security operation in March 2019, less than a month after Pulwama, during a cordon-and-search operation in Pinglan village. NIA charge sheets would later identify multiple other Kashmir-based JeM operatives as having played roles in the operation.
The most senior figure in the operational chain to be captured was Mohammad Umair Farooq, a Pakistan-based Jaish operative who had crossed into Kashmir specifically to oversee the Pulwama operation. NIA documentation places Farooq in southern Kashmir from late 2018, working with Kashmiri-origin operatives on the bomb-making, the suicide-bomber selection, and the attack execution. He was killed in March 2019 in a separate security operation. Other operatives, including some who had handled communications and logistics, were captured alive and provided substantial information that informed the eventual NIA charge sheet, filed in August 2020, which named nineteen accused including Masood Azhar, his brother Rauf Asghar, and the larger Jaish leadership in Pakistan. None of the Pakistan-based accused would face trial in any Indian court because no Pakistani authority would cooperate in their extradition or prosecution, a pattern consistent with every previous case involving Pakistan-based handlers of attacks inside India.
The bomb-making process itself, as reconstructed by NIA forensic teams from residue analysis, eyewitness accounts of the safe-house activities, and captured-handler testimony, took place over approximately three weeks in two locations near Pulwama town. The composition required mixing ammonium nitrate, sourced through commercial agricultural channels but in quantities exceeding any plausible legitimate use, with RDX brought across the Line of Control over a period of months in small concealed shipments, and gelatine sticks acquired from quarrying operations in Kashmir. Each component was chosen for specific operational reasons: ammonium nitrate provided bulk and a base oxidiser, RDX provided the high-explosive intensity that would maximise blast damage against an armoured bus, and gelatine sticks served as the initiating charge that would detonate the main payload. The bomb-making team included at least two operatives with explicit explosives-handling training, both of whom Indian intelligence later identified through forensic and testimonial evidence. The vehicle conversion, in which the Mahindra Scorpio’s fuel tank and rear cargo area were modified to hold the payload while preserving an external appearance of normal civilian use, took place over approximately a week in the final phase before the operation. Adil Ahmad Dar received specific driver-training during this period to handle the laden vehicle and to execute the close-approach manoeuvre that would maximise the blast contact with the targeted bus.
The Detonation and Its Aftermath
In the first hour after the blast, local police, CRPF rapid-response teams, and ambulances reached the scene. The injured were transferred to the army’s 92 Base Hospital at Badami Bagh in Srinagar and to the Sher-i-Kashmir Institute of Medical Sciences. The dead were identified through fingerprint records, tattoo identification, and personal belongings, since many bodies were too badly damaged for visual recognition. By midnight, the families of the forty CRPF personnel were being notified across multiple Indian states: thirteen of the dead were from Uttar Pradesh, six from Punjab, four from Rajasthan, four from Madhya Pradesh, and the remainder from West Bengal, Maharashtra, Tamil Nadu, Bihar, Jharkhand, Odisha, Karnataka, Himachal Pradesh, and Uttarakhand. The geographic spread of the dead, which would become a major theme in subsequent media coverage, made Pulwama in some practical sense a national event in a way that earlier Kashmir attacks had not been.
Jaish-e-Mohammed claimed responsibility within ninety minutes of the blast. The claim came through the organisation’s regular media channels and included Adil Ahmad Dar’s pre-recorded video. The speed of the claim was operationally important: it removed any ambiguity about authorship, foreclosed the diplomatic pretence that had occasionally followed previous attacks, and presented the Indian government with an unmistakably attributable casus belli. Pakistan’s foreign office issued a statement the following morning that condemned the attack but rejected any allegation of Pakistani state involvement and demanded India share evidence linking Pakistan-based handlers to the operation. This response followed a script that had been used after every major attack on India since at least 2001, and its predictability was part of what made the Indian decision space narrow.
The intelligence assessment that reached Prime Minister Modi within twenty-four hours of the bombing reportedly identified three layers of culpability: Adil Ahmad Dar himself, the Kashmir-based JeM cell that had supported him, and the Pakistan-based JeM leadership and their ISI handlers who had directed the operation. The first two layers could be addressed through the standard counter-terrorism response of cordon-and-search operations, captures, and prosecutions. The third layer could not be addressed without Pakistani cooperation, and Pakistani cooperation was not going to be forthcoming. This assessment is what reduced the question of an Indian response from an open analytical problem to a narrower set of operational choices.
Public reaction across India over the following days was an intense and politically formative event. Funeral processions for the forty dead were held in cities and villages across multiple states, attracting large crowds, sustained television coverage, and visible expressions of grief and anger. Politicians of every party visited the families of the dead. Prime Minister Modi, speaking at a public event in Jhansi the day after the bombing, pledged that the perpetrators would pay a heavy price and signalled that the security forces had been given freedom to determine the response. The phrasing was deliberate: it foreshadowed the breaking of established constraints without naming the specific operation that would follow.
Television coverage in India over the seventy-two hours after the bombing was unprecedented in scale and emotional intensity. Most major Indian news channels suspended regular programming for sustained Pulwama coverage, with continuous streaming of funeral processions, family interviews, military analyst commentary, and political reactions. Social media in the same period saw a coordinated outpouring of nationalist sentiment that dwarfed previous post-attack patterns. Hashtags demanding revenge, hashtags celebrating CRPF sacrifice, and hashtags directed at Pakistani targets trended for days. The intensity of the public response, while genuine in its grief, also created political conditions in which any Indian response short of visible kinetic action against Pakistan would have appeared inadequate. The pre-existing political logic, in which the BJP government had built its national-security identity around the 2016 surgical strikes, intersected with the social-media-amplified public mood to produce a response space that was narrower than under any comparable previous attack.
The diplomatic response moved in parallel with the military preparations. India formally withdrew Most Favoured Nation trading status from Pakistan, raised customs duties on Pakistani imports to 200 percent, and recalled its high commissioner from Islamabad. The international response was generally sympathetic to India: the United States, the European Union, France, the United Kingdom, Russia, and Saudi Arabia all condemned the attack and called on Pakistan to act against Jaish-e-Mohammed. China, as had been its consistent practice for over a decade, did not name Jaish-e-Mohammed or Masood Azhar specifically, citing what it called the need for further investigation, the same formula it had used to block UN designation of Azhar repeatedly between 2009 and 2019. Within weeks, however, even China would withdraw its objection, and Azhar would finally be designated by the UN sanctions committee in May 2019.
Within the Indian government, intelligence consolidation in the seventy-two hours after the bombing focused on three operational questions. The first was the full identification of the Kashmir-based cell that had supported the bomber: which safe houses, which handlers, which logistics chain, which financial conduits. By the morning of February 16, the Research and Analysis Wing and the Intelligence Bureau had assembled a working picture of the cell that would inform both the subsequent NIA investigation and the cordon-and-search operations that would intensify over the following weeks. The second was the cross-border command structure: which Pakistan-based Jaish leaders had directed the operation, and what the chain of command back to Bahawalpur looked like. By February 17, the assessment placed primary direction on Mohammad Umair Farooq, who had crossed into Kashmir to oversee the operation directly, and on Rauf Asghar, the operational head of Jaish based in Bahawalpur. The third question concerned the broader Pakistani institutional environment: what the ISI knew, what it had enabled, and what the implications were for any military response that would necessarily target infrastructure inside Pakistani territory. The answers to all three questions were available in working form by the time the Cabinet Committee on Security held its first post-Pulwama meeting on February 16.
The Twelve Day Decision
What happened in New Delhi between February 14 and February 26, 2019, has been partially declassified, partially leaked, and partially reconstructed through journalistic accounts. The overall shape of the decision-making process is now reasonably well established, even if individual moments remain disputed. The Cabinet Committee on Security met multiple times during those twelve days. Air Chief Marshal Birender Singh Dhanoa, then chief of the Indian Air Force, had been involved in contingency planning for cross-border airstrikes since at least the previous year, when National Security Adviser Ajit Doval had reportedly tasked the services with developing options for a kinetic response to a major terror attack that exceeded what the 2016 surgical strikes had demonstrated.
The first three days after the bombing were spent on intelligence consolidation, target identification, and political authorisation. Indian intelligence agencies, working with what they had gathered through technical and human sources over years, produced a list of Jaish-e-Mohammed facilities inside Pakistan that could plausibly be characterised as training or operational centres. The Balakot facility, in Khyber Pakhtunkhwa province, had been on Indian target lists for years. Located in a forested ridge area near Jaba village, it had been identified as a Jaish seminary that included basic militant training functions. Its remoteness, distance from civilian population centres, and depth of Pakistani territory made it operationally significant in two ways: a successful strike there would demonstrate that India was willing to penetrate Pakistani airspace at depth, and the relative absence of civilian collateral risk reduced the escalation risk if the strike went wrong.
By February 17 or 18, the target had been provisionally selected and the operational planning had moved to the IAF. The strike package would consist of twelve Mirage 2000 multi-role aircraft, equipped with SPICE 2000 precision-guided bombs supplied by Israel’s Rafael Advanced Defence Systems. The Mirage 2000 was selected because of its combination of low-altitude penetration capability, weapons-carrying capacity, and the IAF’s deep operational familiarity with the platform after thirty years of service. Supporting aircraft would include AWACS for early warning, Sukhoi-30 fighters for air superiority cover, and aerial refuellers. The total strike package, including supporting aircraft, would involve more than forty Indian aircraft.
The political authorisation came from a Cabinet Committee on Security meeting around February 21 or 22, attended by Prime Minister Modi, Home Minister Rajnath Singh, Defence Minister Nirmala Sitharaman, External Affairs Minister Sushma Swaraj, Finance Minister Arun Jaitley, and the heads of the armed forces and intelligence agencies. The decision was unanimous. The execution date was provisionally set for February 26, with weather and additional intelligence confirmation as the determining variables.
In the final forty-eight hours, two operational decisions were made. The first concerned the timing window. Pre-dawn was chosen for a combination of weather, sensor-coverage, and surprise considerations: Pakistani air defences were assumed to be at lower readiness in the small hours, civilian traffic on Pakistani airspace was minimal, and the cover of darkness reduced visual detection. The second concerned the question of whether to inform any third-party government in advance. The final answer was no. Even close partners, including the United States, were not given prior warning. The reasoning was that any pre-notification carried a non-zero risk of leakage, and that the Indian government wanted to present the strike as an accomplished fact rather than a process Pakistan or anyone else could interrupt.
At approximately 3:30 a.m. local time on February 26, the twelve Mirage 2000 jets took off from multiple bases in northern India. Their flight path took them along the international boundary, then over disputed Kashmir, then in a curving approach that crossed into Khyber Pakhtunkhwa from the north. SPICE 2000 bombs, each weighing approximately one ton with a guidance package that allows targeting of specific structures from stand-off ranges, were released against the Balakot facility at approximately 3:50 a.m. The pilots reported successful weapon release and returned via the same route. The entire mission, from take-off to landing, lasted approximately ninety minutes. By 8:00 a.m. local time, Foreign Secretary Vijay Gokhale held a press briefing in New Delhi announcing that the IAF had conducted a non-military pre-emptive action against a Jaish-e-Mohammed training camp at Balakot, claiming that a very large number of Jaish terrorists, trainers, senior commanders, and groups of jihadis being trained for fidayeen action had been eliminated. The full story of the airstrike, the satellite-imagery debate that followed, and the F-16-versus-MiG-21 aerial engagement of February 27 belongs to its own detailed treatment, but the headline fact for the present article is that India had crossed a line that had held for forty-eight years, and had crossed it because of what happened at Lethpora on February 14.
The day-by-day reconstruction of the twelve-day window, while incomplete in its classified details, reveals a decision tempo that distinguished Pulwama-Balakot from earlier post-attack responses. Day one (February 14) was consumed by casualty consolidation, public communication, and the initial Cabinet Committee on Security briefings. Day two (February 15) saw the first political signals from Prime Minister Modi at the Jhansi event and the diplomatic measures including MFN withdrawal. Days three and four (February 16-17) were the intelligence consolidation phase, with target lists being narrowed and primary attention focusing on a handful of Jaish-e-Mohammed facilities including the Balakot seminary. Days five and six (February 18-19) involved IAF operational planning, with the Mirage 2000 strike package being assembled, weapons sourcing being confirmed, and pilot briefings being initiated under tight compartmentalisation. Days seven through nine (February 20-22) included additional intelligence verification of the target, contingency planning for Pakistani military response scenarios, and the formal political authorisation by the Cabinet Committee on Security. Days ten and eleven (February 23-24) saw final weather assessments, sensor-coverage planning, and the establishment of the dummy operational profile that would mask the strike preparation from Pakistani signals intelligence. Day twelve was the strike itself.
Compared with the response timelines of earlier attacks, the twelve-day window for Pulwama-Balakot was historically short. The 2008 Mumbai attacks produced no Indian military response despite extensive analytical case for one. The 2016 Uri attack produced the cross-Line-of-Control surgical strikes after eleven days, almost identical to the Pulwama-Balakot window. The Pathankot attack of January 2016 produced no kinetic Indian response at all, instead generating a brief diplomatic engagement in which India invited a Pakistani investigation team to Pathankot, an experiment that failed within weeks. The pattern across these cases suggests that the operational tempo of Indian responses has been compressed substantially since 2014, that the institutional capacity for rapid decision-making and execution has been built progressively, and that the twelve-day Pulwama-Balakot window reflected this institutional maturation rather than a hasty improvisation.
Key Figures
Adil Ahmad Dar
Twenty-year-old Kashmiri suicide bomber from Kakapora village in Pulwama district, recruited and indoctrinated by Jaish-e-Mohammed handlers between 2016 and 2018, who drove the explosive-laden Scorpio into the CRPF bus on February 14, 2019. His radicalisation followed a now-familiar Kashmir trajectory: ordinary local youth, encounter with security forces during a period of unrest, gravitation toward religious gatherings cultivated by Jaish handlers, disappearance from home, training, indoctrination, and selection for the operation. His pre-recorded video, released by Jaish on the day of the bombing, established the local Kashmiri face of an operation that depended on Pakistan-based logistics, finance, and command. His death in the bombing eliminated any possibility of capture or interrogation, which was operationally significant for Jaish: the Pakistan-based handlers who had directed him would not be exposed by any Indian custodial proceeding.
Mohammad Umair Farooq
Pakistan-based Jaish-e-Mohammed operative who crossed into Kashmir in late 2018 to oversee the Pulwama operation directly. NIA documentation places him in southern Kashmir from approximately October 2018, working with the locally recruited Kashmiri cell on bomb construction, vehicle preparation, and target reconnaissance. Farooq’s presence in Kashmir, rather than the more typical pattern of remote handling from Pakistan, indicated the operational priority Jaish leadership placed on Pulwama. He was killed in a Indian security operation in March 2019, less than a month after the bombing, during a cordon-and-search action that targeted the residual Jaish cell.
Sajjad Ahmad Bhat
Anantnag-origin Kashmiri operative who purchased the Mahindra Scorpio used in the bombing, drove it for several weeks to establish ordinary-use patterns, and turned it over to the bomb-making team. Bhat himself was killed in a separate Indian security operation in Pinglan village in March 2019. His role, while peripheral to the bomb construction itself, illustrated the depth of local recruitment Jaish had achieved in southern Kashmir by 2018.
Masood Azhar
Founder of Jaish-e-Mohammed, freed by India in December 1999 during the IC-814 hijacking ransom exchange, and the man whose organisation ordered, planned, financed, and executed the Pulwama operation from its Bahawalpur headquarters in Punjab province. Azhar’s biographical arc is the through-line of every major JeM attack against India: from the 2001 Indian Parliament attack through Pathankot in 2016 to Pulwama in 2019. His brother Rauf Asghar, who runs Jaish operationally, was named as a primary accused in the NIA charge sheet filed in August 2020. Neither has ever faced an Indian court because Pakistan has never extradited any of them, despite the UN sanctions designation that came through, finally, in May 2019.
Narendra Modi
Prime Minister of India since May 2014, leading the BJP government that had built its national-security identity around the 2016 surgical strikes after Uri and that faced a general election within sixty days of Pulwama. Modi’s public statements in the days after the bombing signalled the unusual posture: rather than the careful diplomatic phrasing that had followed earlier attacks, he made explicit that the security forces had been given the freedom to determine the response, language understood across Indian politics as authorisation for kinetic action. His role in the actual operational decisions remained as a member of the Cabinet Committee on Security, where the Balakot decision was taken collectively, but his public posture reduced the political space for any response short of visible kinetic action.
Ajit Doval
National Security Adviser since May 2014, former Intelligence Bureau chief, and the figure most associated within Indian government with the operational philosophy that prefers proactive offensive measures over reactive diplomatic ones. Doval reportedly led the cross-departmental coordination that produced the Balakot strike option, including the target-identification work, the political-authorisation process, and the operational integration with the IAF. Doval’s longstanding strategic preference for what he had publicly described as a defensive-offence doctrine became the operating philosophy of the Indian response to Pulwama.
Birender Singh Dhanoa
Air Chief Marshal of the Indian Air Force at the time of Pulwama and Balakot, who had overseen IAF contingency planning for cross-border strikes for over a year before the bombing. Dhanoa’s role in selecting the Mirage 2000 platform, the SPICE 2000 munition, and the Balakot target was central. His subsequent press conferences defending the strike’s effectiveness, including in the face of satellite-imagery questions, became part of the post-strike public messaging. Dhanoa’s career arc placed him in the unusual position of an air force chief who oversaw the first IAF cross-border strike inside Pakistani territory since 1971.
Imran Khan
Prime Minister of Pakistan since August 2018, and the civilian leader whose government’s response to Pulwama would shape Pakistan’s diplomatic posture during the crisis. Khan’s public statements after Pulwama denied Pakistani state involvement, called for evidence to be shared, and offered cooperation on investigation. After Balakot, he announced the return of the captured Indian pilot Wing Commander Abhinandan Varthaman as a peace gesture. Whether Khan exercised any meaningful operational influence over Pakistan’s military response is unlikely; the operational decisions were made by Army Chief Bajwa and the corps commanders, with Khan providing the diplomatic framing.
Qamar Javed Bajwa
Pakistan Army Chief from 2016 through 2022, who held actual operational authority over Pakistani military and intelligence policy during the Pulwama-Balakot crisis. Bajwa’s prior outreach toward Kashmir-related de-escalation, expressed in his 2018 speeches about peace with India, did not translate into any operational restraint on Jaish-e-Mohammed during the period when the Pulwama operation was being prepared. The pattern, consistent with three decades of Pakistani military behaviour, was that public diplomatic gestures and operational continuation of state-sponsored militant activity occurred simultaneously, controlled by different parts of the institution.
Consequences and Impact
The immediate consequences of Pulwama, in the first six months after the bombing, included measurable shifts across multiple domains. Diplomatically, India recalled its high commissioner from Islamabad, withdrew Most Favoured Nation status from Pakistan, raised tariffs on Pakistani imports to 200 percent, and reduced commercial movement across the Wagah border to a trickle. Pakistan, in turn, closed its airspace to Indian commercial aviation for several months, affecting hundreds of flights and costing Indian carriers significant operational and financial disruption. The composite-dialogue framework that had governed India-Pakistan engagement since the early 2000s, already moribund, was effectively buried.
Domestically in India, the political consequences reshaped the 2019 general election. The BJP campaigned heavily on the Balakot strike as evidence of doctrinal change, and the public perception of decisive national-security action contributed to the party’s expanded mandate in May 2019. Opposition criticism of the strike’s tactical effectiveness was dismissed as politically motivated; the strategic significance of having struck inside Pakistani territory was the public-facing fact, and the satellite-imagery debate over building damage receded into specialist commentary. The election result, with BJP securing 303 Lok Sabha seats out of 543, gave Prime Minister Modi a stronger second-term mandate than the first, and one in which the security and Kashmir agendas would be substantially expanded.
In Kashmir itself, Pulwama and its aftermath accelerated a security crackdown that had been intensifying for several years. CRPF deployment patterns were modified to reduce convoy vulnerabilities: civilian traffic clearance during convoy movement was tightened, convoy sizes were reduced by improving rotation logistics, and air movement of CRPF personnel between Kashmir and the mainland was expanded. Cordon-and-search operations against Jaish and Hizbul Mujahideen networks intensified, producing a sustained pace of encounter killings of militants through 2019 and into 2020. By August 2019, the Indian government would revoke Article 370 of the Constitution, which had given Jammu and Kashmir special status, in a move whose timing and political logic were shaped in part by the post-Pulwama environment in which a more assertive Kashmir policy could be pursued.
The impact on Jaish-e-Mohammed itself was substantial in the medium term. The UN Security Council finally designated Masood Azhar as a global terrorist in May 2019, after China withdrew the technical hold it had maintained for over a decade. The designation imposed asset freezes, travel restrictions, and arms embargoes against Azhar personally, although the practical effect inside Pakistan was limited because Pakistani authorities did not implement the sanctions in any meaningful operational sense. Azhar himself disappeared from public view after Balakot and has not been confirmed seen since. Whether he remains in ISI protective custody, has gone into deep concealment for security reasons, or has died, is among the open questions of contemporary South Asian counter-terrorism.
The international diplomatic consequences extended beyond India and Pakistan. The Financial Action Task Force, the international anti-money-laundering body, kept Pakistan on its grey list throughout the post-Pulwama period and added compliance benchmarks specifically targeting Pakistani action against UN-designated terror groups including Jaish. Pakistan would eventually be removed from the grey list in October 2022, but only after extensive demonstrated compliance steps, many of which were directly driven by the post-Pulwama international consensus that Pakistan’s tolerance of groups like Jaish was no longer acceptable. The Belt and Road project’s exposure to Pakistani jihadist groups, the Saudi-Iran alignment toward containment of cross-border militant violence, and the United States designation policies all shifted in ways that traced back, in part, to the diplomatic environment Pulwama created.
For Indian military doctrine, the consequences were doctrinal in the precise sense that the term implies. The IAF’s demonstrated ability to penetrate Pakistani airspace at depth, deliver precision-guided munitions on a stand-off basis, and recover its full strike package without losses (despite the F-16-versus-MiG-21 engagement of the following day) became part of the operational repertoire. The 2025 Operation Sindoor, in which Indian missiles and aircraft would strike multiple Pakistani targets across four days, was operationally and conceptually traceable to the Balakot precedent. What was unprecedented in 2019 had become a baseline by 2025.
The institutional consequences within India’s national-security apparatus extended across multiple agencies. The Research and Analysis Wing’s Kashmir desk was substantially restructured after Pulwama, with additional resources directed at locally radicalised threat actors, expanded technical surveillance capacity, and deepened liaison arrangements with the Intelligence Bureau and J&K Police. The Indian Air Force’s contingency planning capacity for cross-border operations was institutionalised through expanded exercises, dedicated units for stand-off precision strikes, and accelerated procurement of platforms including the Rafale fighter that had been on order before Pulwama and whose delivery beginning in 2020 was framed in part by post-Pulwama operational requirements. The Defence Ministry’s annual planning documents began to reflect, more explicitly than before, the assumption that cross-border kinetic responses to major terror attacks would be part of any future crisis cycle.
The economic consequences of the post-Pulwama diplomatic measures were modest in the short term and significant in the cumulative long term. India-Pakistan trade had been small in absolute terms even before MFN withdrawal, with annual bilateral trade in the range of two billion dollars, and the suspension of MFN status reduced this further to negligible levels. The closure of Pakistani airspace to Indian commercial aviation in February-July 2019 cost Indian carriers an estimated 700 million dollars in additional fuel, longer routes, and disrupted schedules. The Wagah-Attari border, the principal land crossing for goods and people, saw a substantial reduction in commercial traffic that has not recovered. The cumulative effect was a structural disengagement between the two economies that, by 2025, made any future normalisation of bilateral economic relations a significantly larger undertaking than would have been the case in a continuous-engagement environment.
The Kashmir-specific consequences of Pulwama and the post-Pulwama policy environment have been substantial and contested. The August 2019 revocation of Article 370 of the Indian Constitution, which removed the special status that Jammu and Kashmir had held since 1949, was facilitated by the political environment Pulwama had created. The accompanying reorganisation, which divided the former state into the union territories of Jammu and Kashmir and Ladakh, was the most far-reaching constitutional change in India’s federal structure in decades. Whether the change has produced the security stabilisation its advocates argued for, or has deepened the alienation that radicalisation exploits as critics have argued, is a question that the next decade of Kashmir politics will determine. The April 2025 Pahalgam attack, which killed twenty-six tourists at a meadow in southern Kashmir, demonstrated that whatever stabilisation the post-2019 measures had produced, it had not eliminated the underlying threat.
Pakistan’s domestic political consequences of Pulwama were less visible in real time but became significant over the following years. The civilian government of Prime Minister Imran Khan, which had begun with overtures toward dialogue with India, found those overtures effectively foreclosed by the Pulwama-Balakot crisis and its aftermath. The Pakistan military’s institutional response, including the operational continuity of Jaish-e-Mohammed despite the international pressure, demonstrated that no fundamental shift in Pakistan’s strategic-militancy doctrine had occurred. The eventual removal of Pakistan from the FATF grey list in October 2022 reflected demonstrated compliance steps but did not reflect any genuine institutional break with the longstanding pattern of state-tolerated militant infrastructure. The continuity that Pakistani institutional behaviour displayed across the Pulwama-Balakot crisis, the Article 370 revocation, the 2025 Pahalgam attack, and Operation Sindoor is the most striking feature of the post-2019 South Asian security landscape.
The cultural and informational consequences of Pulwama within India deserve specific attention. The funeral coverage of the forty CRPF personnel, broadcast continuously across television networks for several days, established a template for how Indian media would cover security-personnel deaths in subsequent attacks. The use of social media to amplify nationalist sentiment, organise public mobilisation around political demands for response, and create sustained pressure on government decision-making, became a feature of Indian political life that has continued to develop. The 2019 Hindi film Uri: The Surgical Strike, released several weeks before Pulwama, was already shaping public conceptions of how decisive cross-border response should look. After Pulwama and Balakot, an additional wave of films, television programmes, and documentary content reinforced the public framing of cross-border kinetic response as the appropriate Indian doctrine. The 2025 release of Dhurandhar, the Ranveer Singh blockbuster about India’s covert counter-terrorism operations in Pakistan, occurred within a public-cultural environment whose foundations were laid in the post-Pulwama period.
Analytical Debate
Was Pulwama a Jaish operation or an ISI operation
The first major analytical debate surrounding Pulwama concerns where to locate the operational direction. The Kashmiri suicide bomber and the Kashmir-based cell were unambiguously Jaish-e-Mohammed personnel. The Pakistan-based command and finance were unambiguously Jaish leadership. The question is whether the ISI, Pakistan’s military intelligence directorate, gave operational direction beyond its longstanding background relationship with Jaish, or whether Pulwama represented an autonomous Jaish action that the ISI permitted but did not specifically direct.
The case for direct ISI direction rests on three pieces of evidence. First, the timing of the operation, six weeks before Indian general elections, suggested strategic political calculation of a kind more associated with state-level decision-making than with militant-organisation autonomous planning. Second, the explosive payload was unusually large for a Kashmir VBIED, suggesting access to military-grade material whose movement across the Line of Control would have required ISI logistical cooperation. Third, the operational sophistication, including the multi-month preparation, the dedicated Pakistan-based handler crossing into Kashmir, and the specific target selection, exceeded what Jaish’s autonomous operational capability typically produced.
The case for Jaish autonomy rests on the organisation’s track record of having mounted earlier major attacks (Pathankot in 2016, the Indian Parliament attack in 2001) with similar operational complexity, the documented Jaish recruitment infrastructure in Kashmir that did not require new ISI initiation, and the absence of any direct evidence of ISI personnel involvement in the Pulwama planning. Jaish, in this reading, is sophisticated enough to plan major operations on its own, and the ISI’s role is the broader enabling environment rather than specific operational direction.
The most defensible position, given the available evidence, is that the binary itself misrepresents the relationship. Jaish-e-Mohammed has functioned for over two decades as an organisation whose autonomy and direction blend continuously. The ISI does not need to specifically order each Jaish operation because Jaish operates within a strategic framework the ISI has shaped, recruits within networks the ISI tolerates, finances itself through channels the ISI permits, and conducts operations whose general targeting pattern matches Pakistani strategic preferences. The question of whether a specific operation was ISI-ordered or Jaish-autonomous is, in a meaningful sense, malformed: the autonomy exists within a directional environment, and the direction operates through autonomy. Pulwama is consistent with that pattern.
The deeper analytical point is that the binary framing originates in Western-academic distinctions between proxy and direct-action operations that do not quite map onto the South Asian security ecosystem in which Jaish-e-Mohammed has operated. The relationship between the Pakistani security establishment and groups like Jaish has been described variously as patronage, sponsorship, alliance, ideological partnership, and tactical convenience, and the appropriate description varies across time and across specific operations. What the framings share is the recognition that Jaish-e-Mohammed has not at any point in its history operated in genuine independence from the Pakistani security establishment, and that any operation Jaish conducts at the scale and complexity of Pulwama presupposes the institutional environment that Pakistani state policy has created and sustained.
The election timing question
A persistent question about the Indian government’s response is whether the decision to conduct the Balakot airstrike was strategically optimal or substantially shaped by the impending general election. The strict version of the political-motivation thesis holds that the BJP government chose a high-visibility, high-risk military operation specifically because of its electoral utility, and that a more cautious response (covert action, sustained diplomatic pressure, expanded intelligence operations) might have been strategically preferable.
The strict thesis is difficult to sustain on its own terms. The political incentive to respond visibly was a real factor, but it was not in tension with the strategic logic for action: the cumulative pattern of Pathankot, Uri, and Pulwama had already exhausted the diplomatic option from the Indian government’s perspective, the international environment was unusually permissive for an Indian military response, and the operational capacity to conduct cross-border strikes had been built over years specifically for use in this kind of contingency. The election timing made the response politically necessary, but it did not make a militarily and strategically unjustifiable response politically necessary. The Balakot strike was both electorally beneficial and strategically defensible, and these were not mutually exclusive.
The weaker version of the political-influence thesis, which is more defensible, holds that the election timing affected the specific shape of the response (visible airstrikes rather than covert operations, immediate public announcement rather than ambiguity, expanded political messaging in the weeks that followed) without determining whether a response would happen. This version is consistent with how democracies generally make national-security decisions: political and strategic logics interact, and the resulting decision is shaped by both, rather than being determined by either alone.
The Balakot tactical question
The third major debate concerns whether the Balakot airstrike actually achieved its tactical objectives. Indian government statements claimed that a very large number of Jaish terrorists, trainers, senior commanders, and training groups had been eliminated. Pakistani government statements claimed that the bombs had hit empty hillside locations and that no casualties had occurred. Independent satellite-imagery analyses by Western open-source intelligence analysts, reviewed in the days and weeks after the strike, generally showed that the buildings at the targeted location remained standing, with damage visible to surrounding terrain but no obvious indication of the structural destruction that would accompany large casualty figures.
The most defensible interpretation of the available evidence is that the tactical results of the Balakot strike fell somewhere between the Indian and Pakistani claims, and that the precise figures are genuinely uncertain. The SPICE 2000 munition, designed for precision targeting of specific structures, may have hit specific floors of buildings while leaving the larger structure visibly intact in subsequent imagery. The number of personnel present at the seminary at the time of the pre-dawn strike is impossible to verify independently. The Indian claim that very large numbers were killed is unverifiable; the Pakistani claim that no one was killed is also unverifiable. The honest position is that the tactical outcome remains uncertain, with the strategic significance of the strike (the demonstration that India would penetrate Pakistani airspace at depth) being independent of the tactical body count.
This separation between tactical effectiveness and strategic significance is itself a crucial part of how to understand the operation. India’s purpose at Balakot was not primarily to eliminate a specific set of Jaish personnel; it was to establish a precedent. The precedent was established regardless of the tactical body count. In that strict sense, the strike achieved its primary objective even if the casualty figures cannot be confirmed.
The escalation-spiral question
The fourth major debate concerns whether the Indian doctrinal shift demonstrated by Balakot, in combination with the earlier 2016 surgical strikes and the later 2025 Operation Sindoor, represents strategic maturation that has stabilised deterrence or a dangerous escalation spiral that will eventually reach the nuclear threshold. The maturation reading holds that India’s progressively expanding repertoire of responses (covert action, surgical strikes, airstrikes inside Pakistani territory, missile strikes during the 2025 conflict) has clarified Pakistani expectations, raised the cost to Pakistan of continued tolerance of groups like Jaish, and produced a more stable equilibrium in which terror attacks happen less frequently because the consequences are higher.
The escalation-spiral reading holds the opposite: each barrier crossed becomes the new baseline for the next response, the cycle of attack-and-response is intensifying rather than stabilising, the Pakistani military’s incentive to absorb costs without reducing its tolerance of militant groups has not changed, and the trajectory will eventually reach a level of escalation that cannot be contained below the nuclear threshold. The Pahalgam attack of April 2025 and the subsequent four-day Operation Sindoor are read by this camp as evidence that the cycle continues at progressively higher intensity rather than stabilising at any equilibrium.
The available evidence does not yet decisively favour either reading. The frequency of major attacks on Indian targets has reduced since 2019, which is consistent with the maturation thesis. The intensity of the 2025 escalation, with multi-day exchanges of missile and air strikes, was historically unprecedented and is consistent with the spiral thesis. The honest position is that both readings remain analytically defensible, and that the trajectory of the next decade will determine which one was right. Pulwama-Balakot is a node in that ongoing debate, not its resolution.
The intelligence failure question
The fifth major analytical debate concerns the degree to which Pulwama represents a preventable intelligence failure. The case for substantial preventability rests on several pieces of evidence. The Kashmir-based JeM cell that supported Adil Ahmad Dar had been operating in Pulwama district for over a year before the bombing. The recruitment of Dar, his disappearance from home in March 2018, and his subsequent radicalisation followed a pattern that Indian agencies were aware of in general terms. The accumulation of explosive material in the quantity used at Lethpora, between 200 and 350 kilograms, would have required logistical activity over weeks or months that left some signals. The convoy size and timing on February 14 were predictable from CRPF rotation patterns and the post-snowfall backlog. Each of these elements, considered individually, was within the detection capability of the existing intelligence apparatus. What was missing was the integration of these elements into a coherent threat picture before the attack.
The case against full preventability rests on the structural difficulty of detecting locally radicalised actors operating within communities that provide passive cover. The shift from cross-border infiltration to local radicalisation, which was the main militant adaptation of the post-2016 period, reduced the value of cross-border surveillance that had previously detected most major attack preparations. Suicide attacks of the Pulwama type, which were rare in Kashmir before 2019, did not have an established intelligence template. The Kashmir-resident Indian-citizen status of the bomber and most of the support cell limited the surveillance options that would have been available against known cross-border actors. Each of these factors contributed to a detection environment in which the Pulwama plot was harder to identify than earlier major attacks had been.
The most defensible assessment is that Pulwama represents a partial intelligence failure of a kind that intelligence services everywhere experience periodically when adversary methods shift faster than detection methods. The post-Pulwama reforms inside Indian agencies, including the restructured RAW Kashmir desk, the expanded technical surveillance capacity, and the deepened liaison among IB, RAW, and J&K Police, have addressed parts of the gap. Whether they have addressed it completely is a question that only the next major attack will answer.
Why It Still Matters
Pulwama remains relevant in 2026 for several intersecting reasons. The first is doctrinal. The Balakot precedent that Pulwama produced has shaped every subsequent Indian response to Pakistan-linked terrorism, including the most consequential one: Operation Sindoor in May 2025 after the Pahalgam tourist massacre, in which Indian missiles struck multiple Pakistani targets over four days. The doctrinal logic of cross-border kinetic response is now an established part of Indian strategic culture, and Balakot is the case study every defence-academy curriculum returns to in explaining how that logic was operationalised.
The second is the question of the long-term effectiveness of the post-Pulwama doctrine. The next major Pakistan-linked attack on India after Pulwama, in terms of casualties, was the April 2025 Pahalgam massacre, which killed twenty-six tourists at a meadow above Pahalgam in southern Kashmir. The six-year gap between major mass-casualty attacks (Pulwama in February 2019, Pahalgam in April 2025) is the longest such gap in over two decades and is consistent with the deterrence-effectiveness reading. But the existence of Pahalgam also demonstrates that the doctrine has not eliminated the underlying threat, and the resulting Operation Sindoor pushed the escalation envelope further than any previous post-attack response. Whether Pulwama-Balakot taught Pakistan a sustainable lesson or only postponed the next attack remains genuinely unsettled.
The third is the persistence of Jaish-e-Mohammed as an organisational structure. Despite the UN designation of Masood Azhar in May 2019, the Indian shadow-war operations against Pakistan-based terrorist figures that intensified through 2022 and beyond, and the post-Pahalgam Indian campaign that has further degraded Jaish’s senior cadre, the organisation continues to exist, recruit, and plan. The organisational continuity of JeM across more than two decades, including the periods of intense Indian and international pressure, illustrates how durable Pakistan’s tolerance of state-sponsored militant infrastructure remains.
The fourth is the radicalisation lesson. Adil Ahmad Dar’s path from a Kakapora schoolboy to a Lethpora suicide bomber illustrates how Kashmir-resident Indian citizens can be radicalised into mass-casualty terrorism through a combination of grievance produced by security-force interactions, religious-political messaging cultivated by Pakistan-based handlers, and operational support that flows from across the Line of Control. The Indian counter-radicalisation response to this lesson has been mixed: some elements (improved intelligence, expanded community engagement, education and employment programmes in Kashmir) have addressed root causes; other elements (security crackdowns, expanded surveillance, the post-2019 Article 370 changes) have been criticised by some analysts as deepening rather than ameliorating the underlying alienation that radicalisation exploits.
The fifth is the political-cultural shift in how India processes major terrorist attacks. The Pulwama coverage on Indian television, in social media, and in political rhetoric was the first instance of a full-spectrum mass mobilisation of public opinion in support of military action against Pakistan. Subsequent attacks, including Pahalgam, have followed similar patterns, with media coverage feeding political pressure for visible response and the political response feeding further media coverage. This dynamic has shaped how India debates national security to a degree that pre-Pulwama analysts would have found surprising.
For the larger arc of India-Pakistan relations, Pulwama is one of the small number of incidents that scholars and analysts identify as truly pivotal. The Kandahar hijacking of December 1999, the Indian Parliament attack of December 2001, the Mumbai attacks of November 2008, and the Pulwama attack of February 2019 form the sequence of mass-impact events that have progressively shaped the bilateral relationship. Pahalgam in April 2025 has joined this sequence, with its own consequential aftermath in Operation Sindoor. Within the sequence, Pulwama occupies a particular place: it was the attack that finally forced the Indian government to operationalise what had been theoretical for forty-eight years, the willingness to strike Pakistan proper. Once that operational reality was established, the subsequent escalation pattern that runs through Sindoor became possible. Without Pulwama, in some meaningful sense, none of what came after would have happened in the way it did.
The sixth dimension of continuing relevance concerns the implications for international counter-terrorism policy beyond South Asia. Pulwama-Balakot demonstrated, in real-world conditions, that a major democratic nuclear-armed state could conduct cross-border kinetic action against a state-sponsored terrorist target located in another nuclear-armed state, recover its strike package, manage the resulting escalation through limited-war means, and exit the crisis without nuclear use. Each of these elements was a question that pre-2019 strategic literature had treated as theoretical. The Balakot case provided empirical material for analysts examining similar dynamics in other regions where state sponsorship of cross-border terrorism intersects with nuclear deterrence, including the Middle East and East Asia. Whether the lessons drawn from Pulwama-Balakot will be portable to those other regions, or whether the specific features of the India-Pakistan relationship limit the generalisability, is a question that contemporary strategic studies continue to engage.
The seventh dimension is methodological. Pulwama was the first major Indian terror attack to occur in the era of full-spectrum smartphone-mediated public communication, in which photographs from the blast site were circulating on social media within ninety minutes, where suicide-bomber martyrdom videos were released through the same channels that hosted the funeral footage of his victims, and where the political pressure for response built and broadcast itself in continuous loops over twelve days. Every subsequent major attack in India, including Pahalgam in 2025, has occurred in a media environment whose characteristics were established in the Pulwama coverage. The democratic-pressure-on-strategic-decision-making dynamic that operated in those twelve days, with Cabinet decisions made under continuous public observation of the political consequences of inaction, has become a structural feature of how India processes security crises. This feature is generally absent in less democratic adversary states, including Pakistan, and the resulting asymmetry in domestic-political constraints on decision-making is itself a strategic factor whose implications are still being worked out.
Frequently Asked Questions
Q: What happened in the Pulwama attack?
On February 14, 2019, a Mahindra Scorpio loaded with between 200 and 350 kilograms of explosive material was driven into a CRPF bus on the Srinagar-Jammu National Highway near Lethpora village in Pulwama district, Kashmir. The suicide bomber, twenty-year-old Kashmiri Adil Ahmad Dar, detonated his vehicle alongside a bus carrying CRPF personnel returning to deployment after leave. The blast killed forty CRPF personnel and grievously wounded five more. The CRPF convoy comprised seventy-eight vehicles carrying 2,547 personnel, and the attack targeted a specific bus of the 76th Battalion. Jaish-e-Mohammed claimed responsibility within ninety minutes through its standard media channels and released a pre-recorded video of the bomber. The attack was the deadliest on Indian security forces in Kashmir since the start of the insurgency in 1989.
Q: How many CRPF personnel were killed at Pulwama?
Forty CRPF personnel were killed in the Pulwama attack on February 14, 2019. Five more were grievously wounded, requiring extensive medical treatment over subsequent months. The dead came from CRPF battalions drawn from across India, with thirteen from Uttar Pradesh, six from Punjab, four from Rajasthan, four from Madhya Pradesh, and the rest from West Bengal, Maharashtra, Tamil Nadu, Bihar, Jharkhand, Odisha, Karnataka, Himachal Pradesh, and Uttarakhand. The geographic spread of the dead made Pulwama an event that touched families and communities across most of India, contributing to the national scope of the political and emotional response that followed.
Q: Who was the Pulwama suicide bomber?
The suicide bomber was Adil Ahmad Dar, a twenty-year-old from Kakapora village in Pulwama district, Kashmir. Born in March 1998, he was an ordinary local youth through Class 10 schooling, the son of a small-scale shawl trader. His radicalisation began in 2016 during the unrest after Burhan Wani’s killing, after a reported humiliating encounter with security personnel. Between 2016 and 2018 he attended Jaish-e-Mohammed-cultivated religious gatherings in Pulwama district. In March 2018 he disappeared from home and joined Jaish under the guidance of Pakistan-based handlers and a Kashmir-based cell. For approximately ten months he moved between safe houses in southern Kashmir, receiving weapons familiarisation, basic explosives training, and ideological indoctrination, before being selected for the Pulwama operation.
Q: How much explosive was used in the Pulwama attack?
Estimates of the explosive payload range from 200 kilograms (the lower-end NIA figure based on charge-sheet analysis) to 350 kilograms (the higher figure cited in initial media reports based on blast-pattern assessment). The composition was a mix of ammonium nitrate, RDX, and gelatine sticks, assembled at a safe house in Pulwama district over multiple days before the attack. Either figure represented an order of magnitude more explosive material than typical Kashmir-region vehicle-borne IEDs, and the quantity strongly suggested either large-scale local accumulation over an extended period or supply from across the Line of Control with operational logistics that exceeded autonomous Jaish capacity.
Q: What was India’s response to Pulwama?
India responded with a combination of diplomatic, economic, and military measures. Diplomatically, India recalled its high commissioner from Islamabad and downgraded political engagement. Economically, India withdrew Most Favoured Nation trading status from Pakistan and raised customs duties on Pakistani imports to 200 percent. Militarily, twelve days after the bombing, on February 26, 2019, the Indian Air Force conducted the Balakot airstrike: twelve Mirage 2000 jets crossed into Khyber Pakhtunkhwa province in Pakistan and dropped SPICE 2000 precision-guided bombs on a Jaish-e-Mohammed seminary at Balakot. This was the first time since the 1971 war that India had struck inside Pakistani territory proper. The full operational reconstruction of the airstrike is treated separately.
Q: How many days between Pulwama and Balakot?
Twelve days. The Pulwama bombing occurred on February 14, 2019, and the Balakot airstrike occurred on February 26, 2019. During those twelve days, Indian intelligence consolidated the target list, the Cabinet Committee on Security met multiple times to review options, the Indian Air Force prepared the strike package of twelve Mirage 2000 jets and supporting aircraft, weather and intelligence variables were assessed, and political authorisation was given. The twelve-day window was historically short for a major military decision and reflected both the intensity of political pressure and the prior contingency planning that had been done over the preceding year.
Q: Was the Pulwama attack directed by the ISI?
The honest answer is that the question itself is somewhat malformed. Jaish-e-Mohammed operates within a strategic framework shaped by Pakistan’s Inter-Services Intelligence Directorate, recruits within networks the ISI tolerates, finances itself through channels the ISI permits, and conducts operations whose general targeting pattern matches Pakistani strategic preferences. Whether the specific Pulwama operation was ISI-ordered or Jaish-autonomous is less analytically meaningful than acknowledging that the Pulwama operation could only have happened within a Pakistani institutional environment that permits, finances, and shelters Jaish-e-Mohammed. Direct evidence of specific ISI personnel involvement in the Pulwama planning has not been publicly produced, but circumstantial indicators (the timing relative to Indian elections, the unusual size of the explosive payload, the operational sophistication) are consistent with state-level strategic calculation.
Q: Why did Pulwama lead to airstrikes inside Pakistan?
Pulwama led to airstrikes inside Pakistan rather than the kind of cross-Line-of-Control surgical strike India had conducted after the 2016 Uri attack because the cumulative pattern of Pathankot, Uri, and Pulwama had already exhausted the political and strategic case for keeping responses geographically limited to Indian-administered Kashmir. The Indian government concluded that escalation to the level of striking inside Pakistani territory was necessary to demonstrate that the costs of continued tolerance of Jaish-e-Mohammed had risen, and that the international environment was unusually permissive for such a strike. The Balakot facility, in Khyber Pakhtunkhwa, was selected because of its identification as a Jaish seminary, its remoteness from civilian population centres, and its depth in Pakistani territory, which maximised the demonstrative impact while reducing the civilian-collateral risk.
Q: Was Pulwama a Jaish-e-Mohammed operation?
Yes. Jaish-e-Mohammed claimed responsibility within ninety minutes of the bombing through its standard media channels, released a pre-recorded video of the suicide bomber Adil Ahmad Dar, and was confirmed as the operational organisation through subsequent NIA investigation. The NIA charge sheet filed in August 2020 named nineteen accused, including Jaish founder Masood Azhar, his brother and operational head Rauf Asghar, and multiple Pakistan-based and Kashmir-based Jaish operatives. The Kashmir-based cell that supported the suicide bomber was a Jaish unit operating under direction from Pakistan-based Jaish leadership.
Q: What was the political fallout in India after Pulwama?
The political fallout was substantial and lasting. The BJP government of Prime Minister Modi, facing general elections in April and May 2019, made the Balakot airstrike and the broader Indian response a central campaign theme. Public perception of decisive national-security action contributed to the BJP’s expanded mandate in the May 2019 election, in which the party secured 303 Lok Sabha seats out of 543, a stronger majority than its 2014 result. Opposition criticism of the strike’s tactical effectiveness was politically marginalised, and the strategic significance of the cross-border strike became part of mainstream Indian political discourse. The Article 370 revocation in August 2019, which removed Jammu and Kashmir’s special constitutional status, was facilitated by the political environment Pulwama had created.
Q: What happened to Masood Azhar after Pulwama?
Masood Azhar was finally designated as a global terrorist by the UN Security Council in May 2019, after China withdrew the technical hold it had maintained for over a decade. The designation imposed asset freezes, travel restrictions, and arms embargoes against him personally. After the Balakot airstrike, Azhar disappeared from public view and has not been confirmed seen since. Multiple reports have suggested he may be in ISI protective custody, in deep concealment for security reasons, or possibly dead, but no reliable confirmation has emerged. His biographical and operational role as the founder of Jaish-e-Mohammed makes his disappearance one of the open questions of contemporary South Asian counter-terrorism.
Q: Did the Pulwama attack involve cross-border explosive supply?
The available evidence suggests that the explosive material used at Pulwama, given its quantity (200 to 350 kilograms) and composition (a mix of ammonium nitrate, RDX, and gelatine sticks), was unlikely to have been accumulated entirely from local Kashmir sources. RDX in particular is a military-grade explosive whose presence in such quantities indicates either organised cross-border smuggling or large-scale theft from a controlled stockpile. The NIA investigation traced the material to a Jaish-e-Mohammed supply chain that included Pakistan-based logistical support, although the operational details of how the material crossed the Line of Control were not publicly disclosed in full. The cross-border supply question remains one of the operational dimensions where direct evidence is incomplete but circumstantial evidence is strong.
Q: How did Pakistan respond to the Pulwama attack?
Pakistan’s foreign office issued a statement the day after the bombing condemning the attack but rejecting any allegation of Pakistani state involvement and demanding that India share evidence linking Pakistan-based handlers to the operation. This response followed a script used after every major attack on India since at least 2001. After the Balakot airstrike of February 26, Pakistan denied that any significant casualties had occurred, claimed the bombs had hit empty hillside locations, and announced retaliatory measures. The most consequential of these was the F-16 incursion of February 27 that resulted in the capture of Indian pilot Wing Commander Abhinandan Varthaman, who was returned to India on March 1 in what Prime Minister Imran Khan framed as a peace gesture.
Q: What was the Abhinandan episode?
On February 27, 2019, the day after the Balakot airstrike, Pakistani F-16 jets conducted retaliatory operations across the Line of Control. In the resulting aerial engagement, Indian MiG-21 Bison pilot Wing Commander Abhinandan Varthaman engaged Pakistani aircraft and his MiG-21 was shot down over Pakistan-administered Kashmir. Abhinandan ejected, was captured by Pakistani forces, and was held for two days. Prime Minister Imran Khan announced his return on February 28 as a peace gesture, and he was handed over at the Wagah border on March 1. The Abhinandan episode complicated the post-Balakot narrative because it produced a Pakistani de-escalation gesture that was difficult to reconcile with the framing of Balakot as an unambiguous Indian victory. The MiG-21-versus-F-16 engagement also raised questions about Indian aircraft modernisation that have been addressed in subsequent years through expanded Rafale fighter procurement and other capability upgrades.
Q: Did India know in advance that Pulwama was being planned?
Indian intelligence agencies later acknowledged that the broad pattern of Jaish-e-Mohammed activity in Pulwama district during 2018 was known, including the recruitment of locally radicalised youth and the cultivation of safe houses, but the specific Pulwama operation, including the date, the convoy target, the suicide bomber identity, and the explosive payload, was not. This represents a significant intelligence failure of the kind that has been the subject of subsequent reviews and reforms in Indian counter-intelligence practice in Kashmir. The convoy size and timing, which were predictable from CRPF rotation patterns and the post-snowfall backlog, were available to Jaish handlers in ways that the underlying intelligence environment had not adequately accounted for.
Q: What changed for CRPF convoy security after Pulwama?
CRPF convoy security on the Srinagar-Jammu highway was modified after Pulwama in several ways. Civilian traffic clearance during convoy movement was tightened, with longer holds and clearer corridor management at sensitive stretches. Convoy sizes were reduced by improving rotation logistics, including expanded air movement of CRPF personnel between Kashmir and the mainland to prevent the kind of post-snowfall backlog that had produced the unusually large February 14 convoy. Vehicle inspection at side roads merging with the highway was increased. Standoff protocols for civilian vehicles approaching convoys were strengthened. Implementation has been uneven across different stretches of the highway, and intelligence-led operations to identify and dismantle Jaish cells in southern Kashmir have continued through 2025.
Q: How does Pulwama compare with the Uri attack?
The two attacks were the most consequential Kashmir-region terror events of the post-2014 period and form a comparative pair that defines India’s evolving response doctrine. The 2016 Uri attack killed nineteen Indian soldiers in their sleep at a base camp through a fidayeen assault by four Jaish operatives who infiltrated across the Line of Control. The Indian response, ten days later, was a cross-Line-of-Control surgical strike against terrorist launch pads in Pakistan-administered Kashmir, the first such operation publicly acknowledged. Pulwama killed forty CRPF personnel through a vehicle-borne IED detonated by a locally radicalised Kashmiri suicide bomber. The Indian response, twelve days later, was the Balakot airstrike inside Pakistan proper, the first such operation since 1971. Uri established that India would cross the Line of Control; Pulwama established that India would penetrate Pakistani territory at depth. Each attack represented a tactical and strategic escalation, and each Indian response established a new operational baseline.
Q: What does Pulwama mean for India-Pakistan relations going forward?
Pulwama and the Balakot response that followed marked the effective end of the composite-dialogue framework that had governed India-Pakistan engagement since the early 2000s. India’s diplomatic posture since 2019 has been that no normal diplomatic, economic, or cultural engagement with Pakistan is possible until Pakistan acts demonstrably against the terror infrastructure that produced Pulwama and similar attacks. This posture has been reinforced by the Pahalgam attack of April 2025 and Operation Sindoor that followed. The specific bilateral mechanisms (high-level diplomatic meetings, cricket cooperation, cultural exchanges, business engagement) that operated through the 2000s and into the early 2010s have not resumed and show no near-term signs of resumption. The longer-term question of whether any diplomatic framework can be reconstructed, and on what terms, remains genuinely open and is the subject of ongoing analytical and policy debate.
Q: Did the Pulwama attack achieve any strategic objective for Jaish-e-Mohammed?
The strategic calculation behind Pulwama, from the Jaish-e-Mohammed and Pakistani-establishment perspective, has been the subject of considerable post-incident analysis. The attack produced significant Indian casualties and demonstrated continued Jaish operational capacity. It also produced consequences that arguably did not serve Jaish or Pakistani strategic interests: the UN designation of Masood Azhar that China had blocked for a decade, the international diplomatic and FATF pressure that intensified through 2019 and beyond, the Indian Article 370 revocation that hardened Indian control over Kashmir, and the demonstrated Indian willingness to strike inside Pakistani territory that has shaped every subsequent crisis. Whether the operational success of producing forty Indian casualties outweighed the strategic costs is a question that Pakistani strategic planners would need to answer. The pattern of subsequent Jaish operations and the broader Pakistani institutional response suggests that the cost-benefit calculation has not produced a clear shift away from supporting groups like Jaish, even as the costs have visibly risen.
Q: What is the long-term significance of Pulwama in the Indian counter-terror trajectory?
Pulwama’s long-term significance lies in its role as the inflection point that operationalised what had been theoretical doctrine. Before February 2019, the option of striking inside Pakistani territory was on Indian planning maps but had not been used since 1971. After February 2019, the option moved from theoretical to executed, and from there into the operational repertoire that any subsequent Indian government could reach for. The 2025 Operation Sindoor, with its multi-day exchange of missile and air strikes, was operationally and conceptually traceable to the Balakot precedent, which was traceable to Pulwama. In the longer arc that runs from the 1999 IC-814 hijacking through the 2001 Indian Parliament attack and the 2008 Mumbai attacks to Pulwama and Pahalgam, Pulwama occupies a position similar to Mumbai 26/11 in 2008: an attack severe enough that the previous policy framework could not absorb it, and that therefore produced the policy framework of the next era.
Q: How does Pulwama fit into the larger pattern of JeM-orchestrated attacks?
Pulwama fits into a continuous pattern of major Jaish-e-Mohammed attacks against India that begins with the 2001 Indian Parliament attack and continues through the 2016 Pathankot airbase attack, the 2016 Uri attack (in which JeM operatives infiltrated across the LoC), Pulwama in 2019, and various attempts before and after. The pattern shows several consistent features: a Pakistan-based command structure operating from Bahawalpur, recruitment that combines Pakistan-based volunteers with locally radicalised Kashmiris, operational cycles that span months from initial planning to execution, and target selection focused on Indian security personnel. The escalation in attack severity, from small-scale ambushes to suicide vehicle bombings, and the shift from cross-border infiltration to local radicalisation represent two of the most significant evolutionary trends in JeM operational practice over the past two decades.
Q: What did the NIA charge sheet on Pulwama reveal?
The National Investigation Agency charge sheet, filed in August 2020, named nineteen accused individuals including Jaish-e-Mohammed founder Masood Azhar, his brother and operational head Rauf Asghar, his nephews who served in operational roles, and multiple Pakistan-based and Kashmir-based JeM operatives. The charge sheet documented the operational chain from Pakistan-based command through Mohammad Umair Farooq’s cross-border movement to the Kashmir-based cell that supported Adil Ahmad Dar. It traced the financial flows that funded the operation, the communication chains that connected the cell to Pakistan-based handlers, the explosive accumulation timeline, and the vehicle procurement chain. None of the Pakistan-based accused has faced trial in any Indian court because Pakistan has consistently refused extradition or domestic prosecution of Jaish leadership. The charge sheet remains the most comprehensive public documentation of the Pulwama operational architecture and continues to be referenced in subsequent legal and analytical work.
Q: Did India’s airspace closure to Pakistani aircraft affect global aviation?
The Pakistani decision to close its airspace to Indian commercial aviation in February 2019, which lasted until July 2019, had measurable global aviation effects. Indian carriers including Air India lost an estimated 700 million dollars over the closure period through additional fuel costs, longer routes, and disrupted schedules. International carriers using Pakistani airspace for transcontinental routes between Europe and Southeast Asia experienced minor rerouting effects. Cargo aviation was less affected because the longer routes added fuel cost rather than blocking movement entirely. The closure became a case study in how localised airspace decisions in tense bilateral environments can produce global economic ripples that extend well beyond the directly involved nations.
Q: How did Pulwama affect India’s defence procurement priorities?
Pulwama and the Balakot response that followed accelerated several Indian defence procurement priorities that had been in earlier planning stages. The Rafale fighter procurement from France, which had been signed in 2016 but whose delivery began only in 2020, was framed in post-Pulwama public communication as essential for maintaining air superiority in any future cross-border operation. The S-400 air defence system procurement from Russia, signed in 2018 but delivered beginning in 2021, was similarly justified by the air-defence requirements that the post-Balakot environment had clarified. Stand-off precision-strike capability investment, including indigenous BrahMos production and Israeli SPICE-series munition stocks, expanded substantially in the post-Pulwama period. The cumulative effect was an Indian defence posture by 2025 that was substantially better positioned for the kind of cross-border operation that Sindoor would require, and that positioning traced in significant part to the lessons drawn from the Pulwama-Balakot crisis.
Q: What lessons did Pulwama provide for Kashmir security policy?
Pulwama provided several lessons for Kashmir security policy that have shaped the subsequent six years of policy adjustment. The first was the importance of intelligence integration across local, state, and national agencies, with locally radicalised threats requiring fundamentally different surveillance and source-recruitment approaches than cross-border infiltration threats. The second was the vulnerability of routine logistical movements (such as the CRPF rotation that produced the February 14 convoy) when those movements followed predictable patterns that adversaries could exploit. The third was the operational risk of permitting civilian-military traffic mixing at sensitive stretches of strategic highways. The fourth was the radicalisation pipeline that connected security-force interactions, social-media networks, and Pakistan-based handlers, which required policy responses across the security, social, and educational domains. Implementation of these lessons has been mixed, with some elements addressed effectively and others remaining work in progress. The April 2025 Pahalgam attack, while operationally different from Pulwama, demonstrated that the underlying threat environment in Kashmir had not been fully neutralised even after six years of post-Pulwama policy adjustment.
Q: Was the Pulwama attack the deadliest on Indian security forces in Kashmir?
Yes. The Pulwama attack of February 14, 2019, with forty CRPF personnel killed in a single incident, was the deadliest attack on Indian security forces in Kashmir since the start of the insurgency in 1989. Earlier attacks had produced significant casualties: the 1999 Kargil conflict (a conventional military engagement rather than a terror attack) caused much larger losses; the 2002 Kaluchak attack killed thirty-one including soldiers and family members; the 2016 Uri attack killed nineteen Indian Army soldiers. None of the explicitly terror-attack incidents matched the Pulwama casualty figure in a single event. The combination of the suicide-vehicle-bombing methodology, the explosive payload size, and the convoy-bus targeting produced casualties that exceeded any previous terror attack in Kashmir.
Q: How did the post-Pulwama period reshape India’s strategic culture?
The post-Pulwama period reshaped Indian strategic culture across several dimensions. Public expectations regarding what an Indian government should do after a major Pakistan-linked attack shifted from the pre-2014 default of diplomatic protest to the post-2019 default of visible kinetic response. Political competition between national parties on national-security issues became more intense, with each party seeking to project credibility on the question of whether it would, in office, conduct similar or more extensive cross-border operations. Defence-academic institutions including the Indian Air Force’s training programmes, the Indian Army’s officer-education curricula, and civilian strategic-studies programmes incorporated the Pulwama-Balakot case as a foundational study. Media coverage frameworks shifted toward continuous-attention coverage of India-Pakistan crises, with cable news and social-media saturation becoming the operating environment for any future security crisis. The cumulative effect was a strategic culture by 2025 that approached the Pahalgam crisis with frameworks, expectations, and capabilities that had been substantially built in the post-Pulwama period, and that produced the Operation Sindoor response with markedly less institutional difficulty than the Balakot operation had presented six years earlier. The structural lesson, looking back from 2026, is that Pulwama-Balakot was not just a moment of policy adjustment but the beginning of a sustained reorganisation of how Indian national security operates, communicates, and decides.
