Eight days. That was the gap between the moment Prime Minister Narendra Modi stepped off a helicopter in Lahore on December 25, 2015, embracing his Pakistani counterpart Nawaz Sharif inside the Sharif family estate at Raiwind, and the moment four armed fighters in fatigues climbed over the perimeter wall of the Pathankot Air Force Station in the early hours of January 2, 2016. The Lahore visit was the boldest gesture any Indian prime minister had made toward Pakistan in over a decade. The airbase assault was the answer.

The four fighters belonged to Jaish-e-Mohammed, the organization Masood Azhar had built after India released him from Jammu’s Kot Bhalwal prison during the IC-814 hostage exchange at Kandahar in December 1999. Their target was not symbolic. The Pathankot Air Force Station houses MiG-21 Bison fighters, Mi-25 and Mi-35 attack helicopters, and the forward operating capability that defends India’s western flank against the Pakistani Punjab. By the time the seventeen-hour battle ended on the morning of January 3 and the residual combing operation closed on January 5, seven Indian security personnel were dead, more than thirty wounded, and the diplomatic opening Modi had pursued at Raiwind was structurally finished. India would still file paperwork, accept inspectors, demand action, and pretend for several more months that engagement remained possible. But the operational reality changed at Pathankot. The next time terrorists struck an Indian military target, at Uri in September 2016, India did not invite anyone to investigate. Indian special forces simply crossed the Line of Control nine days later and announced what they had done.

Pathankot is the article in this series where the strategic posture shifts. Every event after Pathankot, the Uri attack and the surgical strikes response, the Pulwama bombing and the Balakot airstrike, the Pahalgam massacre and Operation Sindoor, traces back to a question that crystallized at the Punjab airbase: what is the use of inviting Pakistan to investigate Pakistan? The answer, established conclusively when the Pakistani Joint Investigation Team returned home in late March 2016 after a five-day visit producing no actionable findings, was none. From that point onward, India’s counter-terror doctrine ran on two parallel tracks: the conventional military track that produced surgical strikes, Balakot, and Operation Sindoor; and the covert track of the systematic targeted-killing campaign that would eventually find Shahid Latif, the Pathankot mastermind, inside a mosque in Sialkot in October 2023.

This article reconstructs what happened across those seventeen hours at Pathankot, traces the infiltration corridor the attackers used to reach the perimeter, walks through the base defense battle, examines why the Indian security failures contributed to the casualty count alongside the JeM operational planning, analyzes the JIT visit Pakistan agreed to and then sabotaged, and explains why the strategic consequence dwarfed the tactical outcome. Seven security personnel died at Pathankot. The Indo-Pakistani diplomatic relationship died with them.

Background and Triggers

The setting that made Pathankot possible was built across several years of strategic miscalculation, diplomatic improvisation, and JeM patience. After the IC-814 hostage exchange released Masood Azhar at Kandahar on December 31, 1999, the freed cleric founded Jaish-e-Mohammed in Karachi within a month, with the explicit organizational goal of striking Indian targets. The 2001 Indian Parliament attack carried JeM’s signature, as did the 2002 Akshardham temple attack in Gandhinagar. JeM was banned in Pakistan in 2002 under American pressure following the 9/11 attacks, banned again in 2003 after the assassination attempts on General Pervez Musharraf, and then quietly reconstituted under different names while Azhar himself moved between Bahawalpur and Karachi, sheltered by what every Indian intelligence assessment described as the operational-control relationship between the founder of Jaish-e-Mohammed and Pakistan’s Inter-Services Intelligence directorate.

Through the 2000s, the focus of JeM’s external operations narrowed onto specific high-value Indian targets: military installations, security forces, and the Kashmir Valley’s recently raised counter-insurgency formations. The organization rebuilt its training infrastructure at the Markaz Subhan Allah complex outside Bahawalpur, expanded the seminary network in Punjab Province, and created cross-border handler cells in Sialkot, Narowal, and Shakargarh, the three Pakistani districts that share the international boundary with the Indian states of Punjab and Jammu. By 2015, JeM’s strike capability was as dense along the border as it had been at any point since 2001.

Modi’s surprise visit to Lahore on December 25, 2015 was unscheduled, unprecedented, and built on a small piece of personal diplomacy. The Indian prime minister had attended a regional summit in Kabul earlier that day, was returning to New Delhi via a stopover in Lahore that had been arranged on roughly two hours of advance notice, and chose to fly directly to the Sharif family estate at Jati Umra rather than receiving Sharif at the airport. The visit lasted under three hours. The two prime ministers exchanged gifts, watched a wedding in the Sharif household (Sharif’s granddaughter), discussed restarting the foreign-secretary level talks that had been frozen since 2014, and parted with the kind of public warmth that media on both sides interpreted as a possible breakthrough.

In Indian political circles, the response was mixed. Modi’s domestic critics accused the prime minister of personalizing diplomacy in a way that exceeded the formal mandate. Senior officials within the Ministry of External Affairs noted privately that the visit had not been preceded by the working-level preparation that usually attended state-to-state engagements. Within the BJP itself, there was visible discomfort about the speed of the move. Veteran diplomats including Shyam Saran, the former foreign secretary, were among those who flagged the structural gap: a personal-diplomacy gesture by one prime minister could not substitute for the institutional accountability framework needed to translate a thaw into actual policy. The gesture would have to be backed by Pakistani action against the terror groups that operated from Pakistani soil. Without that follow-through, the gesture would be exposed.

The exposure took eight days.

What is now established from the National Investigation Agency charge sheet filed in December 2016, the Punjab Police findings, and the operational reconstruction by Indian security forces is that JeM had been planning the Pathankot operation for several months before Modi’s Lahore visit. The infiltration route had been scouted across the border, the local Punjab logistical handler had been identified and recruited, and the assault team had been pre-staged on the Pakistani side at Sialkot. The Lahore visit did not trigger the attack. The attack was already loaded. The Lahore visit determined what the attack meant.

For Azhar and the JeM operational command, an Indian-Pakistani thaw was the worst strategic outcome conceivable. A JeM organization built around the politics of hostility against India required hostility to remain politically supported within Pakistan’s military establishment, financially sustainable through its donor networks in the Gulf and the diaspora, and ideologically coherent for its rank-and-file fighters. Reconciliation between Modi and Sharif would weaken every one of those dimensions. The Lahore visit, in JeM’s analysis, had to be punctured before the political momentum could consolidate. Pathankot was the puncture.

The Indian intelligence assessment that emerged in the months after the attack credits Azhar himself with the order, the JeM cross-border handler Shahid Latif with the operational plan, and a Punjab Province logistician network with the in-country support. Latif had returned to Pakistan in 2010 after a sixteen-year imprisonment in India for an earlier infiltration operation, settled in Sialkot, and become one of JeM’s most experienced cross-border planners. His specialty was launching small-team infiltrations across the agricultural belt that runs parallel to the international border, the same terrain JeM had used for Pakistani Punjab-to-Indian Punjab penetrations since the late 1990s. The Pathankot plan was Latif’s geographical specialty, executed against a strategic timing that the Lahore visit had created.

The four assault-team members were chosen for capability and for expendability. Three of them carried Pakistani identification, the fourth was unidentified by his actual name but later identified through forensic analysis as a Pakistani national. None had a public profile in Pakistan. None had been on any Indian watch list. The intent was clear: a deniable strike, executed by personnel whose sacrifice would not embarrass the organization or its sponsors, against a target whose strategic value justified the operational risk.

The selection of Pathankot itself reflected JeM’s geographic and strategic doctrine. The Pathankot Air Force Station sits in the Indian state of Punjab, fewer than fifty kilometers from the international boundary at its closest point. The base hosts not only fighter aircraft and attack helicopters but also a forward maintenance and dispersal capability that supports operations across the western air defense identification zone. A successful strike, even a partially successful one, would have damaged Indian air-power readiness in the sector that defends against Pakistani air incursions, embarrassed the Indian Air Force’s perimeter security architecture, and produced a casualty count high enough to dominate Indian media for weeks. The target met every JeM operational criterion: strategically significant, geographically reachable from Sialkot, defensively imperfect, and politically devastating in its symbolic dimensions. The choice was not opportunistic. It was the product of months of organizational planning that had selected the airbase from a roster of potential targets that JeM operational planners had been developing since at least 2014.

The Indian domestic political context that surrounded the Lahore visit had its own complications, beyond the diplomatic gambit Modi had pursued. The Indian National Congress, in opposition since the BJP’s 2014 election victory, had been critical of the Modi government’s Pakistan posture for being internally inconsistent: tough rhetoric in domestic political contexts, accommodating gestures in international ones. Senior Congress leaders, including former diplomats associated with the United Progressive Alliance period, had expressed skepticism about whether the Lahore visit would yield results without parallel pressure on the Pakistani military establishment. Within the BJP itself, the Sangh Parivar’s hardline elements were uncomfortable with what they saw as a softening of the government’s stance, and several internal voices urged the prime minister to add explicit conditions to any further engagement. The Lahore visit, in this context, was always politically fragile in India even before the Pathankot attack made the engagement track impossible. The eight-day timeline between the visit and the attack collapsed both the diplomatic experiment and the political space in which such experiments could be conducted.

The Pakistani domestic political context was equally fraught. Sharif’s Pakistan Muslim League-Nawaz government held nominal authority over Pakistani policy but operated within the structural constraints imposed by the Pakistani military establishment, which under General Raheel Sharif (no relation to the prime minister) maintained effective veto power over the country’s India policy. The Pakistani military’s strategic doctrine had not evolved to support a normalization track with India. The Inter-Services Intelligence directorate’s operational relationships with Jaish-e-Mohammed, Lashkar-e-Taiba, and Hizbul Mujahideen remained intact, and the institutional incentives to preserve those relationships ran directly counter to any genuine accountability framework that the civilian government might attempt to construct. When Modi flew to Lahore on December 25, the prime minister he met had limited capacity to deliver on whatever the conversation produced. When Pathankot occurred eight days later, the gap between Sharif’s nominal authority and his actual capacity to investigate JeM became visible.

The Infiltration Corridor and the Border Crossing

The geography of the Punjab border between India and Pakistan is unforgiving terrain for surveillance. The international boundary runs through flat agricultural land, intersected by the Ravi River, dotted with seasonal nullahs and tube-well infrastructure, and bisected by a chain-link fence that India built across the 1990s and into the 2000s. The fence is continuous in most segments, electrified in some, sensor-enabled in others, but interrupted in places where rivers cross or where local agricultural use predates the modern boundary. The infiltrators who reached Pathankot exploited one of those interruptions.

The reconstruction by Indian intelligence and the Border Security Force places the JeM team’s crossing point near the village of Bamiyal in Pathankot district, approximately three kilometers from the Ravi River and about thirty-five kilometers from the airbase itself. The crossing happened on the night of December 30 or the early hours of December 31, 2015. The exact crossing time has never been publicly established because the BSF surveillance footage from the relevant sector for the relevant night was, in the assessment that emerged later, either missing or inconclusive. The four operatives appear to have moved on foot, in pairs, across approximately one kilometer of open field, then transitioned to a pre-arranged transport pickup on a feeder road inside India.

The pickup was provided by an Indian-side handler whose identity has been redacted in the public NIA charge sheet but whose role is described in the Punjab Police findings: a local resident, recruited by the JeM cross-border network, with a vehicle large enough to carry four armed men plus their equipment. The handler drove the team from the border area toward Pathankot city through the late hours of December 31 and the early hours of January 1. The vehicle they used was a Mahindra XUV that the operatives later seized from Salwinder Singh, a senior superintendent of police in Punjab, after stopping his vehicle at gunpoint near Kolian village on the night of January 1.

The Salwinder Singh episode is one of the most contested facts of the Pathankot timeline. Singh, an SSP returning from a private religious site in the area, was traveling with two companions, his cook and a friend who was a jeweler. The four armed men stopped his vehicle, separated the three occupants, took possession of the SUV, and left Singh and his companions on the roadside with their lives intact. Singh reported the carjacking to local authorities later that morning. The decision by JeM operatives to leave a senior police officer alive after he had seen them at close range has been variously interpreted as operational discipline (no extra deaths, no extra noise), tactical incompetence (a senior officer let go is a senior officer who can describe you), or, in some Indian commentary that emerged later, evidence of more complex relationships within the broader Pathankot security picture that have never been conclusively established.

The carjacked SUV gave the JeM team what they needed: a vehicle with police credentials, in a region where police credentials open most checkpoints, on a route that ran directly toward the airbase. The team drove the SUV the remaining distance to the perimeter of the air force station through the early hours of January 2, abandoned it at a position near the perimeter wall, and entered the base on foot using a section of the boundary wall that was, in the post-incident analysis, neither fenced nor under continuous surveillance. The breach point was approximately two kilometers from the technical area of the base where the high-value aircraft were parked.

The infiltration corridor from Bamiyal to the perimeter wall covers approximately thirty-eight kilometers. Across that distance, the JeM team passed through territory that included three formal Punjab Police jurisdictions, two BSF sub-sectors, and an area of known Air Force Station perimeter responsibility. The team was visible at the Salwinder Singh stop, was driving a vehicle reported as carjacked by 5 a.m. on January 1, and was in the area of the airbase by the late hours of January 1. The Indian counter-mobilization in response to Singh’s report, including the dispatch of a search team from the airbase along with state and central police elements, did not locate the operatives before they crossed the perimeter wall.

Why the counter-mobilization failed has been examined in several reviews. Ajai Shukla, the defense correspondent and former Indian Army officer, argued in his post-incident analysis that the gap between Singh’s first report and the perimeter breach was sufficient time for an effective cordon-and-search operation, and that the failure to establish such a cordon reflected coordination problems among the Punjab Police, the National Security Guard, the BSF, and the Air Force base security elements rather than an absence of warning. Pravin Sawhney, the editor of Force magazine, made a related argument: that JeM’s cross-border operational capability from Sialkot had been documented in Indian intelligence reporting since at least 2012, that the geographic vulnerability of the Pathankot sector was a known concern, and that the defensive posture had not been adjusted to reflect the threat assessment. The combination of an under-fenced perimeter and a delayed counter-response gave the JeM team a window that should not have been available.

What is undisputed is that by the early hours of January 2, all four infiltrators had penetrated the airbase perimeter wall and entered the technical area of the air force station. The defenders had not yet established the cordon that would later contain them. The aircraft, helicopters, and ammunition stores that JeM had targeted were within the operational reach of the assault team for the first several hours of the engagement.

The forensic reconstruction of the cross-border movement, conducted by the National Investigation Agency through 2016, traced specific equipment recovered at the airbase to Pakistani-origin manufacturing and procurement. The AK-47 assault rifles carried by the operatives were of the variant in widespread circulation through Pakistani arms markets. The hand grenades and the explosive devices used by the team carried markings consistent with stockpiles sourced through the cross-border smuggling networks that JeM had cultivated for years. The communications equipment, while not advanced, included encrypted radios that had been provided to the team for coordination during the operation. The packaging and water bottles recovered from the operatives’ position carried Pakistani manufacturer labels and Urdu-language product information. The cumulative forensic record left no serious doubt about the operatives’ origin or their organizational affiliation.

Beyond the physical evidence, the intercepted communications between the four-man team and their handlers across the border provided the most operationally significant intelligence. The handler-side voices were identified by Indian intelligence as belonging to JeM personnel based in Sialkot and other Pakistani Punjab locations. The communications during the operation, captured by Indian signal-intelligence assets, included instructions to the team about target selection within the base, exhortations to maximize casualties, and discussions about the operational status as it evolved through the seventeen-hour engagement. The handler conversations would later become the central piece of evidence in the Indian intelligence case that the operation had been planned and directed from Pakistani territory by named JeM operational leaders, including Latif. The Pakistani JIT, when it visited in March 2016, was provided with the relevant communications records as part of the evidence package; the JIT did not contest the records but did not produce findings based on them either.

The Battle Inside the Base

The Pathankot Air Force Station occupies approximately 2,000 acres of operational and residential land along the Beas River, with its primary operational area in the southwestern quadrant and family quarters distributed across the eastern sectors. The technical area where the MiG-21 Bisons and the attack helicopters were parked sits inside multiple security perimeters: the outer boundary wall, an inner security ring around the runway and hangars, and the dispersed-aircraft revetments that protect individual airframes from blast damage. The JeM team, having breached the outer perimeter, faced the first inner ring as the base was stirring into pre-dawn alert.

The Indian response had begun before the attackers fired their first shot inside the base. Following the Salwinder Singh report and the recognition that armed infiltrators were almost certainly headed toward the airbase, the Defence Security Corps personnel responsible for the inner perimeter had been augmented, the Garud commando element of the Indian Air Force had been activated, and the National Security Guard had dispatched a counter-terrorism team from Manesar to Pathankot. By the time the JeM operatives engaged their first defenders, multiple defensive layers were deploying, but the deployment was not yet complete.

The first contact occurred at approximately 3:30 a.m. on January 2, 2016, when the four JeM fighters encountered a Defence Security Corps patrol near the residential area inside the base. The exchange of fire that followed killed Subedar Fateh Singh, a senior DSC member, and alerted the base’s emergency response system. The attackers split from a single team into two pairs in the next several minutes, presumably to confuse defenders about their numbers and to pursue separate sabotage objectives within the technical area.

The pair that moved toward the airmen’s accommodation and the family quarters area continued their assault through the morning. They engaged DSC personnel at multiple points, used hand grenades and AK-47 fire, and attempted to enter the technical area through a vehicle bay before being pinned down by counter-fire. By approximately 7 a.m., this pair had been cornered within the airmen’s accommodation building. The exchange of fire continued through the morning, with the NSG element now coordinating with the Garud commandos and the DSC to contain the operatives. Both members of this pair were killed by mid-morning.

The second pair moved deeper toward the technical area. Their objective, in the assessment that emerged later, was the dispersed-aircraft revetments where the MiG-21 Bisons and the helicopters were parked. They engaged base defenders across multiple sectors, attempted to reach the runway perimeter through a gap in the inner security ring, and were ultimately contained inside one of the technical-area buildings. The combat with this pair extended longer than with the first pair, in part because the team had reached an area where the use of heavy weapons by defenders risked damaging the aircraft they were trying to protect.

The casualties accumulated through the morning of January 2 and into January 3. Among the seven Indian security personnel killed: Subedar Fateh Singh of the DSC, killed in the first contact at the residential area; Lieutenant Colonel Niranjan Kumar of the National Security Guard, killed when an explosive device he was attempting to defuse on a body of one of the attackers detonated; Sergeant Khangkhanyam Kumar of the Garud commando element, killed during the assault on the technical area; Constable Kulwant Singh, Constable Jagdish Chand, and Subedar Major Fateh Singh of the DSC, killed during the perimeter battle; and Havildar Sanjeevan Singh, killed during the combing operation that followed the initial firefight. Multiple additional security personnel were wounded, several severely.

Lt. Col. Niranjan Kumar’s death was particularly painful for the NSG and for the Indian counter-terrorism community. An experienced bomb-disposal officer, Niranjan was attempting to disarm an explosive device strapped to one of the killed attackers when the device detonated, killing him along with three other NSG personnel near him. The post-incident review of the bomb-disposal failure became one of the most extensively studied operational lessons of the Pathankot battle: the use of suicide-belt or body-strapped explosives by a killed attacker as a delayed-action booby trap was a tactical innovation that the NSG had not previously encountered in this exact form on Indian soil. The lessons from Niranjan’s death directly shaped the bomb-disposal protocols used by the NSG in every subsequent counter-terror operation, including the operations during the Uri response and the post-Pulwama combing operations.

By the morning of January 3, both pairs of JeM operatives had been killed. The combing operation, however, extended through January 4 and into January 5. The base was treated as if additional infiltrators might be present, every accommodation block was searched, and the technical area was inspected for explosive devices that might have been planted during the first hours of the assault. The extended combing operation contributed to the high rounded death toll: not all of the Indian fatalities occurred during the active firefight; some occurred during the search-and-clear phase that followed, when the perceived threat level remained elevated and operational tempo remained high.

What the JeM operatives did not achieve at Pathankot is as significant as what they did. The MiG-21 Bisons, the Mi-25 attack helicopters, and the Mi-35 attack helicopters parked in the dispersed-aircraft revetments were not damaged. The fuel storage facilities were not breached. The ammunition depot was not reached. The radar and communications infrastructure was untouched. The strategic damage the operation was designed to inflict, the destruction of front-line air assets at a critical sector airbase, was prevented by the defensive containment that pinned the attackers in residential and accommodation areas before they could reach the airframes. From a strict operational standpoint, the Pathankot defenders prevented the catastrophic outcome despite the seven personnel killed.

The Indian narrative around Pathankot, in the weeks immediately after the engagement, oscillated between two readings of this tactical result. The first read the prevented destruction as evidence that the security architecture worked. The second read the perimeter breach itself, the seventeen-hour duration of the firefight, and the casualty count as evidence that the security architecture was substantially compromised. Both readings have merit. What both readings missed in the early days is the dimension that became dominant within several months: the strategic consequence at the diplomatic level was going to overshadow whatever the tactical balance sheet showed.

Several specific operational decisions during the engagement shaped the outcome in ways that received scrutiny in the post-incident reviews. The decision to deploy NSG personnel from Manesar by air, rather than to rely entirely on the Garud commandos and DSC elements already on site, reflected the assessment that the threat profile required specialist counter-terror capability. The decision was correct in principle but introduced a coordination challenge: the NSG team arrived during an active firefight, into a base whose internal layout they had limited prior familiarity with, and had to integrate into an already-running tactical engagement led by personnel of different services. The friction in this integration cost time during the morning of January 2, and the time loss had specific consequences in the subsequent containment of the second pair of attackers. Subsequent NSG deployment protocols were revised to reduce similar coordination problems in future incidents at military installations distant from the National Capital Region.

The use of helicopter air support during the engagement was another decision examined in the after-action reviews. Indian Air Force Mi-17 helicopters operated over the base during the day on January 2, providing aerial reconnaissance and command oversight of the firefight progression. The helicopters did not engage targets directly, given the proximity of friendly forces and the operational restriction on causing collateral damage to base infrastructure. The reconnaissance role nonetheless contributed to the situational awareness of the ground commanders, helped track the movements of the second JeM pair through the technical area, and provided communications relay between the various ground elements engaged in different sectors of the base. The successful integration of air and ground elements during the engagement became a model for subsequent counter-terror operations at military installations.

The medical and casualty evacuation capability deployed during the operation also received review. The wounded personnel, several with severe injuries, were evacuated initially to the Pathankot military hospital and subsequently to higher-level medical facilities at Jalandhar and Delhi. The evacuation process, conducted under conditions of ongoing operational activity at the base, demonstrated both the capability and the limits of the in-place medical response. Several of the wounded survived because of the rapid evacuation; several others died from injuries that might have been survivable with faster surgical intervention. The institutional learning from the medical-response dimension of the Pathankot operation contributed to the broader effort to upgrade military medical capabilities at forward operating stations, particularly the surgical capacity available within the first hour of an incident.

Key Figures

The cast of named individuals in the Pathankot story includes operational commanders, political leaders, security personnel, and the sequence of officials who managed the diplomatic response. Each shaped a part of the outcome.

Masood Azhar

The JeM founder, freed at Kandahar in December 1999, returned to Pakistan to build an organization explicitly oriented toward armed action against India. By 2015, Azhar had moved between Bahawalpur and other Punjab Province cities, was sheltered by Pakistani authorities despite being on multiple international designation lists, and exercised what Indian intelligence described as direct command authority over JeM’s external operations. The Indian assessment is that the Pathankot operation was authorized by Azhar personally, planned by his organizational lieutenants, and executed within JeM’s standard operational planning cycle. The post-incident UN designation effort that India pursued to add Azhar to the United Nations Security Council 1267 sanctions list was blocked at China’s behest until 2019, when sustained Indian and American pressure in the wake of the Pulwama attack finally moved the designation through. The Pakistani position, then and now, has been that Azhar’s exact whereabouts and operational status are unclear and that no actionable evidence linking him to specific attacks has been produced. The Indian position is that the evidentiary chain from the captured Pathankot operatives’ communications to Azhar’s command-and-control role is conclusive.

Shahid Latif

The Pathankot operational planner who would become the most consequential single name in the post-attack consequence chain. Latif had been imprisoned in India from 1994 to 2010 for an earlier JeM-affiliated infiltration operation, had returned to Pakistan after his release, and had become the JeM cross-border handler for Pakistani Punjab-to-Indian Punjab operations. His geographic specialty was the Sialkot-to-Indian-Punjab corridor that the Pathankot team used. His operational approach was small-team, deniable, expendable assets striking high-value Indian targets. He survived the Pathankot operation. He was identified by Indian intelligence within weeks. He became one of the highest-priority targets in the targeted-killing campaign that India would launch in the early 2020s. On October 11, 2023, masked gunmen entered a mosque in Daska, near Sialkot, where Latif was at morning prayers, and shot him along with two associates. The killers escaped on motorcycles. Pakistan registered a routine murder case. Indian intelligence considered the matter closed: the Pathankot mastermind had been reached, seven years and nine months after the attack he planned.

Narendra Modi

The Indian prime minister whose Lahore visit had produced the diplomatic opening that Pathankot was designed to close. Modi’s response to the attack was visibly restrained. The prime minister did not deliver immediate public statements, did not threaten military retaliation, and did not break off the diplomatic channels that had just been opened. Within forty-eight hours of the attack, the Ministry of External Affairs reached out to Pakistan with a request that Pakistani authorities investigate the JeM elements responsible. The decision to maintain the diplomatic channel rather than to escalate immediately was Modi’s, made over the objection of some advisors who pushed for a more aggressive public posture. The decision reflected what was at the time a calculated bet: that Pakistan would respond to a structured investigation request with at least minimal action against JeM, and that maintaining the diplomatic momentum from Raiwind would still be possible. The bet failed. Modi’s strategic learning from that failure is visible in every subsequent attack-response sequence: the Uri response was a military strike across the Line of Control nine days after the attack; the Pulwama response was the Balakot airstrike inside Pakistan thirteen days after the bombing; the Pahalgam response was Operation Sindoor, the missile-strike campaign across multiple Pakistani cities, fifteen days after the tourist massacre. The pattern shows a leader who once tested engagement and never tested it again.

Nawaz Sharif

The Pakistani prime minister at the time of both the Lahore visit and the Pathankot attack. Sharif’s personal diplomatic instincts had favored normalization with India, his political base in Punjab Province had economic reasons to support the Saarc-area engagement, and his civilian government had nominal authority to investigate JeM. None of those factors translated into actual accountability for Pathankot. The investigation Pakistani authorities conducted was managed not by Sharif’s civilian apparatus but by structures aligned with the Pakistani military and the ISI, who had every reason to protect JeM’s cross-border infrastructure from disruption. Sharif’s political weakness vis-a-vis the military establishment was visible in the Pathankot response: he could announce a Joint Investigation Team, but he could not actually investigate. The civilian-military gap in Pakistani decision-making, a structural feature of Pakistani politics since the 1980s, was the dimension that doomed the JIT process from the start.

The Joint Investigation Team

Pakistan announced the formation of a five-member Joint Investigation Team in March 2016, comprising representatives from the Inter-Services Intelligence directorate, the Intelligence Bureau, the Military Intelligence, the Counter-Terrorism Department of Punjab Province, and the Federal Investigation Agency. The team was led by Muhammad Tahir Rai of the Punjab Counter-Terrorism Department. Indian intelligence assessment of the team’s composition was that the inclusion of ISI representatives, alongside the absence of any independent civilian judicial element, predetermined the inquiry’s outcome. The JIT visited India from March 27 to April 1, 2016. The members were given a structured briefing at the airbase, taken to specific evidence locations, shown the recovered weapons and equipment, and provided with the NIA’s preliminary findings linking the operation to JeM. They returned to Pakistan with no acknowledgment of the JeM attribution, no commitment to prosecute named individuals, and ultimately no follow-through. By mid-2016, the JIT process was effectively defunct. By 2017, it had been formally suspended without producing any meaningful conclusions.

The Casualties

The seven security personnel killed at Pathankot represent the human reality that the strategic narrative often overshadows. Subedar Fateh Singh, the DSC member killed in the first contact, had been within months of his retirement after over thirty years of service. Lieutenant Colonel Niranjan Kumar, the NSG bomb-disposal officer, was thirty-four years old, married, with a young son. Sergeant Khangkhanyam Kumar of the Garud commandos was twenty-eight, from Manipur, and had been in the Air Force for eight years. The other four casualties spanned a range of services and ages. Their families received Indian government compensation, the men received posthumous honors, and the strategic consequence chain that flowed from their deaths produced, eventually, the elimination of the man who planned the operation. The operational closure does not bring the casualties back. It does not erase the seventeen hours their families spent following the news from Pathankot. The accounting of cost and consequence at this scale remains incomplete.

The JeM Cross-Border Architecture

Beyond the named individuals, the Pathankot operation depended on an organizational architecture that JeM had constructed across years of operational planning and that survived the attack itself largely intact. The architecture included recruitment cells in Pakistani Punjab madrassas, training facilities at Bahawalpur and at smaller dispersed locations across the province, handler networks specializing in different cross-border corridors (the Sialkot corridor for Indian Punjab targets, the Muzaffarabad corridor for Kashmir targets, the Karachi corridor for maritime infiltrations), logistical support chains that could move equipment and personnel across the border, and ideological-political infrastructure that maintained the recruitment pipeline and the donor network. The Pathankot operation drew on the Sialkot corridor architecture in particular, but the broader organizational architecture was the precondition for any specific operation’s feasibility. The Indian intelligence response, both during the post-Pathankot period and across the subsequent years, has aimed to disrupt this architecture rather than only to neutralize the individual operatives involved in any given attack. The disruption has been partial: the architecture has been damaged but not destroyed, and JeM continues to maintain operational capability even after the substantial costs imposed by the Sindoor strikes against Bahawalpur in May 2025. The continuing existence of the architecture, even in degraded form, is the structural reason the Indian counter-terror posture remains active rather than declared concluded.

Consequences and Impact

The immediate consequences of Pathankot were tactical. The base resumed full operations within days. The damaged infrastructure was repaired. The bodies of the four JeM operatives were photographed and cataloged. The forensic evidence, including weapons, equipment, communications devices, and documents, was sent to the National Investigation Agency for analysis. The NIA charge sheet that emerged in December 2016 named the JeM organization, Masood Azhar, Shahid Latif, and several other Pakistani-side conspirators as the operational planners.

The medium-term consequences shifted the diplomatic posture. India’s request for Pakistani investigation produced the JIT, the JIT visit produced no findings, and the visible failure of the Pakistani follow-through hardened Indian opinion against any further engagement. Within Indian policy circles, the period from January to August 2016 was the last sustained debate about whether engagement with Pakistan could yield results. By September 2016, when the Uri attack killed nineteen Indian soldiers, the debate was over. The surgical strikes that followed were executed without any diplomatic preliminary, without any inviting-Pakistan-to-investigate gesture, and without any announcement that India was seeking accountability through anything other than direct military action.

The long-term consequences are still unfolding. Pathankot established the pattern that has held since: India absorbs an attack, India builds a military or covert response, India executes that response without seeking Pakistani cooperation, and India treats Pakistani public denials as the expected output of the system rather than as facts requiring engagement. The pattern has produced Uri (attack September 2016, surgical strike response September 2016), Pulwama (attack February 2019, Balakot airstrike response February 2019), and Pahalgam (attack April 2025, Operation Sindoor response May 2025). Each iteration has compressed the response timeline and expanded the operational scope. The compression and expansion both trace back to the recognition that crystallized after the Pakistani JIT returned home empty-handed: there is no diplomatic process that will produce accountability, and so there is no strategic point in waiting for one.

Beyond the bilateral diplomatic track, Pathankot also reshaped India’s internal security architecture. The Defence Security Corps personnel who had borne the initial defensive burden at the base were augmented and re-equipped in the years that followed. The National Security Guard’s bomb-disposal protocols were redesigned around the lessons of Lt. Col. Niranjan’s death. The Air Force’s perimeter security across all forward operating bases was reviewed and upgraded, with particular attention paid to the gaps in the boundary fence and the surveillance coverage that had allowed the Pathankot infiltrators to penetrate. The Border Security Force’s deployment density along the Punjab sector of the international boundary was adjusted, with additional posts and additional sensor coverage in the corridors that JeM had used. Each of these improvements reflected the institutional learning from the seventeen-hour battle.

International consequences accumulated more slowly. The United States, which had been broadly supportive of the Modi-Sharif engagement track, recalibrated its public posture toward Pakistani counterterrorism failures in the months after Pathankot. The Trump administration that took office in January 2017 would later suspend security assistance to Pakistan in part on the grounds that Pakistani authorities had not taken adequate action against groups including Jaish-e-Mohammed, with Pathankot cited as one of the most visible recent examples. The United Nations process to designate Masood Azhar under the 1267 sanctions regime accelerated through 2018 and 2019, with American diplomats privately citing Pathankot in the consultations that preceded the designation. The international institutional response, slow and procedural, reinforced the bilateral lesson: Pakistani authorities were either unable or unwilling to deliver accountability for attacks emanating from their territory.

The financial and reputational costs to Pakistan accumulated through the Financial Action Task Force grey-list process that intensified through 2018 and 2019, and that placed Pakistan under sustained scrutiny over its terror-financing controls. While the FATF process was driven by multiple inputs, the Pathankot failure to investigate JeM credibly was one of the cited examples of Pakistan’s inadequate compliance with international counter-terrorism financing standards. The grey-listing carried real economic costs to Pakistan in terms of investor risk premiums, banking-sector compliance costs, and reduced access to international capital markets. Those costs accumulated over time and contributed to the macroeconomic pressures that constrained Pakistani policy choices through the late 2010s and into the 2020s.

For Jaish-e-Mohammed specifically, the medium-term consequences were mixed. The organization remained operational, the Bahawalpur infrastructure remained intact, and the cross-border handler network continued to function for several years. JeM would execute the Pulwama bombing in February 2019 using a similar operational architecture: a Pakistani-side handler, an Indian-side network, and a high-value military target. The Balakot airstrike in response to Pulwama, which struck a JeM training facility at Jaba in Khyber Pakhtunkhwa province, marked the first time India had bombed a target inside Pakistan since 1971, and it represented the first direct kinetic cost to JeM’s training infrastructure imposed by India in retaliation for an attack. The Operation Sindoor strikes of May 2025 went further, hitting the JeM headquarters complex at Bahawalpur directly. Across the trajectory from Pathankot to Sindoor, JeM moved from being a deniable irritant to being a target whose physical infrastructure was now within range of Indian missile and air strikes.

The shadow-war track imposed costs of a different kind. Shahid Latif was killed at Sialkot in October 2023. Other JeM operatives, named in the NIA Pathankot charge sheet, would meet similar ends across the years that followed. The pattern of the Pathankot-to-Pulwama elimination chain demonstrated that the consequences of attacks could reach back to specific individuals whose names appeared in Indian intelligence files. Those eliminations did not return Pakistan to the negotiating table, but they did impose individual-level costs on the JeM operational leadership that the organization had not previously faced.

Beyond the immediate organizational and individual consequences, Pathankot reshaped how Indian intelligence agencies organized their cross-border operational planning. The Research and Analysis Wing, which had historically focused on strategic-level intelligence collection rather than on direct kinetic operations, began through the post-Pathankot period to develop the integrated intelligence-and-operational capability that would eventually support the targeted-killing campaign. The integration of human intelligence sources within Pakistan with operational planning cells in India, the development of secure communications between handlers and operational assets, and the construction of the deniable operational architecture that would allow named JeM and LeT operatives to be reached without provoking conventional military escalation all proceeded across the years after Pathankot. The institutional capacity that crystallized in 2022 and 2023, when the targeted-killing campaign accelerated, had been under construction since the months immediately after the JIT’s failure.

The Pakistani institutional response to the post-Pathankot trajectory was largely defensive. The protection of senior JeM, LeT, and Hizbul figures was strengthened across the post-2016 period, with increased personal-security details, restricted public movement, and greater operational compartmentalization within the organizations. The institutional cost of these protective measures was significant: organizations that had previously operated openly, with senior leaders maintaining public profiles, recruiting at large rallies, and giving sermons at major mosques, were forced to retreat into more restrictive operational profiles. The transition was not complete; senior figures including Hafiz Saeed continued to maintain public profiles in some periods, with adjustments based on intelligence assessments of immediate threat levels. The cumulative effect, however, was to constrain the operational space within which Pakistani-based terror organizations could function, and that constraint imposed costs on their recruitment, training, and operational capacity that compounded over time.

The economic consequences for Pakistan, beyond the FATF-related costs, included the broader confidence effects on foreign direct investment, on Pakistani capital-market access, and on the country’s ability to attract international engagement on counter-terror cooperation. The post-Pathankot period saw progressive deterioration of these economic dimensions, with the underlying causation traceable to the cumulative pattern of Pakistani non-cooperation on attacks that India and the international community attributed to Pakistani-based groups. While the macroeconomic outcomes were determined by many factors beyond the counter-terror dimension, the counter-terror failures contributed to the constrained policy environment within which Pakistani economic decisions were made through the late 2010s and into the early 2020s. The cumulative cost has been substantial, even if no single decision can be attributed cleanly to the Pathankot precedent specifically.

Analytical Debate: Was the JIT Genuine or Engineered to Fail

The most contested analytical question about Pathankot is what to make of the JIT process. India invited the JIT. Pakistan agreed to send it. The JIT visited the airbase. The visit produced nothing. The question is whether that nothing was a genuine failure of investigative capacity, a deliberate sabotage by Pakistani authorities who had every reason to protect JeM, or, in the most cynical reading, an Indian gambit calculated to expose Pakistani bad faith for the international audience.

The genuine-failure reading argues that Pakistan in early 2016 lacked the institutional capacity to investigate JeM credibly even when its civilian leadership wanted to. The civilian-military gap in Pakistani policy meant that Sharif’s announcement of the JIT could not bind the ISI elements that actually controlled the relevant evidence. The ISI’s institutional interest in protecting JeM as an asset of Pakistani policy outweighed any diplomatic incentive Sharif could offer. The JIT was, on this reading, the best the civilian government could deliver, and what it could deliver was insufficient to produce a real investigation.

The deliberate-sabotage reading goes further. It argues that the JIT was designed from the start to fail, and that the failure was the actual Pakistani policy. The composition of the team, with ISI representation in a body nominally investigating ISI-linked entities, predetermined the outcome. The Pakistani decision to insist on access to the airbase, including to areas where Indian counter-evidence was held, was a tactical move to gather Indian counter-intelligence rather than to advance the inquiry. The JIT’s return without findings was not a failure but a success: Pakistan had performed the diplomatic gesture of sending the team, had produced the deniable claim that no actionable evidence was found, and had preserved JeM’s operational architecture intact. On this reading, Pakistan played the diplomatic game perfectly while protecting what it actually valued.

The Indian-gambit reading is more speculative. It suggests that the Modi government, recognizing that the JIT would likely fail, offered the JIT process precisely to ensure that the failure would be visible to the international community. The argument is that India needed a documented Pakistani non-response in order to build the international case for stronger measures, including the eventual UN designation of Masood Azhar and the FATF grey-listing. By making the JIT offer publicly, India placed Pakistan in a position where any failure would be diplomatically costly. The failure happened, the cost accumulated, and the long-term Indian strategic position improved. This reading credits Modi with significant strategic foresight; whether the actual decision-making rose to that level of calculation is debated.

Shyam Saran, the former Indian foreign secretary, offered a synthesis that draws elements from each reading. Saran’s view is that the JIT offer was genuine in the sense that India did want Pakistani action against JeM, that the offer was strategic in the sense that India recognized the failure would expose Pakistani non-cooperation, and that the failure was caused by Pakistan’s structural inability to investigate JeM credibly given the civilian-military balance. None of the three readings is fully wrong; the reality combined elements of all three. The Indian invitation was genuine; the Pakistani response was sabotaged; the resulting record served the long-term Indian case.

C. Raja Mohan, the strategic analyst, has framed the JIT episode within a broader argument about the diplomatic pivot from engagement to confrontation. Mohan’s analysis is that Pathankot revealed the structural impossibility of the Modi government’s initial Pakistan strategy: the assumption that bold personal diplomacy could create a thaw that would translate into Pakistani action against terror groups had been tested and disconfirmed within eight days. The JIT was the post-Lahore-visit attempt to salvage the engagement track. Its failure made the abandonment of engagement permanent. Mohan’s framing places Pathankot as the inflection point where Indian diplomacy toward Pakistan moved from incremental engagement to long-term confrontation, with the implementation of the new posture spread across the surgical strikes, Balakot, the shadow war, and Operation Sindoor.

Within Pakistani analytical commentary, the JIT process has been treated mostly as a successful diplomatic exercise. The argument from sympathetic Pakistani analysts is that Pakistan responded to a tragic incident with a structured investigation, the investigation found insufficient evidence to support the Indian attribution, and Pakistani authorities therefore had no basis to act against the named JeM individuals. The argument is, on its face, structurally sustainable; in practice, it requires accepting that an investigation conducted by ISI-affiliated bodies could find insufficient evidence against an organization the ISI has long been credibly accused of protecting. The Indian counter-argument is that the impossibility of an honest result was the entire reason the team’s composition was structured the way it was. The two readings are unlikely ever to converge.

A related debate concerns the Indian security failures that contributed to the casualty count. Should the analysis of Pathankot foreground the perimeter breach and the seventeen-hour duration of the firefight, framing the attack as a defensive failure that JeM exploited? Or should it foreground the prevented destruction of the high-value airframes, framing the attack as a defensive success that contained the operational damage? Both readings have merit. The Indian counter-terror community has, on balance, treated Pathankot as both: a defensive success in terms of asset protection, a defensive failure in terms of casualty prevention, and a procedural failure in terms of the gap between Salwinder Singh’s report and the perimeter cordon. The institutional learning across all three dimensions shaped the response architecture for every subsequent terror attack on a military target.

There is also a less-discussed analytical question about Modi’s Lahore visit itself: should the Indian decision to attempt the visit on roughly two hours of notice be treated as bold leadership that JeM disrupted, or as inadequately prepared diplomacy that exposed the prime minister to a predictable strategic counter-move? Some of Modi’s domestic critics have argued the latter, suggesting that a more carefully prepared engagement, with simultaneous demands for Pakistani action against JeM as a condition for further normalization, would have created a stronger framework for either accountability or controlled escalation if the framework failed. The defenders of the Lahore visit argue that no level of preparation could have prevented JeM’s attack, given that JeM’s strategic incentive to disrupt any thaw was independent of the specific format of the engagement. The two views may both be correct: a more prepared engagement might have produced a stronger record while still failing to prevent the attack.

What is no longer debated, in either Indian or international policy circles, is whether the engagement track that Modi attempted in December 2015 is a viable path forward. It is not. The Lahore visit was the last serious attempt to test it. Pathankot demonstrated why no further test would be made. The post-Pathankot Indian Pakistan policy has moved through a sequence of more confrontational postures, each of which has expanded the operational repertoire that India is willing to deploy and contracted the diplomatic space that Pakistan can exploit to defer accountability. The trajectory from Pathankot through Sindoor describes that progression in concrete terms.

A further analytical question concerns the role of the Indian-side handler in the operation. The presence of a domestic logistical handler, whose identity and role have been documented in the NIA charge sheet, raises questions about how JeM cross-border networks recruit and maintain Indian-side support. The handler in the Pathankot case was not a deep-cover operative but rather a local resident with a vehicle and access to transit routes through the Punjab countryside. The recruitment process appears to have involved a combination of ideological appeal, financial incentive, and personal-network connections to JeM-affiliated families with cross-border ties. The institutional response to this recruitment vector has involved both intelligence-led monitoring of vulnerable populations in border districts and broader counter-radicalization initiatives across Indian Punjab. The effectiveness of these measures has been mixed. The recruitment vector remains operational, even as the specific handler network used for Pathankot has been substantially disrupted by post-incident investigations and arrests.

A related debate concerns the broader counter-radicalization dimension. The cross-border infiltration that JeM executed against Pathankot relied on local Indian Punjab support that had ideological and operational dimensions. The Indian counter-radicalization framework that emerged in response, including expanded community engagement programs in border districts, intelligence-led identification of radicalized individuals, and prosecution of identified handlers, has produced mixed results. Some assessments credit the framework with substantially reducing the available pool of Indian-side handlers JeM could recruit; others argue that the framework operates at the margin while the underlying vulnerabilities (economic precarity, ideological appeal of radical Islamist discourse to a small subset of the population, family ties across the border) persist. The post-Pathankot decade has seen a gradual reduction in successful cross-border infiltrations relying on Indian-side handlers, but the reduction is partial rather than complete.

Why It Still Matters

Almost a decade after the seventeen-hour battle ended at Pathankot Air Force Station, the strategic architecture that the attack and the failed JIT process produced remains the operative framework for Indian Pakistan policy. Every subsequent attack-response sequence draws from the lessons that crystallized in the months after January 2016. Every Indian decision about whether to attempt diplomatic engagement, whether to share intelligence with Pakistan, whether to invite Pakistani cooperation in any form, references implicitly or explicitly the precedent that Pathankot established. The shadow war that India launched in the early 2020s, the open-war operations in Operation Sindoor, the comprehensive abandonment of engagement that followed Pahalgam and Sindoor, all reflect a posture whose foundational moment was the failed JIT visit of late March 2016.

The continuing relevance is visible in specific institutional changes that persist. The Indian Air Force’s perimeter security at forward operating stations has been redesigned across the post-Pathankot period, with attention to the boundary-wall vulnerabilities that the attackers exploited. The National Security Guard’s deployment posture has been adjusted to permit faster response to incidents beyond the National Capital Region. The Border Security Force has thickened its deployment along the Punjab sector of the international boundary. The defense intelligence apparatus has been reorganized to reduce the gaps between Punjab Police, BSF, and Air Force base security elements that the JeM team exploited in the hours before the perimeter breach. None of these changes was announced as a Pathankot response. All of them happened in the years after Pathankot, and all of them reflect the institutional learning from the failures the attack exposed.

The relevance also extends to the specific individuals whose names appeared in the Indian charge sheets and intelligence files. Latif’s killing in Sialkot in October 2023 reached a target whose connection to Pathankot was the central organizing principle of his selection. Other named JeM operatives have been the subjects of ongoing intelligence attention, with some eliminated in subsequent years and others still operational under tighter security constraints. The list of names from the Pathankot file has effectively become a long-term Indian targeting roster, with the seven-year gap between attack and Latif’s elimination establishing the rough timeframe within which Indian counter-terror agencies expect to reach high-priority targets. The subsequent timeline, with the broader pattern of mosque-based and other targeted eliminations that has accelerated since 2022, shows the Pathankot list being progressively crossed off.

For the Pakistani side, the continuing relevance of Pathankot is structural rather than tactical. The failed JIT process became the template for a recurring Pakistani approach: announce an investigation, conduct the investigation in a way that produces no findings, decline to prosecute, and rely on the gap between announcement and outcome to manage international pressure. The pattern repeated after Pulwama, after the 26/11 Mumbai investigation, after the various individual eliminations that India has been credibly linked to. Each iteration has further weakened Pakistan’s diplomatic credibility on counter-terrorism, reduced the international willingness to extend Pakistani authorities the benefit of the doubt, and accelerated the structural shifts (the FATF grey-listing, the UN 1267 designation of Azhar) that have constrained Pakistani policy options. The Pathankot template, perfectly executed in 2016, has produced compounding diplomatic costs that Pakistan continues to bear.

The strategic moral of Pathankot, for any future Indian leadership considering an opening with Pakistan, is the eight-day timeline. Eight days separated Modi’s Lahore visit from the perimeter breach. The compression of that timeline expressed something about the reliability of Pakistani non-state and quasi-state actors to disrupt any engagement track that threatens the institutional and economic architecture they depend on. Future Indian leaders will not be able to ignore that compression. Any new attempt at engagement will have to assume that the JeM, LeT, and Hizbul Mujahideen networks have the operational capability and political incentive to deliver another Pathankot within days of any thaw. The political cost to any Indian government of being humiliated again, the way the Modi government was humiliated in early 2016, is high enough that the engagement track is unlikely to be tested seriously for another generation.

For students of the broader India-Pakistan trajectory, Pathankot also serves as the moment when the asymmetry between Indian and Pakistani strategic options visibly tilted toward India. Before Pathankot, the relationship had been characterized by Pakistani escalation followed by Indian diplomatic appeals, with the operational asymmetry running against India. After Pathankot, and especially after Uri and Balakot, the asymmetry began to invert: Pakistani escalation was now followed by Indian operational action, and the operational asymmetry began to run against Pakistan. The conventional capabilities that India had accumulated through the 2009-2015 period of restraint (the precision-strike platforms, the special-forces capacity, the integrated intelligence picture) became deployable in a strategic posture that Pathankot helped crystallize. The accumulated capability met the political will at Pathankot. The combination has shaped every subsequent crisis.

The asymmetry shift that Pathankot helped crystallize has had implications beyond the immediate India-Pakistan relationship. Within South Asian strategic discourse, the post-Pathankot decade has produced a recognizable Indian strategic personality: confident in its capabilities, willing to bear the costs of unilateral action, skeptical of multilateral processes that rely on Pakistani cooperation, and prepared to escalate the operational ladder when provoked. The personality has its costs. Critics within India argue that the abandonment of engagement has reduced the diplomatic flexibility available for crisis management, that the reliance on military and covert tools has narrowed the policy options for de-escalation, and that the new posture has structural risks that were not present under the older framework. Defenders of the post-Pathankot posture argue that the older framework had failed to produce accountability, that engagement without accountability merely subsidized continuing attacks, and that the new posture has imposed costs on Pakistani-based terror infrastructure that the older framework never approached. Both positions have merit. The strategic personality that Pathankot helped construct will continue to be debated for as long as Indian counter-terror policy remains a topic of public discussion.

What Pathankot finally demonstrates, for the readers of this series who are tracing the long arc from IC-814 through to Sindoor, is the necessary connection between the conventional and covert tracks of Indian counter-terror policy. The conventional track, marked by the surgical strikes, Balakot, and Sindoor, imposes immediate and visible costs on Pakistani military and terror infrastructure. The covert track, marked by the elimination of Latif and dozens of other operatives across Pakistani cities, imposes individual-level and long-term costs on the operational leaders who plan and execute attacks. Neither track alone would have produced the strategic shift that the post-Pathankot decade has produced. Together, they have created a pressure environment that Pakistani authorities and Pakistani-based terror organizations now have to navigate continuously, with the threat of consequence no longer something they can dismiss as the empty rhetoric of an Indian government that talks but does not act. Pathankot was the moment that talk visibly failed. Everything since has been the construction of the alternative.

The final dimension of Pathankot’s continuing relevance concerns its role as a reference point in the public discourse around Indian counter-terror policy. Within the Indian political conversation, Pathankot is invoked regularly as the moment when the limits of engagement became visible. Within the Pakistani political conversation, Pathankot is largely avoided, given that any honest examination of the JIT failure exposes the structural problem in Pakistani counter-terror capacity. Within the international policy community, Pathankot is cited frequently in analytical and policy work on safe havens, on counter-terror cooperation between adversarial states, and on the conditions under which targeted-killing programs become politically and operationally necessary. The article in this series that traces the broader chain of attacks places Pathankot at the inflection point where the chain shifts from being primarily a Pakistani offensive against Indian targets to being a sequence of Pakistani attacks followed by progressively more aggressive Indian responses. The framing matters because it shapes how future Indian and Pakistani decision-makers understand the available strategic options.

The reference function extends beyond the bilateral context. Pathankot has been cited in policy work on counter-terror cooperation in other adversarial-state contexts: the United States and Iran, India and China in their disputed-border framework, and the various sub-state conflicts where targeted-killing campaigns have been considered or executed. The structural parallels are imperfect, but the analytical lesson is portable: when institutional channels for cross-border counter-terror cooperation fail, the policy alternatives narrow toward unilateral action. The conditions under which such action becomes operationally viable, politically sustainable, and strategically successful are the conditions Pathankot helped clarify for India. Other states facing similar strategic configurations now have a documented case study to consult. The case study points consistently toward the conclusion that engagement cannot be sustained without accountability, that accountability cannot be extracted from institutionally compromised counter-parties, and that unilateral action becomes necessary when the alternatives have been exhausted. The Pathankot trajectory has documented that conclusion in operational and political detail across the past decade.

Frequently Asked Questions

Q: What happened at the Pathankot airbase attack?

In the early morning hours of January 2, 2016, four armed fighters belonging to Jaish-e-Mohammed breached the perimeter of the Pathankot Air Force Station in Punjab, India. The attackers used a stolen police-marked SUV to approach the base, climbed over a section of the boundary wall, and engaged Indian security personnel in a battle that lasted approximately seventeen hours through January 3, with the combing operation extending into January 4 and 5. The attackers were killed by Indian security forces. Seven Indian security personnel were killed in the engagement, including DSC members, an NSG bomb-disposal officer, and Garud commandos. The high-value aircraft and helicopters at the base were not damaged. The attack came eight days after Indian Prime Minister Narendra Modi’s surprise visit to Lahore to meet Pakistani Prime Minister Nawaz Sharif, and it directly disrupted the diplomatic opening that the visit had created.

Q: How did JeM terrorists infiltrate the Pathankot airbase?

The JeM operational team crossed the international border between Pakistan and India near the village of Bamiyal in Pathankot district on the night of December 30 or early hours of December 31, 2015. They moved on foot across approximately one kilometer of agricultural land, then transitioned to a vehicle pickup arranged by an Indian-side handler. The team carjacked an SUV from a Punjab Police senior superintendent named Salwinder Singh near Kolian village on the night of January 1, drove the stolen vehicle to the perimeter of the airbase, abandoned it near the boundary wall, and entered the base on foot through a section of the perimeter that was neither continuously fenced nor under surveillance. The infiltration corridor covered approximately thirty-eight kilometers from the border crossing to the perimeter breach. The JeM cross-border handler responsible for planning the operation was Shahid Latif, who was based in Sialkot and specialized in launching small-team infiltrations across the agricultural belt parallel to the international border.

Q: How many security personnel were killed at Pathankot?

Seven Indian security personnel were killed in the Pathankot engagement, with multiple additional personnel wounded. The fatalities included Subedar Fateh Singh of the Defence Security Corps, killed in the first contact at the residential area; Lieutenant Colonel Niranjan Kumar of the National Security Guard, killed when an explosive device he was attempting to defuse on a killed attacker’s body detonated; Sergeant Khangkhanyam Kumar of the Garud commando element of the Indian Air Force; Constable Kulwant Singh, Constable Jagdish Chand, Subedar Major Fateh Singh of the DSC; and Havildar Sanjeevan Singh, killed during the combing operation that followed the initial firefight. All four JeM attackers were also killed during the engagement. The seven Indian fatalities became the focal point of the post-incident institutional review, particularly the death of Lt. Col. Niranjan, which led to a redesign of NSG bomb-disposal protocols.

Q: Who masterminded the Pathankot attack?

Indian intelligence has identified Shahid Latif, a JeM cross-border handler based in Sialkot, Pakistan, as the operational mastermind of the Pathankot attack. The attribution is supported by intercepted communications, evidence recovered from the killed attackers, and handler-relationship analysis from Indian intelligence sources. Above Latif, the Indian assessment names JeM founder Masood Azhar as the authorizing authority, with Azhar exercising direct command over the organization’s external operations from his location in Pakistani Punjab Province. Pakistani authorities did not accept the Indian attribution, did not arrest Latif, and did not prosecute Azhar. Latif remained operational in Pakistan until October 11, 2023, when masked gunmen shot him inside a mosque in Daska, near Sialkot. The seven-year-and-nine-month gap between the Pathankot attack and Latif’s killing illustrates the long timeline within which Indian counter-terror agencies pursue high-priority targets.

Q: Why did India invite a Pakistani JIT after Pathankot?

The Modi government’s decision to invite a Pakistani Joint Investigation Team to visit the Pathankot airbase reflected the residual hope, at the moment of the Lahore visit’s diplomatic opening, that bilateral cooperation on terrorism could be salvaged from the attack. The structured investigation framework was offered as a test: if Pakistani authorities responded with genuine investigation and prosecution, the engagement track that Modi had begun could be sustained. The decision was made over objections from some Indian advisors who pushed for a more aggressive public posture. The JIT visited from March 27 to April 1, 2016, was given access to evidence and briefings at the airbase, and returned to Pakistan without producing actionable findings or commitments to prosecute named individuals. The failed visit confirmed for Indian decision-makers that bilateral counter-terror cooperation through Pakistani institutional channels was structurally impossible, given the civilian-military gap in Pakistani policy and the ISI’s institutional interest in protecting JeM. After Pathankot, India did not invite Pakistani cooperation again on any subsequent terror incident.

Q: Did the Pakistani investigation produce results?

The Pakistani Joint Investigation Team visit to India in late March 2016 produced no actionable findings. The five-member team, led by Muhammad Tahir Rai of the Punjab Counter-Terrorism Department and including representatives from the ISI, Military Intelligence, Intelligence Bureau, and the Federal Investigation Agency, returned to Pakistan without acknowledging the JeM attribution, without committing to prosecute named individuals, and without taking institutional action against JeM or its leaders. By mid-2016, the JIT process was effectively defunct, and by 2017 it had been formally suspended. Indian intelligence assessment is that the JIT’s composition predetermined this outcome: the inclusion of ISI representatives, in a body nominally investigating ISI-linked entities, made an honest result impossible. Pakistani official commentary has framed the absence of findings as a legitimate evidentiary outcome rather than as a sabotaged investigation, but the Indian and international consensus is that the JIT was structurally designed to fail. The failure became a template for subsequent Pakistani responses to terror investigations, including after Pulwama in 2019.

Q: How did Pathankot change India-Pakistan relations?

Pathankot ended India’s last serious attempt at engagement-based normalization with Pakistan. Before the attack, the Modi government had pursued a calibrated opening, marked by the Lahore visit and accompanied by working-level discussions about restarting foreign-secretary-level talks. After Pathankot and the failed JIT process, India did not initiate any further diplomatic opening for the rest of the Modi-Sharif period, did not respond positively to subsequent Pakistani gestures, and adopted a posture that treated Pakistani offers of cooperation with consistent skepticism. The structural shift hardened across subsequent attacks: the Uri response in September 2016 was a unilateral surgical strike across the Line of Control without any diplomatic preliminary; the Pulwama response in February 2019 was the Balakot airstrike inside Pakistan; the Pahalgam response in May 2025 was Operation Sindoor, the missile-strike campaign against multiple Pakistani cities. Each iteration moved further from any engagement framework. The post-Pahalgam Indian declaration that talks would not resume until terrorism stops formalized what had been operational reality since Pathankot.

Q: What was PM Modi’s Lahore visit and how does it connect?

On December 25, 2015, Indian Prime Minister Narendra Modi made a surprise visit to Lahore, Pakistan, to meet his Pakistani counterpart Nawaz Sharif. The visit was unscheduled, arranged on roughly two hours of advance notice, and conducted at the Sharif family estate at Jati Umra in Raiwind. Modi attended a wedding in the Sharif household, exchanged gifts with the Pakistani prime minister, and discussed restarting foreign-secretary-level dialogue that had been frozen since 2014. The visit lasted under three hours and was widely interpreted in both Indian and Pakistani media as a significant diplomatic gesture that could presage a thaw in bilateral relations. The Pathankot attack occurred eight days later, on January 2, 2016. The compressed timeline between the Lahore visit and the airbase assault has been read by Indian analysts as JeM’s deliberate disruption of the diplomatic opening: the organization’s strategic interest in Indo-Pakistani hostility was fundamentally threatened by any normalization, and the Pathankot operation, which had been planned for months before the Lahore visit, was triggered to fully neutralize the political momentum that the visit had created. The connection between the visit and the attack is the central explanation for why Pathankot’s diplomatic consequences exceeded its tactical scale.

Q: How long did the Pathankot battle last?

The active firefight at the Pathankot Air Force Station lasted approximately seventeen hours, beginning with the first contact at around 3:30 a.m. on January 2, 2016, and continuing into the morning of January 3 when the last of the four JeM attackers was killed. The combing operation that followed the active firefight extended through January 4 and into January 5, as Indian security forces inspected every accommodation block and area of the technical zone for additional infiltrators or planted explosive devices. The full operation, including the post-firefight clearance, spanned approximately three full days. The extended duration of the operation, well beyond the time it took to neutralize the four attackers, contributed to several of the casualties: Lt. Col. Niranjan’s death occurred during the post-firefight defusing operation rather than during the active engagement. The seventeen-hour primary firefight became one of the longest counter-terror operations on Indian military soil since the 2008 Mumbai attacks, and the institutional review of the duration shaped subsequent counter-terror response protocols across the Indian armed forces.

Q: Were the high-value aircraft at Pathankot damaged?

No. The MiG-21 Bison fighter aircraft, the Mi-25 attack helicopters, and the Mi-35 attack helicopters parked in the dispersed-aircraft revetments of the Pathankot Air Force Station were not damaged in the attack. The defensive containment of the JeM team, which pinned the attackers in residential and accommodation areas before they could reach the inner technical zone where the aircraft were parked, prevented the strategic damage the operation was designed to inflict. Fuel storage facilities, ammunition depots, radar infrastructure, and communications systems were also untouched. From a strict operational standpoint, the prevention of catastrophic damage to high-value air assets was the most significant defensive success of the engagement. The success was achieved at the cost of seven Indian security personnel killed and over thirty wounded. The trade-off, while painful, has been treated by Indian counter-terror analysts as a defensive outcome that prevented a substantially worse strategic catastrophe.

Q: How did Pathankot lead to the surgical strikes?

Pathankot did not directly produce the surgical strikes of September 2016, but it produced the strategic framework within which the surgical strikes became possible. The failure of the Pakistani JIT process between January and April 2016 demonstrated to Indian decision-makers that diplomatic engagement following terror attacks would not produce accountability. When the Uri attack killed nineteen Indian soldiers on September 18, 2016, the Modi government did not repeat the JIT-invitation process. Instead, Indian special forces crossed the Line of Control on September 29, 2016, struck JeM and LeT launch pads in Pakistan-occupied Kashmir, and returned without significant casualties. The decision to execute the surgical strikes rather than to seek diplomatic redress was the direct strategic consequence of the Pathankot lesson: that diplomatic redress was a path that produced no result. Indian Director General of Military Operations Lt. Gen. Ranbir Singh’s announcement of the strikes the following day was the public confirmation of the new doctrine. Without Pathankot’s preceding demonstration that engagement was structurally impossible, the political space for the surgical-strikes decision would not have existed.

Q: What happened to Shahid Latif, the Pathankot mastermind?

Shahid Latif, the JeM cross-border handler identified by Indian intelligence as the operational planner of the Pathankot attack, was killed on October 11, 2023, inside the Mosque of Allama Iqbal in Daska, near Sialkot, Pakistan. Two masked gunmen entered the mosque while Latif was at morning prayers, opened fire, killed Latif and two associates, and escaped on motorcycles. Pakistani authorities registered a routine murder investigation and did not produce any prosecution. Indian counter-terror agencies treated the killing as the closure of one of the most significant cases on the Pathankot file. The seven-year-and-nine-month gap between the airbase attack and Latif’s elimination establishes the timeframe within which Indian intelligence pursued high-priority targets in Pakistan. Latif’s death is part of the broader pattern of mosque-based eliminations that has marked the targeted-killing campaign since 2022, and it represents the most direct individual-level consequence the Pathankot attack produced.

Q: Did India have intelligence warning before the Pathankot attack?

Yes, partially. Indian intelligence had been tracking JeM cross-border infiltration capability from the Sialkot sector for years before Pathankot, and specific assessments warning of a potential strike on military installations in the Punjab corridor had been circulated within the Indian counter-terror community in late 2015. The geographic vulnerability of the Pathankot airbase, with its under-fenced perimeter and proximity to the international border, was a documented concern. What the available intelligence did not include was specific prior warning of the date, time, or exact target of the January 2 attack. The Salwinder Singh carjacking on the night of January 1, which provided the most specific real-time warning that armed infiltrators were heading toward the Pathankot area, did trigger a counter-mobilization, but the cordon was not established before the operatives reached the perimeter. Pravin Sawhney has argued that the gap between general threat awareness and specific tactical warning was structural rather than coincidental, reflecting the limits of Indian intelligence collection against JeM operational planning conducted within Pakistani territory. The Singh report itself remains one of the most contested elements of the timeline, with debates continuing over how the counter-mobilization could have been faster.

Q: Was the Salwinder Singh carjacking suspicious?

The carjacking of Punjab Police Senior Superintendent Salwinder Singh by the four JeM operatives on the night of January 1, 2016, has been one of the most-debated elements of the Pathankot timeline. Singh was returning from a private religious site in the Pathankot area with two companions, his cook and a friend who was a jeweler. The four armed fighters stopped his Mahindra XUV at gunpoint near Kolian village, separated the three occupants, took possession of the vehicle, and left the three men on the roadside with their lives intact. Singh reported the incident to local authorities later that morning. The decision by JeM operatives to leave a senior police officer alive after he had seen them at close range has been variously interpreted as operational discipline, tactical incompetence, or, in some Indian commentary, evidence of more complex relationships within the broader Pathankot security picture. Subsequent investigations did not produce evidence of any pre-existing relationship between Singh and the attackers, and Indian authorities concluded that the carjacking was an opportunistic acquisition of a police-marked vehicle by the JeM team. The episode nonetheless contributed to the institutional review of how rapidly counter-mobilization can respond to specific tactical warnings.

Q: How does Pathankot connect to the broader India-Pakistan trajectory?

Pathankot occupies a pivotal position in the twenty-six-year arc from IC-814 in 1999 through to Operation Sindoor in 2025. Before Pathankot, the Modi government had attempted to test whether engagement-based normalization with Pakistan could yield results despite the structural problem of Pakistani-based terror groups. After Pathankot and the failed JIT process, India abandoned the engagement track and constructed the parallel conventional and covert response framework that has defined its counter-terror posture ever since. The conventional track produced the surgical strikes of 2016, the Balakot airstrike of 2019, and Operation Sindoor of 2025. The covert track produced the targeted-killing campaign that has eliminated dozens of named JeM, LeT, and Hizbul Mujahideen operatives across Pakistani cities, including Latif at Sialkot in 2023. Pathankot is the moment when both tracks became necessary and possible. Before Pathankot, the political space for either track was constrained by the engagement attempt; after Pathankot, both tracks could be developed and deployed without further internal opposition from advocates of engagement. The strategic infrastructure that India has used in every subsequent crisis was, in effect, designed in the post-Pathankot period.

Q: What was the international response to Pathankot?

The international response to Pathankot was initially measured, given the prevailing diplomatic context of the Modi-Sharif engagement attempt and the international interest in supporting any Indo-Pakistani thaw. Several Western governments expressed condolences for the Indian casualties and called for Pakistani investigation. The United States position evolved through 2016, with growing official skepticism about Pakistani counter-terror commitment as the JIT process produced no findings. By 2017, with the new Trump administration adopting a more confrontational posture toward Pakistani non-cooperation, the international framing had shifted. The UN process to designate Masood Azhar under the 1267 sanctions regime, blocked by China through several rounds of consideration, ultimately succeeded in May 2019, after the Pulwama attack provided the renewed momentum that Pathankot alone had not generated. The Financial Action Task Force grey-listing of Pakistan, which intensified through 2018 and 2019, cited Pakistani failures on JeM and LeT enforcement, with Pathankot among the cited examples. The accumulated international pressure across the post-Pathankot period contributed to the structural costs Pakistan now bears in capital markets and diplomatic standing.

Q: Did Pakistan ever prosecute anyone for Pathankot?

No. Despite the announcement of the Joint Investigation Team in March 2016, the JIT visit to India, and the access provided by Indian authorities to evidence and the airbase site, Pakistani authorities did not prosecute any named individual for the Pathankot attack. The JeM members named in the Indian National Investigation Agency charge sheet, including Masood Azhar and Shahid Latif, were not arrested in Pakistan, were not subjected to formal investigation by Pakistani prosecutorial authorities, and were not prevented from continuing their activities. The absence of Pakistani prosecution despite the formal cooperation framework was the central evidence of the JIT’s failure. Pakistan’s official position has been that Indian evidence was insufficient to support prosecution under Pakistani standards. The Indian counter-position is that the standards were structurally unmeetable given the civilian-military gap in Pakistani policy and the ISI’s institutional protection of JeM. Pakistani non-prosecution of Pathankot has become one of the most-cited cases in the international record of Pakistani failures on counter-terror cooperation, and it shaped subsequent international expectations about what Pakistani institutions would or would not deliver.

Q: What lessons did India’s security forces learn from Pathankot?

The institutional learning from Pathankot reshaped Indian counter-terror response architecture across multiple dimensions. The Indian Air Force redesigned perimeter security at forward operating stations, with particular attention to the boundary-wall vulnerabilities that the JeM team exploited, the surveillance gaps at the Bamiyal sector, and the coordination problems between airbase security elements and Punjab Police. The Defence Security Corps was augmented and re-equipped, with increased manning levels and upgraded weapons. The National Security Guard restructured its bomb-disposal protocols around the lessons of Lt. Col. Niranjan Kumar’s death from the booby-trapped attacker’s body, with new procedures for handling dead operatives’ bodies that have been cited as having prevented similar losses in subsequent operations. The Border Security Force adjusted its deployment density along the Punjab sector of the international boundary, adding posts and sensor coverage in the corridors JeM used. The integrated intelligence picture across Punjab Police, BSF, Air Force base security, and the Intelligence Bureau was strengthened to reduce the gaps in real-time threat sharing that the Salwinder Singh report had exposed. The cumulative institutional changes across all of these dimensions have shaped every subsequent terror incident on Indian military or paramilitary targets, and they reflect the depth of the operational lessons that the seventeen-hour engagement at Pathankot generated.

Q: Could a Pathankot-style attack happen again?

The threat of a Pathankot-style attack against an Indian military installation has been substantially reduced but not eliminated. The structural changes implemented since 2016, including improved perimeter security at forward operating bases, faster counter-mobilization protocols, denser deployment along the Punjab and Jammu sectors of the international boundary, and the targeted-killing campaign that has eliminated multiple JeM and LeT operatives responsible for cross-border planning, have substantially raised the operational bar for any future infiltration. The JeM and LeT organizations themselves have absorbed sustained operational and leadership-level costs across the post-Pathankot decade, with multiple senior planners eliminated and their cross-border architectures disrupted. At the same time, the underlying motivation for such operations has not disappeared: the Pakistani strategic interest in maintaining Indo-Pakistani hostility, the operational interest of JeM and LeT in continued relevance, and the geographic vulnerability of military installations close to the international boundary all remain. The post-Pahalgam shift, in which Pakistan-based groups have continued operations despite the demonstrated Indian willingness to respond with conventional military strikes, suggests that the threat persists at a reduced operational tempo. The Indian counter-terror architecture is now designed to absorb such attacks faster, contain them more effectively, and respond more decisively, but a future Pathankot-style attempt cannot be definitively ruled out.

Q: Why does Pathankot matter for understanding the shadow war?

Pathankot matters for the shadow war narrative because it produced the strategic framework within which the campaign of targeted eliminations of Pakistani-based terror operatives became politically and operationally possible. Before Pathankot, the Indian assumption was that diplomatic and institutional channels could deliver accountability for cross-border terror attacks. The Pakistani JIT process disproved that assumption. After Pathankot, the question facing Indian decision-makers was: if institutional channels do not deliver accountability, what does? The shadow-war answer, developed across the late 2010s and operationalized in the early 2020s, was that individual-level accountability could be imposed directly on the operational planners and commanders, irrespective of whether Pakistani institutions chose to act. The killing of Shahid Latif at Sialkot in October 2023 is the direct realization of that answer, applied to the specific Pathankot case. The broader pattern of similar eliminations across multiple Pakistani cities, targeting operatives from JeM, Lashkar-e-Taiba, Hizbul Mujahideen, and Khalistani separatist organizations, represents the systematic application of the lesson that Pathankot taught. The shadow war is, in effect, the operational answer to the question that the failed JIT posed: how do you impose consequences when the institutions that should impose them refuse?

Q: How has Pathankot been remembered and commemorated?

The seven security personnel killed at Pathankot have been honored through the standard Indian armed forces commemoration practices: posthumous gallantry awards, family compensation, and inclusion in the broader memorial framework for personnel killed in counter-terror operations. Lt. Col. Niranjan Kumar received the Shaurya Chakra posthumously in 2016. Subedar Fateh Singh and other DSC fatalities received gallantry recognitions appropriate to their actions in the engagement. Sergeant Khangkhanyam Kumar of the Garud commandos received commemoration within the Indian Air Force’s tradition for personnel killed in special-operations engagements. The Pathankot Air Force Station itself continues to operate, with the technical area, the residential quarters, and the perimeter all reconstructed and reinforced after the attack. Annual commemorations on January 2 mark the anniversary within the Indian military community. Beyond the formal commemoration, the operational lessons of the engagement remain embedded in the training curricula of the NSG, the Garud commando element, and the various armed forces counter-terror units. The institutional memory of Pathankot, both the loss and the lessons, continues to shape Indian counter-terror practice almost a decade after the seventeen-hour battle ended.

Q: What is the relationship between Pathankot and the Bahawalpur strike during Operation Sindoor?

During Operation Sindoor in May 2025, Indian missile strikes hit the Jaish-e-Mohammed headquarters complex at Bahawalpur, the Pakistani Punjab city that has hosted JeM’s operational and ideological infrastructure since the early 2000s. The Bahawalpur strike was one of the most significant individual operations within the broader Sindoor campaign, and it reflected a direct line of strategic logic from Pathankot. The Pathankot attack had been ordered by the JeM command structure in Bahawalpur, planned by the cross-border handler network in Sialkot, and executed by JeM fighters. The Pakistani institutional refusal to act against Bahawalpur infrastructure across the post-Pathankot period meant that the structures that had produced Pathankot remained intact and continued producing subsequent attacks, including Pulwama and Pahalgam. The Sindoor decision to strike Bahawalpur directly represents the closing of a strategic loop: the Indian conventional military capability that had been developed across the post-Pathankot period was finally applied against the source infrastructure that the Pakistani institutional process had refused to disturb. The Bahawalpur strike was, in effect, the Indian alternative to the prosecution that Pakistan never delivered. The strategic logic that connects Pathankot in January 2016 to Bahawalpur in May 2025 is the central thread of the Indian counter-terror evolution across that decade, and it explains why the consequences of the seventeen-hour battle at Pathankot continue to unfold long after the event itself has receded into history. The continuing salience of the Pathankot precedent in subsequent strategic decisions confirms its place as one of the most consequential single attacks in the entire post-1999 India-Pakistan trajectory, even though its direct casualty count was small relative to attacks like 26/11 Mumbai or the Pulwama bombing.