At 0400 hours Indian Standard Time on May 7, 2025, Rafale jets of the Indian Air Force released SCALP cruise missiles into Pakistani airspace, initiating the most consequential twenty-three minutes in South Asian military history since the fall of Dhaka in December 1971. Nine targets across Pakistan-administered Kashmir and Pakistan’s Punjab province received precision munitions in rapid succession, each strike calibrated to dismantle infrastructure belonging to Jaish-e-Mohammed, Lashkar-e-Taiba, and Hizbul Mujahideen. By the time the final weapon found its mark, India had crossed every remaining conventional military threshold with its nuclear-armed neighbor: first missile strikes on Pakistani soil proper, first multi-target simultaneous campaign, first combat deployment of the Rafale platform, and first use of SCALP cruise missiles in South Asian airspace. Those twenty-three minutes did not merely punish the perpetrators of the Pahalgam massacre. They permanently altered the strategic geography of the subcontinent.

Background and Triggers

The road to those twenty-three minutes began fifteen days earlier, on April 22, 2025, in the meadows of Baisaran Valley near Pahalgam in Indian-administered Jammu and Kashmir. Five gunmen opened fire on a group of tourists, killing twenty-six civilians, including twenty-five Indian nationals and one Nepali citizen. The attackers reportedly checked victims’ religious identities before shooting, targeting Hindu and Christian tourists while sparing Muslim locals. The Resistance Front, a proxy organization linked to Lashkar-e-Taiba, initially claimed responsibility through a social media post before retracting the claim and blaming hackers for the message. That retraction convinced almost no one. The specificity of the initial claim, including operational details that only participants could have known, made the hacking explanation functionally impossible to sustain.

India’s response unfolded across fourteen meticulously calibrated days of diplomatic, economic, and military escalation. New Delhi suspended the Indus Waters Treaty’s most-favored-nation provisions, expelled Pakistani diplomatic staff, closed border crossings, and mobilized approximately four hundred aircraft to forward positions along the western border. Each day brought a new measure, each measure a signal that the window for a Pakistani diplomatic off-ramp was closing. Indian Foreign Secretary Vikram Misri communicated through public statements rather than private channels, ensuring that the escalation ladder was visible not just to Islamabad but to Washington, Beijing, and the broader international community. The intent was unmistakable: India was constructing a paper trail of exhausted alternatives that would make the eventual military response appear not just justified but inevitable.

The intelligence mobilization that accompanied the diplomatic escalation was equally deliberate. India’s reconnaissance satellite constellation, including the Radar Imaging Satellite (RISAT) series and the high-resolution CARTOSAT platforms, conducted intensified passes over the nine target locations, updating the strike coordinates and confirming that the facilities remained operational. Signals intelligence platforms intercepted communications between militant commanders in Pakistan and operatives along the LoC, building a real-time picture of the targeted organizations’ alert posture. Human intelligence assets in Lahore, Bahawalpur, and Muzaffarabad reported on security changes at known militant facilities, looking for signs that the organizations had begun dispersing personnel or relocating equipment in response to the escalating crisis. The intelligence picture that emerged was encouraging for Indian planners: despite the public signals of imminent military action, the targeted organizations had not significantly altered their operational patterns, suggesting either confidence that Pakistan’s nuclear deterrent would prevent Indian strikes or a bureaucratic inertia that prevented rapid adaptation.

By early May, the diplomatic phase had served its purpose. Pakistan’s government under Prime Minister Shehbaz Sharif denied any connection to the Pahalgam attack, rejected India’s demand to hand over suspects, and accused New Delhi of manufacturing a crisis. On April 30, Pakistani military officials publicly stated that an Indian military strike was imminent, signaling that Islamabad’s intelligence services had detected the buildup but lacked either the capability or the political will to preempt it through the concessions India demanded. The stage was set.

What distinguished the fourteen-day buildup from previous India-Pakistan crises was its transparency. After the 2001 Parliament attack, India mobilized for months in Operation Parakram without striking. After the 2008 Mumbai massacre, India chose restraint entirely. After Uri in 2016, the surgical strikes came within ten days but crossed only the Line of Control, not the international border. After Pulwama in 2019, the Balakot airstrike struck a single target in Khyber Pakhtunkhwa using gravity bombs from Mirage 2000 aircraft, a platform designed in the 1970s. Each of these responses was constrained by either political hesitation, military capability limitations, or both. By May 2025, both constraints had loosened. The Rafale acquisition, completed between 2020 and 2022, gave the Indian Air Force a platform capable of launching precision cruise missiles from standoff distances. The S-400 air defense system, delivered from Russia between 2021 and 2023, provided a protective umbrella against Pakistani aerial retaliation. And the political mandate, shaped by the sectarian nature of the Pahalgam massacre, was unambiguous. When Indian Defence Minister Rajnath Singh authorized the strikes, the infrastructure to execute them was already in position.

The Countdown to 0400 Hours

Multi-agency intelligence had been tracking the nine target locations for months before Pahalgam provided the political trigger. Indian reconnaissance satellites, signals intelligence platforms, and human intelligence assets inside Pakistan had mapped the physical footprint of Jaish-e-Mohammed, Lashkar-e-Taiba, and Hizbul Mujahideen facilities with coordinates precise enough for cruise missile targeting. The Intelligence Bureau, the Research and Analysis Wing, and the Defence Intelligence Agency fed their assessments into a consolidated target package that the National Security Advisor’s office had been refining since at least early 2024. Pahalgam did not create the target list. Pahalgam authorized its execution.

The operational planning fell to the Integrated Defence Staff, working in coordination with the Indian Air Force’s Western Air Command and the Indian Navy’s Western Naval Command. Arzan Tarapore, a specialist in Indian military operations at Stanford University, has noted that coordinating a nine-target simultaneous campaign across two distinct geographic zones, Punjab and Pakistan-administered Kashmir, required a level of joint planning that India had never previously demonstrated in combat. The challenge was not merely logistical. Each target had to receive its munitions within a narrow time window to prevent Pakistan’s air defense network from reacting to the first strike and protecting the remaining eight. The twenty-three-minute window was not a tactical accident. It was a calculated requirement dictated by the need to saturate Pakistan’s command-and-control architecture before it could issue coherent defensive orders.

In the hours before the strike, Indian Air Force crews at Ambala and Hasimara air bases prepared Rafale jets with SCALP cruise missiles mounted on external hardpoints. At other forward bases, Sukhoi Su-30MKI aircraft received BrahMos supersonic cruise missiles, the first confirmed combat loading of the BrahMos on the Su-30MKI platform. Electronic warfare aircraft prepared jamming packages designed to blind Pakistan’s Chinese-supplied radar systems. The Integrated Air Command and Control System, a network linking radar stations, command centers, and fighter squadrons across northern India, entered full operational readiness. S-400 batteries at forward positions powered their acquisition radars, ready to provide the defensive umbrella that would protect Indian airspace during the inevitable Pakistani retaliation.

The final authorization came through a secure communication chain from the Cabinet Committee on Security to the Chiefs of Staff Committee to the operational commanders. At approximately 0345 hours IST, Rafale pilots received their go codes. Fifteen minutes later, the first SCALP left its pylon.

The psychological dimension of those final fifteen minutes deserves consideration. Indian Air Force pilots sitting in their cockpits at Ambala and Hasimara knew that they were about to launch the deepest Indian military campaign into Pakistani territory since the 1971 war. They understood that the weapons they were about to release would trigger a chain of events whose consequences extended far beyond the twenty-three-minute strike window. Pakistani retaliation was certain. Aerial engagement was probable. Indian casualties were possible. The pilots had trained for years on these platforms and rehearsed similar strike profiles in exercises, but no exercise could replicate the psychological weight of launching cruise missiles at a nuclear-armed adversary’s territory in the pre-dawn darkness. Their professionalism in executing the mission without reported hesitation or error spoke to the quality of Indian Air Force training and the clarity of the operational mandate they had received.

At other locations across northern India, supporting elements of the operation executed their assigned tasks. Electronic warfare aircraft activated their jamming equipment, flooding Pakistani radar frequencies with noise designed to mask the incoming cruise missiles. Airborne early warning aircraft, India’s Phalcon and Netra platforms, took station along the border to provide real-time surveillance of Pakistani air force responses. Fighter squadrons at multiple forward bases went to combat alert, prepared to scramble in defense of Indian airspace once Pakistan’s retaliation began. Naval assets in the Arabian Sea adjusted their posture for potential maritime contingencies. The twenty-three minutes were the visible tip of an operational pyramid that involved thousands of personnel across hundreds of kilometers of Indian territory.

Target One: Markaz-e-Taiba, Muridke

The most strategically significant target in Operation Sindoor’s nine-site package sat on a two-hundred-acre compound in Muridke, a city in Punjab’s Sheikhupura District approximately thirty-five kilometers northwest of Lahore, Pakistan’s second most populous city. Markaz-e-Taiba, the organizational headquarters of Lashkar-e-Taiba and its front organization Jamaat-ud-Dawa, was not a hidden facility. It operated openly, housing a seminary, a medical clinic, a school, a college, and the administrative offices from which Hafiz Saeed had directed LeT’s operations for three decades. The compound’s proximity to Lahore, a metropolitan area of over eleven million people, meant that any strike carried extraordinary risk of civilian casualties and political fallout. India struck it anyway.

Indian military officials Colonel Sofiya Qureshi and Wing Commander Vyomika Singh, briefing media on May 7, identified Markaz-e-Taiba as a center for recruitment, training, and indoctrination of militants subsequently infiltrated into Indian-administered Kashmir. The facility’s status as LeT’s nerve center was not a matter of dispute. The United Nations, the United States, the European Union, and India itself had designated Jamaat-ud-Dawa as a front for Lashkar-e-Taiba. Hafiz Saeed, the organization’s founder and operational chief, had been arrested and convicted by Pakistani courts in 2020 on terror financing charges under sustained international pressure, but the Muridke complex continued to function as LeT’s institutional headquarters under subordinate leadership.

Pakistan’s Inter-Services Public Relations directorate, led by Lieutenant General Ahmed Sharif Chaudhry, provided a sharply different account. Chaudhry stated that four Indian missiles struck a mosque named Masjid Ummul Qura within the compound, killing one man and injuring another, with two additional people reported missing. He described the surrounding residential quarters as damaged and the attack as targeting innocent civilians at a place of worship. Images released by Pakistani media showed rescuers searching through debris of what appeared to be a government health and education complex, reinforcing the narrative of civilian infrastructure destruction.

The Muridke strike was, by design, the opening salvo’s most politically charged target. Hitting LeT’s headquarters signaled that India was no longer constraining its conventional military operations to Pakistan-administered Kashmir, as it had during the 2016 surgical strikes, or to remote border areas, as at Balakot in 2019. Striking thirty-five kilometers from Lahore meant striking at the institutional core of Pakistan-sponsored proxy warfare in a location the Pakistani state had explicitly protected for decades. The message to Islamabad was layered: India possessed the intelligence to locate these facilities with precision, the platforms to reach them with standoff weapons, and the political resolve to accept the diplomatic consequences of attacking them. For the complete operational overview of how this target fit into the broader campaign, the Sindoor guide provides the full four-phase reconstruction.

Indian intelligence work behind the Muridke targeting deserves attention. Indian surveillance of the Markaz-e-Taiba compound predated the Pahalgam attack by years, if not decades. Satellite imagery analysis, signals intelligence from communication intercepts, and human intelligence from assets operating in the Lahore metropolitan area had produced a detailed floor plan of the compound’s operational sections, distinguishing between the seminary buildings used for education, the administrative offices used for organizational management, and the sections that Indian intelligence assessed as serving recruitment and training functions. The weapons selection for the Muridke strike reflected this granular intelligence: precision-guided munitions were aimed at specific structures within the two-hundred-acre campus rather than at the compound as a whole, a targeting methodology that required sub-building-level accuracy.

The Muridke compound’s history as a protected site underscored the political significance of striking it. For three decades, the Pakistani state had shielded the facility from international pressure, allowing it to operate openly despite UN sanctions designating Jamaat-ud-Dawa as a LeT front. Hafiz Saeed had held public rallies at the compound, run a hospital and ambulance service from it, and used its seminary to produce a steady stream of recruits for LeT’s militant operations. The fact that India struck this facility, the most publicly visible and politically protected piece of terrorist infrastructure in Pakistan, signaled that no target was beyond India’s reach or its political will. The precedent was as important as the damage: if Markaz-e-Taiba was not safe, nothing was.

Target Two: Markaz Subhanallah, Bahawalpur

Approximately five hundred kilometers south of Muridke, the second major Punjab target received its ordnance within the same twenty-three-minute window. Markaz Subhanallah, also known as the Usman-o-Ali campus, sat near Ahmedpur Sharqia on the outskirts of Bahawalpur, one of Pakistan’s major cities in southern Punjab. This was the institutional seat of Jaish-e-Mohammed, the organization founded by Masood Azhar after his release from Indian custody during the IC-814 hijacking crisis of December 1999. If Muridke was LeT’s brain, Bahawalpur was JeM’s heart.

The Usman-o-Ali complex combined a madrassa, organizational headquarters, and reportedly weapons storage facilities within a single campus. Indian intelligence assessed the site as a hub for JeM’s recruitment pipeline, indoctrination programs, and operational planning. Colonel Qureshi described the target as Markaz Subhanallah and identified it as a center for training operatives subsequently deployed to carry out attacks in Indian territory, including the cadres responsible for the Pulwama bombing of February 2019 and the Pathankot airbase assault of January 2016.

Pakistan’s ISPR provided starkly different details. Lieutenant General Chaudhry reported that four Indian missiles struck a mosque named Masjid Subhan in Ahmedpur Sharqia, destroying it entirely. He stated that at least five people were killed in the attack, including two men, two women, and a three-year-old girl, with thirty-one additional people injured, twenty-five men and six women. Four residential quarters where civilian families were living were damaged. Indian media reports circulated claims that Abdul Rauf Azhar, a senior JeM commander and brother of founder Masood Azhar, had been killed in the strike. These reports remained unconfirmed. Masood Azhar himself, in a subsequent statement acknowledging family members’ deaths, did not name Abdul Rauf among the deceased, leaving his fate uncertain.

The Bahawalpur strike carried a distinct strategic message from the Muridke attack. Bahawalpur was the city where JeM was born, where Masood Azhar had grown up and established the organization’s institutional infrastructure, and where JeM’s seminary continued to produce graduates who filled the organization’s operational ranks. Striking Bahawalpur meant striking at JeM’s origin story, at the physical location where the consequences of the IC-814 prisoner exchange had metastasized into a fully operational terrorist organization with the capacity to execute attacks like Pulwama and Pahalgam. Saurav Jha, a defense analyst who has tracked Indian weapons procurement, noted that the simultaneous strikes on both Muridke and Bahawalpur demonstrated that India could engage targets separated by five hundred kilometers within the same operational window, a capability that neither the 2016 surgical strikes nor the 2019 Balakot operation had demonstrated.

JeM’s presence in Bahawalpur carried temporal significance beyond the immediate strike objectives. JeM’s founding in 2000, the direct consequence of India’s decision to release Masood Azhar during the IC-814 hijacking crisis, represented what many Indian analysts regarded as the original sin of India’s counter-terrorism policy. Releasing a detained militant leader under hostage pressure led to the creation of an organization that subsequently carried out some of the most devastating attacks on Indian soil, from the 2001 Parliament assault to the 2016 Pathankot airbase attack to the 2019 Pulwama convoy bombing. Striking the physical location where that organization had gestated and grown into a major threat carried a symbolic resonance that went beyond the immediate military objectives. It was, in effect, India’s delayed correction of the 1999 decision, delivered not through diplomacy but through a SCALP warhead.

Reports of women and children among the casualties at Bahawalpur introduced an ethical dimension that neither government fully addressed. India’s position, that the facility was a militant headquarters, implied that any casualties were the responsibility of an organization that chose to co-locate operational infrastructure with civilian residences. Pakistan’s position, that the facility was a mosque and residential area, implied that India had deliberately targeted civilians at a place of worship. The truth likely occupied contested ground between these poles. JeM’s Usman-o-Ali campus had always combined educational, religious, and operational functions within a single compound, a deliberate architectural choice that created exactly the kind of ambiguity that made post-strike damage assessment politically combustible.

Target Three: Shawai Nala Camp, Muzaffarabad

Shifting from Punjab to Pakistan-administered Kashmir for the third target. Shawai Nala camp, located near Muzaffarabad, the capital of Pakistan-administered Kashmir, was identified by Indian officials as a Lashkar-e-Taiba training facility. Muzaffarabad sits at the confluence of the Jhelum and Neelum rivers, roughly twenty-five kilometers from the Line of Control, the de facto border between Indian and Pakistani-administered portions of Kashmir. Its proximity to the LoC had made it a staging ground for militant infiltration into Indian territory for decades.

The Shawai Nala facility, according to Indian briefings, served as a forward training camp where LeT operatives received final preparation before attempting to cross the LoC into Indian-administered Kashmir. The camp’s location in the mountainous terrain near Muzaffarabad provided natural concealment while maintaining proximity to the infiltration routes that run through the Jhelum valley and across the Pir Panjal range. Indian intelligence assessed that graduates of the Shawai Nala program constituted a significant portion of the fighters intercepted or killed by Indian security forces along the LoC in recent years.

Pakistani accounts of the Muzaffarabad strikes painted a different picture. The ISPR reported damage to civilian structures and casualties among local residents, framing the attacks as assaults on populated areas in the administrative capital of a disputed territory. The geographic sensitivity of striking Muzaffarabad, the seat of the government of Pakistan-administered Kashmir, added a diplomatic dimension to the military calculus. India’s position, as articulated by Foreign Secretary Misri, was that the strikes targeted terrorist infrastructure regardless of its location, and that the presence of militant facilities in or near population centers was itself a choice made by the organizations and their state sponsors to use civilian proximity as a shield.

The Shawai Nala strike reflected a pattern visible across all five targets in Pakistan-administered Kashmir. Each site was situated along the infiltration corridor that runs from Pakistan through the Jhelum and Neelum valleys into Indian-administered Kashmir. Striking these facilities simultaneously aimed not just to destroy physical infrastructure but to disrupt the entire pipeline through which trained operatives moved from Pakistani training camps to their deployment zones in the Kashmir valley. The operational logic was not merely punitive but functionally degrading, designed to impose a sustained capability deficit on LeT’s forward operations.

Indian intelligence assessments of the Shawai Nala camp had identified it as part of a network of forward facilities that Lashkar-e-Taiba maintained along the LoC frontier. These camps rotated operatives through final training cycles that focused specifically on the terrain and conditions they would encounter during infiltration attempts. Trainees at facilities like Shawai Nala learned the specific mountain passes, forest trails, and river crossings that smugglers and militants had used for decades to move between the two sides of the LoC. They practiced night movement, cold-weather survival, and small-arms handling adapted to the high-altitude environment. Destroying these forward training nodes aimed to create a gap in LeT’s infiltration pipeline that the organization could not quickly replace, as the site-specific knowledge embedded in these facilities, knowledge of particular routes, terrain features, and Indian patrol patterns, could not be transferred to a new location without extensive re-development.

The Muzaffarabad strikes also tested Pakistan’s air defense coverage in a region where terrain complicates radar performance. The mountainous topography of Pakistan-administered Kashmir creates radar shadows and dead zones that cruise missiles, flying at low altitude along river valleys, can exploit to approach targets undetected. Indian operational planners selected approach routes for the Muzaffarabad-bound munitions that maximized the use of these terrain masking effects, threading missiles through valleys that Pakistani radar stations on higher ground could not effectively cover. The successful engagement of both Muzaffarabad targets without reported interception during the approach phase validated the Indian Air Force’s terrain analysis and route planning for operations in mountainous environments.

Target Four: Markaz Abbas, Kotli

Kotli District, located south of Muzaffarabad in Pakistan-administered Kashmir, received the fourth set of strikes in the twenty-three-minute sequence. Indian officials identified the target as Markaz Abbas, a JeM-affiliated facility that they described as an operational command post for coordinating militant activities in the Poonch and Rajouri sectors of Indian-administered Kashmir. Kotli sits approximately forty kilometers from the LoC, close enough to serve as a staging area but far enough to avoid the routine monitoring that Indian forces maintained along the immediate border zone.

The Abbas compound, according to Indian intelligence assessments, functioned as a transit hub for JeM operatives moving between the organization’s headquarters in Bahawalpur and its forward positions along the LoC. The facility reportedly combined residential quarters for operatives with communications equipment and planning spaces. Its designation as a JeM site distinguished it from the LeT facilities struck elsewhere in Pakistan-administered Kashmir, underscoring that Operation Sindoor’s target package was designed to degrade both major Pakistan-based organizations simultaneously rather than focusing exclusively on one.

Pakistan’s ISPR reported that the strikes in Kotli hit a mosque identified as Masjid-e-Abbas, with the lieutenant general stating that five civilians were killed across the Muzaffarabad and Kotli locations combined. The discrepancy between India’s identification of the site as a JeM command post and Pakistan’s description of it as a mosque encapsulated the broader dispute that surrounded every target in Operation Sindoor. India maintained that militant organizations in Pakistan routinely operated from within religious structures, using them as administrative offices, weapons stores, and meeting points precisely because they understood that strikes on mosques would generate international condemnation. Pakistan maintained that the structures were places of worship and that India was manufacturing military justifications for attacks on civilian and religious infrastructure.

The Kotli target also illustrated the geographic depth of India’s intelligence penetration into Pakistan-administered Kashmir. Previous Indian operations, including the 2016 surgical strikes, had been limited to targets within a few kilometers of the LoC. Striking Kotli, forty kilometers from the border, demonstrated that India’s target identification capability extended well beyond the immediate frontier zone and into the administrative heartland of Pakistan-administered Kashmir. This geographic expansion of the operational envelope was, in strategic terms, as significant as the weapons upgrade from gravity bombs to cruise missiles. It meant that Pakistan could no longer assume that facilities located beyond the immediate border zone were safe from Indian conventional military action.

Kotli’s strategic importance derived from its position as a transit hub connecting the lowlands of Punjab with the mountainous terrain of Kashmir. Militants moving from training camps in Bahawalpur or Muridke toward the LoC frequently passed through the Kotli corridor, making it a natural location for forward staging facilities. The city’s road network, connecting it to Rawalpindi and Islamabad to the north and to the LoC crossing points to the east, provided the logistical infrastructure that militant organizations needed to sustain infiltration operations. By striking facilities in both Kotli and Muzaffarabad, India targeted the two key nodes in the north-south transit chain that connected Pakistan’s militant training infrastructure to the Kashmir theater of operations. The combined effect was designed to sever the pipeline at multiple points simultaneously, imposing a capability gap that no single organizational response could quickly repair.

Target Five: Syedna Bilal Complex, Muzaffarabad

The fifth target returned to Muzaffarabad, striking a second facility in the Pakistan-administered Kashmir capital. Indian officials identified this site as the Syedna Bilal complex, a JeM-affiliated structure that they described as a training and indoctrination center. The decision to strike two separate targets within a single city reflected India’s assessment that Muzaffarabad hosted multiple distinct militant facilities belonging to different organizations, each requiring individual targeting rather than a single area-effect strike.

Pakistan’s response identified the target as Masjid Syedna Bilal, a mosque that the ISPR stated was damaged in the Indian strikes along with the surrounding residential area. Casualty figures from the Muzaffarabad strikes were reported collectively by Pakistan, with the ISPR attributing deaths across the two Muzaffarabad targets to the same series of strikes. The dual targeting of Muzaffarabad raised particular concerns among international observers because the city, as the administrative capital of Pakistan-administered Kashmir, housed government offices, hospitals, and dense residential neighborhoods in close proximity to any potential military targets.

Indian military planners anticipated this criticism. The use of precision-guided munitions, specifically the SCALP cruise missile with its terminal guidance system combining GPS, inertial navigation, and terrain reference, was designed to limit the blast radius to the target structure and its immediate surroundings. Colonel Qureshi emphasized during the May 7 briefing that every target location had been selected to minimize civilian casualties, with the strike timing of 0400 hours, the pre-dawn period when civilian movement would be minimal, chosen as an additional precaution. The extent to which these precautions succeeded in limiting civilian harm remained a matter of fierce dispute between the two governments. For the broader damage assessment debate, the contested casualty figures require their own dedicated analysis.

The two Muzaffarabad strikes carried a particular psychological weight. By hitting the capital of Pakistan-administered Kashmir twice in the same operation, India signaled that it considered the entire territory a legitimate operational theater, not merely the frontier areas closest to the LoC. This represented a significant escalation from the 2019 Balakot strike, which targeted a location in Khyber Pakhtunkhwa rather than Pakistan-administered Kashmir itself. Striking Muzaffarabad, the symbolic and administrative center of Pakistan’s claim to the disputed territory, carried implications that extended beyond counter-terrorism into the broader India-Pakistan territorial dispute.

International observers noted that the dual Muzaffarabad strikes created a precedent with implications beyond the immediate conflict. If India could strike the administrative capital of Pakistan-administered Kashmir and frame the operation as counter-terrorism rather than territorial aggression, the distinction between counter-terrorism operations and acts of war against a rival state’s administered territory became increasingly difficult to maintain. This ambiguity was, from India’s perspective, a feature rather than a bug. It expanded the scope of operations that India could claim as legitimate counter-terrorism measures while narrowing the range of targets that Pakistan could consider safe from Indian conventional military action. The geographic boundary that had previously constrained Indian operations, essentially the Line of Control, had been not just crossed but rendered strategically irrelevant by the Muzaffarabad strikes.

Target Six: Gulpur Camp, Kotli District

The sixth target in the twenty-three-minute sequence hit a facility near Gulpur in Kotli District, the second strike in this Pakistan-administered Kashmir district. Indian officials identified the Gulpur site as a joint LeT and Hizbul Mujahideen camp, the first target in the operation attributed to the involvement of Hizbul Mujahideen, a Kashmir-focused militant group with deep roots in the Valley’s indigenous insurgency. The inclusion of a Hizbul target reflected India’s assessment that the Pahalgam attack, while claimed initially by The Resistance Front, a LeT proxy, was part of a broader militant ecosystem that included Hizbul operatives as well.

The Gulpur facility, according to Indian intelligence briefings, served as a cross-organizational training site where operatives from multiple groups received instruction in infiltration tactics, weapons handling, and communications security before deployment across the LoC. Joint facilities of this nature had been documented by Indian intelligence agencies since the 1990s, when the ISI had encouraged cooperation among different militant organizations operating in Kashmir to maximize the insurgency’s operational reach while distributing the risk across multiple groups.

Striking a joint LeT-Hizbul facility expanded the operation’s target profile beyond the two organizations directly linked to the Pahalgam attack. India’s rationale, as articulated by officials, was that cross-organizational infrastructure in Pakistan-administered Kashmir operated as an integrated network regardless of organizational branding, and that dismantling any single component required addressing the shared facilities that connected them. Arzan Tarapore has observed that this approach reflected a shift in Indian counter-terrorism doctrine from targeting specific organizations to targeting the infrastructure that enabled cross-organizational cooperation, a more systemic approach that treated the problem as a network rather than a collection of discrete entities.

The second strike in Kotli District within the same twenty-three-minute window also demonstrated the density of India’s target intelligence in Pakistan-administered Kashmir. Two targets in Kotli and two in Muzaffarabad meant that four of the operation’s nine targets were clustered in a relatively compact geographic area along the Jhelum valley, reflecting the concentration of militant infrastructure in this corridor. The full conflict timeline from Pahalgam through the ceasefire maps how these strikes fit into the broader sequence of events.

Target Seven: Markaz Ahl-e-Hadith, Barnala, Bhimber District

The seventh target shifted south within Pakistan-administered Kashmir to Bhimber District, which borders Punjab and lies adjacent to the Narowal and Sialkot districts of Pakistani Punjab. Indian officials identified the target as Markaz Ahl-e-Hadith in the village of Barnala, which they attributed to Lashkar-e-Taiba. The Ahl-e-Hadith designation was significant because LeT’s ideological orientation derives from the Ahl-e-Hadith school of Sunni Islam, a puritanical movement that forms the doctrinal backbone of Hafiz Saeed’s organization. Identifying a Markaz (center) with this specific doctrinal affiliation pointed to a facility that served both ideological indoctrination and organizational functions.

Bhimber was notable for its proximity to the Punjab border, sitting in a transitional zone between Pakistan-administered Kashmir and Pakistani Punjab. Pakistani officials had not initially mentioned Bhimber as one of the strike locations in their early briefings on May 7, reporting strikes at six locations rather than nine. The location’s proximity to Kotli, mentioned separately in ISPR briefings, created confusion about whether the Bhimber strike was being counted within the Kotli figures or whether it represented an additional target that Pakistan’s initial damage assessment had not yet incorporated.

The targeting of a facility in Bhimber underscored a geographic pattern in Operation Sindoor’s design. The five targets in Pakistan-administered Kashmir were distributed along a north-south axis from Muzaffarabad through Kotli to Bhimber, effectively tracing the western edge of the disputed territory’s border with Pakistani Punjab. This distribution suggested that India’s target package was designed not merely to strike specific facilities but to demonstrate the ability to engage targets across the full length of the LoC and beyond, from the northern extremity near Muzaffarabad to the southern reaches near Bhimber. For a military doctrine built on deterrence through demonstrated capability, the geographic spread of the strikes was as important as the damage they inflicted on any individual target.

Striking seven targets by this point in the twenty-three-minute sequence meant that India’s weapons systems, communications networks, and command-and-control architecture were performing the simultaneous coordination that peacetime exercises had rehearsed but combat had never tested. Every additional target engaged within the window validated the proposition that India could sustain precision operations at scale against a nuclear-armed adversary’s territory without the operational chain breaking down. The absence of any reported malfunction or misdirection during the initial wave, a claim contested by Pakistan regarding the Sialkot strikes, suggested that the pre-strike intelligence and targeting preparations had achieved a level of accuracy consistent with the best-case planning scenarios.

Target Eight: Mehmona Joya, Sialkot District

The operational theater returned to Pakistani Punjab for the eighth target. Indian officials identified a facility near the village of Mehmona Joya in Kotli Loharan West, Sialkot District, as a Hizbul Mujahideen camp. Sialkot, one of Pakistan’s most important industrial centers for surgical instruments, sporting goods, and leather products, sits in the narrow corridor of Pakistani Punjab between the Indian border to the east and the Line of Control to the north. Its industrial significance made it a high-profile location for military targeting, though India’s stated target was not the city itself but a militant facility in the rural outskirts.

Pakistan’s ISPR offered a notably different account of the Sialkot strikes. Lieutenant General Chaudhry stated that one of the two strikes directed at Kotli Loharan, the village north of Sialkot, had misfired and failed to detonate, while the other had landed in an open field and caused no damage. If accurate, this account would represent the only reported failure in Operation Sindoor’s nine-target package, a single miss rate of approximately eleven percent. India’s Colonel Qureshi did not directly address the ISPR’s misfire claim during the May 7 briefing, instead stating that India had struck what it called the Sarjal camp in the Sialkot area, identified as a training center for operatives responsible for a March 2025 attack that killed four police officers in Indian-administered Kashmir.

The discrepancy between India’s and Pakistan’s accounts of the Sialkot strikes illustrates the verification challenge that pervaded every aspect of Operation Sindoor’s damage assessment. India claimed successful strikes on all nine targets. Pakistan denied meaningful damage at several locations and reported civilian casualties at others. Commercial satellite imagery, the primary tool available for independent verification, can show structural damage and blast patterns but cannot confirm the identity or number of human casualties. The absence of independent ground-level access to any of the nine strike sites meant that the competing narratives remained unresolved.

Sialkot’s inclusion in the target package reflected India’s intelligence assessment that the Hizbul Mujahideen maintained training infrastructure in this border district, leveraging its proximity to the LoC for rapid infiltration into the Poonch and Rajouri sectors. The March 2025 police killing in Indian-administered Kashmir, which India attributed to Hizbul operatives trained at the Sialkot facility, provided a specific and recent operational link between the training camp and attacks on Indian soil. This specificity was characteristic of the May 7 briefing’s approach: each target was tied not merely to organizational affiliation but to identifiable recent attacks or operational activities.

The Sialkot district’s significance extends beyond its role as a militant training ground. As one of Pakistan’s most important industrial centers, with a major economic stake in international trade, its proximity to the Indian border had always made it a sensitive location in any military escalation scenario. Indian military planners were acutely aware that strikes near Sialkot would generate economic anxiety in Pakistan’s business community, adding an economic pressure dimension to the military message. The rural location of the targeted facilities, away from the city’s industrial zones, reflected the operational principle of striking militant infrastructure while avoiding collateral damage to Pakistan’s legitimate economic assets, a distinction that India’s briefings emphasized repeatedly.

From Sialkot in northeastern Punjab to Bahawalpur in the south demonstrated that India’s intelligence and strike reach covered the full length of Pakistani Punjab, a province of over one hundred twenty million people that constitutes Pakistan’s political and economic heartland. This reach had never been demonstrated before. Previous Indian operations had been limited to remote border areas in Khyber Pakhtunkhwa or along the LoC itself. Engaging targets across the breadth of Punjab sent a message that transcended the specific counter-terrorism objectives: Indian precision munitions could reach any point in Pakistan’s most important province.

Target Nine: Tera Katlan, Sarjal, Shakargarh Tehsil

India’s final target in the opening twenty-three-minute salvo was located near the village of Tera Katlan in the Sarjal area of Shakargarh Tehsil, Sialkot District. Indian officials identified this facility as a JeM camp, the third JeM target in the nine-site package alongside Bahawalpur and Markaz Abbas in Kotli. Shakargarh sits in the northernmost reaches of Pakistani Punjab, close to the point where Punjab, Pakistan-administered Kashmir, and the Indian border converge. Its location in the geographic triangle where these three zones meet made it a natural transit point for operatives moving between JeM’s headquarters in Bahawalpur and the organization’s forward positions along the LoC.

The Tera Katlan facility, according to Indian intelligence, functioned as a JeM staging area where operatives received their final briefings and equipment before attempting LoC crossings. The camp’s location in the rural hinterland of Shakargarh, away from major roads and urban centers, provided the seclusion that operational staging required. India’s identification of two JeM targets in the Sialkot district area, one attributed to Hizbul and one to JeM, suggested that this border region hosted a concentration of militant infrastructure from multiple organizations, consistent with the cross-organizational cooperation patterns documented in other parts of the target package.

With the ninth strike complete, the twenty-three-minute window closed. Indian Air Force assets withdrew from Pakistani airspace, and the operation’s opening phase transitioned from offensive strike to defensive posture as commanders anticipated Pakistan’s response. The response came within hours, beginning with artillery shelling along the LoC and escalating over the following days into drone attacks, missile launches, and the largest aerial engagement between Indian and Pakistani fighters since the 1971 war. But those consequences belonged to the days that followed. The twenty-three minutes themselves were, in operational terms, complete.

The completion of the nine-target sequence without a single reported interception during the strike window represented a comprehensive failure of Pakistan’s early warning and air defense architecture. Despite possessing Chinese-supplied radar systems, including the YLC-18 long-range surveillance radar and the HQ-9 air defense missile system, Pakistan’s air defense network appears to have been unable to detect, track, and engage the incoming munitions in the compressed timeline that the twenty-three-minute window allowed. Indian electronic warfare jamming degraded radar performance across the strike corridors, and the low-altitude, terrain-following flight profiles of the SCALP missiles exploited the radar shadows that the mountainous and semi-arid terrain of Punjab and Kashmir created. By the time Pakistani air defense operators recognized the scope of the attack, the weapons were already reaching their terminal guidance phases, where interception becomes exponentially more difficult.

The nine-target completion also validated a planning methodology that Indian military strategists had developed through years of wargaming and simulation. Each target in the package had been assigned a specific weapons system based on the facility’s characteristics: hardened structures received SCALP or BrahMos warheads capable of penetrating reinforced construction, while lighter structures received HAMMER munitions or loitering drones. This weapon-to-target matching ensured that the available munitions inventory was allocated efficiently, with the most expensive and capable weapons reserved for the most challenging targets. The successful completion of all nine engagements within the planned window suggested that the wargaming and simulation phase had accurately predicted the operational requirements, a finding with significant implications for how the Indian military plans future precision-strike campaigns.

The Weapons That Defined the 23 Minutes

Operation Sindoor marked the combat debut of multiple weapons systems that India had acquired or developed over the preceding decade, transforming the strike campaign into the largest real-world test of advanced precision munitions since the opening phase of the 2003 Iraq invasion. The complete weapons catalog covers each system’s specifications and performance in granular detail, but understanding the twenty-three minutes requires grasping how these platforms worked together.

The SCALP cruise missile, manufactured by European defense consortium MBDA under the designation SCALP-EG (Systeme de Croisiere Autonome a Longue Portee - Emploi General), provided the operation’s primary deep-strike capability. Also known as Storm Shadow in its British variant, the SCALP is an air-launched cruise missile with a range exceeding four hundred fifty kilometers in its export configuration. Its guidance system combines inertial navigation, GPS satellite positioning, and terrain reference navigation, allowing it to fly at low altitude along pre-programmed routes that exploit terrain features to avoid radar detection. The missile’s terminal guidance uses infrared imaging to match the target against stored reference images, providing accuracy measured in single-digit meters. According to Air Forces Monthly, Indian Air Force Rafale jets launched ten SCALP-EG cruise missiles during the operation, with aircraft operating from Ambala and Hasimara air bases.

Jointly developed by India’s Defence Research and Development Organisation and Russia’s NPO Mashinostroyeniya, provided the operation’s high-speed strike component. Traveling at approximately Mach 2.8 to Mach 3, the BrahMos reaches its target far faster than the subsonic SCALP, reducing the adversary’s reaction time from minutes to seconds. During Operation Sindoor, BrahMos missiles were launched from Sukhoi Su-30MKI aircraft, marking the first confirmed combat use of the air-launched BrahMos variant. Former Air Chief Marshal V.R. Chaudhari subsequently described the BrahMos and SCALP combination as a complementary strike package where the SCALP’s stealth and range provided precision against hardened targets while the BrahMos’s speed overwhelmed air defenses through sheer velocity.

The HAMMER precision-guided munition (Highly Agile Modular Munition Extended Range), developed by French firm Safran, provided a medium-range option between the long-reach SCALP and the high-speed BrahMos. The HAMMER is a guidance kit attached to conventional bombs, converting them into precision munitions with ranges of up to seventy kilometers depending on launch altitude. Its guidance system combines GPS and inertial navigation with an autonomous terminal seeker, making it resistant to electronic jamming. The HAMMER’s relatively lower cost compared to cruise missiles made it suitable for targets where extreme range or speed was not required but precision remained essential.

Loitering munitions, also categorized as kamikaze drones, added a fourth capability layer to the strike package. The SkyStriker, co-developed by Israeli firm Elbit Systems and India’s Alpha Design Technologies, made its combat debut during Operation Sindoor. Capable of carrying a five-to-ten-kilogram warhead over a range of approximately one hundred kilometers, the SkyStriker loiters over the target area until the operator identifies and confirms the aim point, then dives into the target. The Nagastra-1, developed by Indian firm Solar Industries, provided a fully indigenous loitering munition option with a fifteen-kilometer range and 1.5-kilogram explosive payload. Solar Industries’ leadership confirmed its use during the operation. The JM-1, produced by Indian firm Johnnette Technologies, became the first entirely Indian-designed kamikaze drone to be employed in combat when it struck targets during Operation Sindoor.

The diversity of the weapons package reflected a deliberate doctrinal choice. By employing cruise missiles, precision-guided bombs, supersonic munitions, and loitering drones in a single twenty-three-minute window, India demonstrated what defense analysts call “multi-domain strike capability,” the ability to engage targets using complementary platforms that stress an adversary’s defenses across multiple threat axes simultaneously. A defender optimized to intercept cruise missiles remains vulnerable to supersonic BrahMos. A defender scanning for high-altitude bombers may miss terrain-hugging SCALP missiles. A defender focused on incoming missiles may not detect loitering munitions approaching from unpredictable vectors. The layered approach ensured that no single defensive countermeasure could neutralize the entire strike package.

Combat performance of these systems during the twenty-three minutes became a subject of intense interest for defense procurement agencies worldwide. Rafale jets had seen limited combat before Sindoor, primarily in French operations over Libya, Syria, and Mali. The SCALP had been used in those conflicts but never against a peer-level adversary with sophisticated air defenses. The BrahMos had never been fired in anger. The fact that all three systems were employed simultaneously against an adversary equipped with Chinese-supplied radar and air defense systems turned the twenty-three minutes into an unintended but invaluable combat evaluation. India’s subsequent decision to procure an additional one hundred SCALP missiles in a deal reportedly valued at approximately three thousand crore rupees suggested that the Indian Air Force considered the system’s combat performance satisfactory.

Operating multiple weapons systems from different platforms in the same airspace cannot be overstated. SCALP missiles, traveling at subsonic speeds along terrain-hugging profiles, occupied different altitude bands and flight paths than supersonic BrahMos missiles following ballistic or sea-skimming trajectories. HAMMER munitions, released from Rafale jets at medium altitude, followed yet another flight profile, using gravity-assisted glide combined with powered terminal guidance. Loitering munitions operated at lower altitudes, circling target areas and transmitting real-time video to operators who could redirect them to emerging targets of opportunity. Managing this diversity of flight profiles, speeds, altitudes, and guidance methods within a common airspace required deconfliction protocols that ensured no weapon interfered with another’s flight path or guidance signal.

Electronic warfare aspects of the weapons package added yet another layer of complexity. SCALP missiles rely partly on GPS for mid-course navigation, meaning that any Indian jamming of GPS frequencies to deny Pakistan navigation data could potentially affect Indian weapons as well. The SCALP’s terrain-reference navigation system provided a GPS-independent backup, but other munitions in the package lacked this redundancy. Frequency management, the practice of carefully partitioning the electromagnetic spectrum so that friendly jamming signals do not interfere with friendly guidance signals, was critical. Indian electronic warfare officers operating from specialized aircraft had to maintain a real-time map of which frequencies were being jammed, which were being used by Indian weapons, and which needed to remain clear for command-and-control communications, all while adapting to Pakistan’s own electronic countermeasures responses.

Ammunition expenditure during the twenty-three minutes also carried significant logistics implications. Ten SCALP missiles represented a substantial portion of India’s SCALP inventory, which was limited by the terms of the Rafale acquisition contract. BrahMos missiles, while produced domestically in a joint venture, remain expensive and time-consuming to manufacture. The post-Sindoor replenishment orders that India placed with MBDA for additional SCALPs and the acceleration of domestic BrahMos production schedules reflected a strategic lesson: precision-strike campaigns consume expensive munitions rapidly, and a nation’s ability to sustain such campaigns depends on its inventory depth and resupply speed. India’s defense procurement establishment began treating missile inventory management as a first-order strategic priority in the months following Sindoor, a shift with long-term implications for India’s defense budget and industrial base.

Coordinating a Nine-Target Simultaneous Campaign

The operational challenge of engaging nine targets across two geographic zones within twenty-three minutes represented a quantum leap in Indian military capability. Previous Indian cross-border operations had engaged single targets: one objective at Uri in 2016 (though the surgical strikes hit multiple launch pads along a narrow LoC front), one facility at Balakot in 2019. Sindoor required the Indian military to coordinate strike packages from multiple air bases, synchronize launch times across aircraft operating hundreds of kilometers apart, manage electronic warfare jamming across a front stretching from Muzaffarabad to Bahawalpur, and maintain defensive readiness against Pakistani retaliation while the offensive operation was still in progress.

IACCS, India’s Integrated Air Command and Control System, provided the backbone for this coordination. IACCS is a network that fuses radar data from across India’s air defense architecture into a single common operational picture, distributed to command centers and fighter squadrons in real time. During Operation Sindoor, the system enabled commanders to track the position of every Indian aircraft, the launch status of every weapon, and the status of Pakistani air defenses simultaneously. Coordination between the Indian Air Force and the Indian Navy, which reportedly provided BrahMos launch platforms from western naval assets, required the kind of joint-service integration that India had been developing through exercises like Tarang Shakti and Vayu Shakti but had never tested in combat conditions.

The timing constraints were dictated by two competing requirements. Compressed timing, striking all nine targets as close to simultaneously as possible, minimized Pakistan’s ability to alert unhit facilities and disperse assets once the first strike was detected. But compressed timing also increased the risk of coordination failure, where aircraft arriving early at launch positions might be detected, or where weapon systems launched seconds apart might create electromagnetic interference with each other’s guidance packages. The twenty-three-minute window represented the operational compromise: tight enough to prevent effective Pakistani defensive coordination, loose enough to permit sequential launches that avoided mutual interference.

Indian Air Force operations from Ambala and Hasimara, two bases separated by approximately one thousand two hundred kilometers, required precise timing synchronization. Rafale jets launching SCALP missiles from the western approaches needed to release their weapons at times calculated so that the missiles’ time-of-flight, varying by distance and route, delivered all warheads to their targets within the same compressed window. BrahMos missiles, traveling at Mach 3, had much shorter flight times than the subsonic SCALP and therefore needed to be launched later despite covering similar or shorter distances. The sequencing of launches from different platforms, bases, and geographic positions to produce near-simultaneous impacts across nine dispersed targets was, in the assessment of multiple defense analysts, the single most technically demanding aspect of the entire operation.

The electronic warfare dimension added another coordination layer. Indian jamming aircraft needed to suppress Pakistani radar coverage across the strike corridors without interfering with India’s own weapons guidance systems. SCALP missiles use terrain-reference navigation that operates independently of GPS, providing resilience against GPS jamming, but other weapons in the package relied on satellite navigation that could theoretically be disrupted by friendly electronic warfare systems operating in adjacent frequency bands. Managing the electromagnetic spectrum across a multi-platform, multi-weapon operation, ensuring that jamming degraded the adversary’s defenses without compromising friendly weapons guidance, required a level of electronic warfare coordination that India had practiced extensively in exercises but never validated in combat.

Intelligence preparation for the twenty-three minutes deserves recognition as a separate operational achievement. Each of the nine targets required precise geographic coordinates, updated structural information confirming that the targeted buildings still served their assessed functions, pattern-of-life analysis indicating when the facilities would be occupied by militants rather than civilians, and air defense mapping showing the optimal approach routes for incoming munitions. This intelligence had been compiled over months through a fusion of satellite reconnaissance, signals intelligence, and human intelligence from sources operating inside Pakistan. The Research and Analysis Wing, India’s external intelligence agency, and the Defence Intelligence Agency, the military’s intelligence arm, reportedly conducted a final verification cycle in the seventy-two hours before the strikes, confirming that no major changes to the target set had occurred since the operational plan was finalized.

The decision to strike at 0400 hours reflected careful analysis of multiple variables beyond the obvious advantage of reduced civilian movement. Atmospheric conditions at that hour, typically characterized by stable air pressure and minimal wind, provided optimal cruise missile flight conditions. The pre-dawn darkness reduced the effectiveness of any visual observation and reporting by local residents that might alert other targets. Pakistani radar stations, while operational around the clock, would have been staffed at nighttime manning levels rather than the heightened alert postures of daytime operations. Even the choice of a weekday rather than a weekend was deliberate, as weekend schedules in the targeted facilities might have produced different occupancy patterns from those that intelligence had mapped during weekday observations.

Command-and-control architecture employed during the twenty-three minutes reflected India’s evolving joint warfare doctrine. Rather than a single service controlling the operation, the Integrated Defence Staff served as the coordination hub, linking the Indian Air Force’s operational squadrons with the National Security Advisor’s strategic direction and the Cabinet Committee on Security’s political authority. This structure had been designed but never combat-tested, and the twenty-three minutes served as its validation. Post-operation analysis within the Indian military establishment reportedly concluded that the IACCS and Integrated Defence Staff coordination performed above expectations, though specific areas for improvement were identified in the classified after-action reviews.

The Damage Verification Debate

The damage inflicted during the twenty-three minutes became the most contentious factual question of the entire India-Pakistan conflict. India claimed that all nine targets were hit, that the strikes destroyed significant terrorist infrastructure, and that the operation killed over one hundred militants. Pakistan denied meaningful damage at several locations, claimed that Indian missiles hit mosques and civilian residences rather than militant facilities, and reported thirty-one civilian casualties across the six strike locations it acknowledged. Neither side permitted independent access to the strike sites, and both sides had strong political incentives to shape the damage narrative to serve their domestic and international audiences.

Commercial satellite imagery, the closest available approximation to independent verification, showed structural damage consistent with precision munition impacts at several of the reported target locations. Pre-strike and post-strike imagery comparison revealed destroyed or heavily damaged buildings at Muridke and Bahawalpur, though the resolution of commercially available satellite imagery could confirm that buildings were hit and destroyed but could not determine who was inside them at the time of impact. Satellite data from Planet Labs and Maxar Technologies showed blast patterns, debris fields, and structural collapses at multiple sites, supporting India’s claim that the weapons reached their targets. Logistical convoys observed in satellite imagery moving into Bahawalpur in the days following the strikes suggested continued activity at the site, complicating the damage assessment.

The gap between India’s claimed casualty figures and Pakistan’s reported numbers was too wide for reconciliation. India’s assertion of over one hundred militant deaths implied that the targeted facilities were occupied at the time of the strikes by significant numbers of militants, a plausible scenario given that the pre-dawn timing coincided with the period when residents of residential-style compounds would be in their quarters. Pakistan’s insistence on thirty-one civilian deaths, including women and children, implied that the facilities were residential neighborhoods rather than militant installations. Both versions served political needs: India needed high militant casualty figures to justify the operational risks, while Pakistan needed civilian casualty figures to generate international sympathy and frame the strikes as aggression against a civilian population.

The verification impasse reflected a structural problem inherent in military operations of this nature. Precision-guided munitions can be independently assessed for accuracy (did they hit the intended building?) through satellite imagery, but the two most politically important questions, whether the targeted facilities were actually military infrastructure and how many militants versus civilians died, required ground-level access that neither side was willing to provide. This structural unverifiability meant that the damage narrative remained, and will likely remain, a matter of which government’s claims an observer chooses to credit rather than a settled factual question. The parallel to the Balakot damage debate of 2019, where India claimed extensive damage to a JeM training facility while Pakistan denied significant impact, was unavoidable. Both episodes exposed the same gap between precision-strike capability and post-strike verification capability. India could put a missile through a specific window but could not prove to the world what was behind that window.

International dimensions of the damage debate complicated matters further. The United States, navigating its relationships with both India and Pakistan, refrained from endorsing either side’s casualty claims, instead calling for de-escalation. China, as Pakistan’s primary diplomatic and military ally, backed Islamabad’s civilian casualty narrative without providing independent evidence. European nations, several of which had supplied the weapons India used, maintained careful neutrality on the damage question while privately expressing satisfaction that their systems had performed as advertised. This geopolitical overlay meant that the damage assessment was never purely a factual question. It was a diplomatic instrument that different powers calibrated to their strategic interests.

The Centre d’Histoire et de Prospective Militaires, a Swiss military research institution, published a detailed reconstruction in January 2026 that attempted to reconstruct the campaign using operational data rather than either side’s claims. Their analysis credited the Indian strikes with achieving their stated counter-terrorism objectives while acknowledging that the full scope of damage, both to militant infrastructure and civilian populations, remained beyond independent verification. The Swiss report represented the closest approximation to an impartial assessment but acknowledged its own limitations given the absence of ground-truth data.

For the specific analysis of India’s claim of killing over one hundred militants, the dedicated damage assessment article examines the evidence and counter-claims in granular detail. Here, it suffices to note that the damage verification debate is not merely a factual question but a structural feature of modern precision warfare between adversaries who control access to their own territory. Until a mechanism exists for independent post-strike assessment, and no such mechanism is likely to emerge between India and Pakistan, every precision strike campaign will produce the same inconclusive damage narrative.

Key Figures Behind the Operation

The twenty-three minutes were the product of decisions made by individuals at multiple levels of India’s civil-military hierarchy, each contributing a specific element to the operation’s conception, authorization, and execution.

National Security Advisor Ajit Doval, widely regarded as the architect of India’s post-2014 aggressive counter-terrorism posture, played a central role in shaping the operational concept. Doval’s background as a former Intelligence Bureau director with extensive field experience in counter-terrorism operations in Punjab, Kashmir, and abroad gave him a granular understanding of the intelligence requirements for precision targeting. Under his leadership, the National Security Council Secretariat had been developing contingency plans for a range of military responses to potential Pakistan-originated terrorist attacks, plans that could be activated rapidly when the political trigger arrived. Pahalgam provided that trigger, and the speed with which India transitioned from the attack to the fourteen-day escalation ladder to the strikes themselves reflected preparation that predated the specific crisis by months or years.

Indian Defence Minister Rajnath Singh served as the civilian authority who conveyed the Cabinet Committee on Security’s authorization to the military leadership. Singh’s public statements in the days preceding the strikes had signaled that India considered military action not merely an option but a near-certainty, a departure from the strategic ambiguity that had characterized previous crises. His characterization of the strikes as “focused, measured, and non-escalatory” established the rhetorical framework that India used to manage international reaction, positioning Sindoor as a targeted counter-terrorism operation rather than an act of war against Pakistan. Singh’s role was not merely administrative. His political standing as a senior BJP leader with close ties to Prime Minister Narendra Modi ensured that the military had unambiguous civilian backing for the operation, eliminating the kind of civil-military ambiguity that had complicated previous crisis responses.

Indian Foreign Secretary Vikram Misri led the diplomatic communication that accompanied the strikes. Misri’s May 7 briefing, delivered alongside military officials, represented a coordinated civil-military information operation designed to control the narrative in the critical first hours after the strikes. His insistence that the operation targeted terrorist infrastructure and avoided Pakistani military or civilian facilities established the legal and diplomatic position that India maintained throughout the subsequent crisis. Misri’s diplomatic preparation extended beyond the public briefing. In the hours before the strikes, the Indian government reportedly communicated through diplomatic channels with the United States, the United Kingdom, and other key partners, informing them that a military operation was imminent and framing it as a counter-terrorism action rather than an inter-state military assault.

Colonel Sofiya Qureshi and Wing Commander Vyomika Singh delivered the operational details during the May 7 briefing, becoming the public faces of the military dimension of Operation Sindoor. Their presentation of target maps, strike descriptions, and organizational attributions provided the evidentiary case that India offered to justify the operation. The decision to have two women officers present the strikes was noted by international media as a deliberate signal about the Indian military’s institutional evolution, though Pakistani commentators criticized it as performative. Regardless of the symbolic dimension, Qureshi and Singh provided the most detailed public accounting of the operation’s targets, weapons, and organizational rationale, establishing the factual record that subsequent analysis has built upon.

On the Pakistani side, Lieutenant General Ahmed Sharif Chaudhry, the director general of the ISPR, became the primary voice of Pakistan’s counter-narrative. Chaudhry’s briefings provided the casualty figures, damage descriptions, and attribution challenges that Pakistan used to contest India’s claims. His identification of the strike targets as mosques and civilian structures, rather than militant facilities, formed the core of Pakistan’s case that the operation constituted an unprovoked assault on civilian and religious infrastructure. Chaudhry’s communication strategy followed a pattern established during previous India-Pakistan crises: rapid public engagement, detailed casualty reporting (with figures that served Pakistan’s narrative), and consistent framing of India’s actions as aggression against a sovereign nation rather than counter-terrorism operations against designated militant groups.

Former Air Chief Marshal V.R. Chaudhari, who had overseen the Rafale induction and force modernization during his tenure as India’s air force chief, subsequently provided candid assessments of the operation’s execution. His description of the BrahMos and SCALP combination as a precision strike package that “forced them to wave the white flag” reflected the Indian military establishment’s assessment that the twenty-three minutes achieved their operational objectives. His acknowledgment that Pakistan’s subsequent drone and missile retaliation caused things to get “a little out of hand” before India’s air defense network contained the response provided a more nuanced picture than the official triumphalism of the initial briefings. Chaudhari’s retrospective comments are significant because they come from the officer who was responsible for building the capability that Sindoor deployed, giving him a uniquely informed perspective on both the operation’s achievements and its limitations.

Why Twenty-Three Minutes Changed South Asia

The twenty-three minutes of Operation Sindoor’s opening salvo did not simply punish the perpetrators of the Pahalgam massacre. They rewrote the operational assumptions that had governed India-Pakistan military interactions for over half a century. Every Indian military response before Sindoor had been constrained by an implicit set of rules: do not cross the international border, do not strike deep into Pakistani territory, do not engage multiple targets simultaneously, do not employ the most advanced weapons systems. Sindoor violated every one of these constraints in a single twenty-three-minute window, and the fact that the crisis was subsequently contained through a ceasefire negotiated within four days demonstrated that crossing these thresholds did not inevitably produce the nuclear escalation that had deterred previous Indian governments.

Deterrence implications extend beyond the India-Pakistan context. For decades, the assumption among strategic analysts globally was that nuclear-armed states could not engage in conventional military operations against each other’s territory without triggering an escalation spiral that would end in nuclear exchange. The Cold War model, refined through crises from Berlin to Cuba, held that nuclear weapons created an upper boundary on conventional conflict that neither side could safely approach. Operation Sindoor demonstrated that this boundary was more elastic than the Cold War model suggested, at least in the South Asian context. India launched cruise missiles into a nuclear-armed adversary’s territory, struck nine targets across two provinces, and the crisis was resolved through conventional military engagement and diplomatic negotiation rather than nuclear threats.

The weapons-systems implications were equally profound. The SCALP’s combat debut demonstrated that European cruise missiles could penetrate Chinese-supplied air defense networks, a finding with direct relevance for procurement decisions in Taiwan, Japan, Australia, and every other Indo-Pacific nation evaluating its defense needs against Chinese military systems. The BrahMos’s first combat use validated a jointly developed weapons system that India has been marketing aggressively to partner nations including the Philippines, Vietnam, and Indonesia. The successful deployment of indigenous loitering munitions by multiple Indian manufacturers demonstrated that India’s defense-industrial base could produce combat-effective weapons systems, not merely licensed copies of foreign designs. Defense procurement agencies worldwide watched the twenty-three minutes with professional intensity, and the subsequent arms deals, including India’s SCALP replenishment order and continued international BrahMos sales, reflected the commercial consequences of combat-validated performance.

For India’s broader strategic trajectory, the twenty-three minutes marked the moment when the country’s conventional military capability caught up with its strategic ambition. Since the 1999 Kargil conflict, Indian military planners had pursued the concept of “limited war under the nuclear umbrella,” the ability to conduct precise, calibrated conventional operations against Pakistan without triggering nuclear escalation. This concept had been tested incrementally, from the 2016 surgical strikes to the 2019 Balakot operation, with each step pushing the boundary slightly further. Sindoor did not merely push the boundary. It redefined it. Nine targets, precision cruise missiles, multiple weapons systems, simultaneous strikes across two geographic zones, and all within a nuclear-armed adversary’s sovereign territory. The distance between the 2016 surgical strikes and Sindoor was not merely quantitative but qualitative, a transition from limited cross-border raids to a full-spectrum precision strike campaign comparable in scope to the opening phases of US operations in Iraq, Libya, or Syria.

The shadow war had operated for years through covert means, with unknown gunmen on motorcycles eliminating India’s most-wanted targets in Pakistani cities. Sindoor represented the overt complement to that covert campaign, demonstrating that India could prosecute its counter-terrorism objectives through conventional military means as well. The convergence of the covert and conventional tracks into a unified deterrence architecture was, in the assessment of multiple analysts, the most significant strategic development to emerge from the twenty-three minutes.

Pakistan’s response to those twenty-three minutes, beginning with artillery shelling of Indian border towns and escalating through drone attacks, missile launches, and Operation Bunyan-un-Marsoos, demonstrated that India’s strikes were absorbed rather than deterred but also that Pakistan’s retaliation was asymmetric rather than proportional. Pakistan did not respond with its own precision strikes on Indian military infrastructure. Instead, the response combined indiscriminate artillery fire, drone intrusions, and claims of engagement that India characterized as largely intercepted by its layered air defense network. The asymmetry itself was instructive: it suggested that Pakistan lacked the precision-strike capability to replicate what India had accomplished in those twenty-three minutes, forcing Islamabad to substitute volume for accuracy and indiscriminate fire for targeted engagement.

The twenty-three minutes also carried implications for India’s relationship with its defense suppliers. France, the manufacturer of both the Rafale platform and the SCALP missile, found its most advanced export products combat-validated in a way that no marketing campaign could replicate. Russia, the co-developer of the BrahMos, gained similar validation. The S-400 air defense system’s performance during the subsequent days of Pakistani retaliation provided additional data points for Russia’s export pitch, though the disputed claims regarding S-400 interceptions at three hundred kilometers remained unverifiable. Conversely, the performance of Chinese-supplied systems in Pakistani service came under intense scrutiny, with reports suggesting that Chinese air defense radars failed to detect or engage the incoming SCALP missiles, a finding with significant implications for the global perception of Chinese military technology’s effectiveness against Western systems.

Strategic consequences of those twenty-three minutes will take years, perhaps decades, to fully manifest. The immediate military crisis was contained. The ceasefire held. The diplomatic fallout was managed. But the precedent was established: India had demonstrated the capability and the will to conduct precision strikes deep into Pakistani territory, and the world had not ended. For every future Indian government facing a provocation from Pakistan-based militants, the question would no longer be whether India possessed the capability to respond with precision strikes. That question was answered at 0400 hours on May 7, 2025. The question going forward would be whether India possessed the political restraint not to.

The operational lessons of those twenty-three minutes will be studied in war colleges worldwide for decades to come. The Indian military demonstrated that a nine-target simultaneous campaign using precision cruise missiles could be executed by a force that had never previously employed these systems in combat, that the transition from peacetime readiness to full-scale precision strike operations could be completed within days of a political trigger, and that a layered air defense system could absorb the adversary’s retaliation while the offensive operation was still generating strategic effects. These are not theoretical propositions. They are validated operational capabilities, and their validation transforms the strategic calculus for every government that might consider sponsoring or tolerating attacks on Indian interests.

For Pakistan specifically, the twenty-three minutes presented a strategic dilemma that has no clean resolution. Pakistan’s nuclear deterrent, the ultimate guarantee of the state’s security, proved irrelevant during the twenty-three-minute window because India’s strikes were precisely calibrated to fall below the nuclear threshold while inflicting maximum damage on militant infrastructure. Pakistan could not credibly threaten nuclear retaliation against an operation that destroyed terrorist training camps but avoided Pakistani military installations and government buildings. The nuclear umbrella, which Pakistan had relied upon for decades to shield its sponsorship of cross-border terrorism from Indian conventional military consequences, developed a hole precisely large enough for cruise missiles to pass through. Closing that hole, either through upgrading conventional defenses to intercept Indian precision munitions or through adjusting nuclear doctrine to lower the threshold for nuclear response, presents Pakistan with choices that are either extremely expensive or extremely dangerous, and possibly both.

Frequently Asked Questions

Q: What exactly happened during Operation Sindoor’s 23 minutes?

At approximately 0400 hours Indian Standard Time on May 7, 2025, the Indian Air Force launched precision missile strikes on nine targets across Pakistan-administered Kashmir and Pakistan’s Punjab province. The strikes targeted infrastructure belonging to Jaish-e-Mohammed, Lashkar-e-Taiba, and Hizbul Mujahideen, using a combination of SCALP cruise missiles launched from Rafale jets, BrahMos supersonic cruise missiles launched from Sukhoi Su-30MKI aircraft, HAMMER precision-guided munitions, and loitering munitions including the SkyStriker and Nagastra-1. All nine targets were engaged within a twenty-three-minute window designed to prevent Pakistan’s air defense network from mounting an effective response to any individual strike.

Q: How many targets did India strike during the 23 minutes?

India struck nine targets in total. Five were located in Pakistan-administered Kashmir: two in Muzaffarabad (the Shawai Nala camp and Syedna Bilal complex), two in Kotli District (Markaz Abbas and Gulpur camp), and one in Bhimber District (Markaz Ahl-e-Hadith, Barnala). Four were in Pakistan’s Punjab province: Markaz-e-Taiba in Muridke near Lahore (LeT headquarters), Markaz Subhanallah near Bahawalpur (JeM headquarters), and two facilities in the Sialkot District area (Mehmona Joya and Tera Katlan). Indian officials presented a map during their May 7 briefing marking twenty-one known militant camps, of which nine were selected for the strikes.

Q: What time did the strikes begin?

The strikes began at approximately 0400 hours Indian Standard Time on May 7, 2025. This pre-dawn timing was selected to minimize civilian casualties by targeting facilities during the period of lowest civilian activity. The 0400-hour launch time also aligned with optimal conditions for the electronic warfare campaign that accompanied the strikes, as reduced atmospheric activity and lower electromagnetic background noise at that hour improved the effectiveness of radar jamming operations.

Q: Were Rafale jets used in Operation Sindoor?

Operation Sindoor marked the first significant combat deployment of India’s Rafale fleet. Rafale jets operating from Ambala and Hasimara air bases launched SCALP cruise missiles against targets in both Pakistan-administered Kashmir and Punjab. The deployment represented a substantial upgrade from India’s 2019 Balakot airstrike, which relied on Mirage 2000 aircraft. The Rafale’s ability to carry and launch the SCALP from standoff distances, beyond the range of Pakistan’s air defense systems, was a critical operational enabler that previous Indian fighter platforms could not have provided.

Q: Which specific weapons were fired during the 23-minute campaign?

The primary weapons included SCALP-EG cruise missiles (ten were launched from Rafale jets according to Air Forces Monthly), BrahMos supersonic cruise missiles launched from Sukhoi Su-30MKI aircraft, HAMMER precision-guided munitions, and loitering munitions including the SkyStriker (co-developed with Israel’s Elbit Systems), Nagastra-1 (developed by India’s Solar Industries), and JM-1 (developed by India’s Johnnette Technologies). The diversity of the weapons package was designed to stress Pakistan’s air defenses across multiple threat axes simultaneously.

Q: Were the strikes launched from air, sea, or both?

The primary strikes were air-launched, with Rafale jets carrying SCALP missiles and Sukhoi Su-30MKI aircraft carrying BrahMos missiles. The Indian Navy’s Western Naval Command was reportedly involved in the operational planning and may have contributed BrahMos launch platforms from naval assets, though the specific contribution of naval platforms during the initial twenty-three-minute window has not been officially detailed. The subsequent phases of the India-Pakistan conflict involved naval deployments as well, but the opening salvo was predominantly an air force operation.

Q: How many of the nine targets were actually hit?

India claims that all nine targets were successfully struck. Pakistan disputes this, with the ISPR reporting that one of the two strikes directed at the Sialkot District area misfired and did not detonate, while the other landed in an open field causing no damage. Independent verification through commercial satellite imagery has confirmed structural damage consistent with precision munition impacts at several locations, particularly Muridke and Bahawalpur, but complete target-by-target verification of all nine sites has not been achieved due to the absence of independent ground-level access.

Q: How did India coordinate a nine-target simultaneous strike?

The Integrated Air Command and Control System (IACCS) provided the coordination backbone, fusing radar data and operational communications into a single real-time picture distributed to command centers and aircraft across the operational theater. Aircraft from multiple bases, including Ambala and Hasimara, launched weapons at times calculated so that varying time-of-flight profiles (subsonic SCALP, supersonic BrahMos, medium-range HAMMER) would produce near-simultaneous impacts across all nine dispersed targets. Electronic warfare aircraft provided jamming support to suppress Pakistani radar coverage along the strike corridors.

Q: What was the SCALP missile’s role in the operation?

Designated SCALP-EG (Systeme de Croisiere Autonome a Longue Portee) served as the primary deep-strike weapon for Operation Sindoor. With a range exceeding four hundred fifty kilometers, stealth features including a low radar cross-section, and a guidance system combining GPS, inertial navigation, and terrain-reference navigation with infrared terminal homing, the SCALP enabled Rafale jets to engage targets deep in Pakistani territory without entering the range of Pakistan’s air defense systems. Ten SCALP missiles were reportedly launched during the operation.

Q: How does the SCALP differ from the BrahMos missile?

The two missiles serve complementary rather than competing roles. SCALP is subsonic, stealthy, and long-ranged, designed to penetrate air defenses through low observability and terrain-hugging flight paths. BrahMos is supersonic (Mach 2.8 to 3), non-stealthy, and relies on speed rather than stealth to overwhelm defenses. SCALP’s advantage is in reaching distant, heavily defended targets without detection. BrahMos’s advantage is in speed, leaving the adversary with seconds rather than minutes to react. Used together, they create a multi-axis challenge that no single defensive system can optimally address.

Q: What were the loitering munitions used in Operation Sindoor?

Three loitering munition systems were employed during the operation. The SkyStriker, co-developed by Israel’s Elbit Systems and India’s Alpha Design Technologies, carries a five-to-ten-kilogram warhead over a one-hundred-kilometer range and loiters above the target area until the operator confirms the aim point. The Nagastra-1, developed by India’s Solar Industries, is an indigenous system with a fifteen-kilometer range and 1.5-kilogram warhead. The JM-1, developed by India’s Johnnette Technologies, became the first fully Indian-designed kamikaze drone used in combat. All three types made their combat debuts during Operation Sindoor.

Q: How did Pakistan respond to the 23-minute strike campaign?

Pakistan’s immediate response included artillery shelling along the Line of Control, targeting Indian border towns including Poonch. Over the following days, Pakistan launched drone attacks using domestically developed UAVs and Turkish-origin systems, fired Fatah-I and Fatah-II rockets at Indian military positions, and claimed to have launched Operation Bunyan-un-Marsoos targeting Indian military installations. An aerial engagement involving approximately one hundred fourteen aircraft from both sides occurred, described as the largest beyond-visual-range engagement in the India-Pakistan context. India’s integrated air defense network, including the S-400 system, intercepted the majority of incoming Pakistani ordnance.

Q: Was Operation Sindoor the first missile exchange between nuclear powers?

Operation Sindoor represented the first time two nuclear-armed nations engaged in confirmed missile strikes against each other’s territory in the jet age. Previous nuclear-armed confrontations, including the 1969 Sino-Soviet border clashes and the 1999 Kargil conflict, involved conventional artillery and small arms rather than cruise missile exchanges. The precedent has significant implications for nuclear deterrence theory, challenging the assumption that nuclear weapons create an absolute ceiling on conventional military operations between nuclear-armed states.

Q: What role did electronic warfare play in the operation?

Electronic warfare was critical to the operation’s success. Indian jamming aircraft suppressed Pakistani radar systems, including Chinese-supplied air defense networks, preventing them from detecting and tracking incoming SCALP and BrahMos missiles during the strike window. The Indian Air Force bypassed and jammed Pakistan’s air defense systems sufficiently to ensure that none of the primary strike weapons were intercepted during the twenty-three-minute window. The electronic warfare dimension represented a capability that India had developed extensively in peacetime exercises but had never previously deployed in a combat environment against a peer-level adversary.

Q: How does Operation Sindoor compare to the 2019 Balakot airstrike?

The two operations represent different generations of Indian military capability. Balakot employed twelve Mirage 2000 aircraft delivering gravity bombs (SPICE precision-guided munitions) against a single target in Khyber Pakhtunkhwa. Sindoor employed Rafale and Sukhoi aircraft delivering cruise missiles, precision-guided munitions, and loitering drones against nine targets across two provinces. Balakot crossed the Line of Control but struck remote border territory. Sindoor struck population centers including targets near Lahore, Pakistan’s second-largest city. Balakot’s damage assessment remained disputed for years. Sindoor’s damage was visible on commercial satellite imagery within days.

Q: What satellite imagery showed about the strike sites?

Commercial satellite imagery from providers including Planet Labs and Maxar Technologies showed structural damage, blast patterns, and debris fields at multiple target locations, particularly at Muridke and Bahawalpur. Pre-strike and post-strike comparison revealed destroyed or heavily damaged buildings consistent with cruise missile impacts. However, satellite imagery can confirm that structures were hit and destroyed but cannot determine the identity or number of human casualties, leaving the most politically significant questions (militant versus civilian dead) unresolvable through remote sensing alone.

Q: Did India kill militants or civilians in the strikes?

This remains the most contested factual question of the entire operation. India claims over one hundred militants were killed across the nine target sites. Pakistan reports thirty-one civilian casualties, including women and a three-year-old child, and denies any militant deaths. Independent verification has not been possible due to the absence of ground-level access to the strike sites. The gap between the two claims is too wide for reconciliation, and each side’s figures serve its respective political narrative. Satellite imagery can confirm structural damage but cannot resolve the casualty dispute.

Q: Was Abdul Rauf Azhar killed in the Bahawalpur strike?

Indian media reports circulated claims that Abdul Rauf Azhar, a senior JeM commander and brother of founder Masood Azhar, was killed in the strike on the Markaz Subhanallah facility near Bahawalpur. These reports remained unconfirmed at the time of publication. Masood Azhar, in a subsequent statement acknowledging the deaths of family members in the strike, did not name Abdul Rauf among the deceased. His fate remains officially uncertain, and neither Indian nor Pakistani government sources have provided definitive confirmation.

Q: Why was the Muridke compound the most significant target?

Markaz-e-Taiba in Muridke served as the organizational headquarters of Lashkar-e-Taiba and its front organization Jamaat-ud-Dawa. The two-hundred-acre compound housed the seminary, administrative offices, medical clinic, and organizational infrastructure from which Hafiz Saeed had directed LeT’s operations for three decades. Its proximity to Lahore, approximately thirty-five kilometers away, made it the most politically charged target because striking near Pakistan’s second-largest city demonstrated India’s willingness to accept the diplomatic consequences of hitting targets in densely populated regions. The compound’s designation as LeT’s headquarters was recognized by the United Nations, the United States, and the European Union.

Q: How did the 23 minutes affect global weapons procurement?

The combat performance of the SCALP, BrahMos, and Rafale during the twenty-three minutes influenced defense procurement decisions globally. India’s subsequent order of one hundred additional SCALP missiles, reportedly valued at approximately three thousand crore rupees, validated the system’s combat effectiveness. BrahMos export discussions with the Philippines, Vietnam, and Indonesia gained momentum from the missile’s successful combat debut. The Rafale’s demonstrated ability to penetrate Chinese-supplied air defense networks had implications for procurement decisions in Taiwan, Japan, and other Indo-Pacific nations evaluating their defense needs. Conversely, questions about the performance of Chinese air defense systems in Pakistani service created concerns among nations relying on Chinese military equipment.

Q: What does the 23-minute window mean for future India-Pakistan conflicts?

The twenty-three-minute window established the precedent that India possesses the capability and political will to conduct multi-target precision strikes deep into Pakistani territory. For future crises, this precedent means that Pakistan can no longer assume that Indian military responses will be limited to single targets, border areas, or conventional aircraft delivering gravity bombs. The precision-strike capability demonstrated during Sindoor’s opening minutes creates a permanent asymmetry in the deterrence equation, shifting the burden of risk management from India (which previously self-deterred from striking) to Pakistan (which must now assume that any major provocation will trigger a comparable or escalated response).

Q: Could Pakistan have defended against the strikes?

Pakistan’s air defense network, equipped with Chinese-supplied radar and missile systems, failed to intercept the incoming SCALP and BrahMos missiles during the twenty-three-minute window. The combination of electronic warfare jamming, the SCALP’s stealth characteristics, the BrahMos’s supersonic speed, and the multi-axis nature of the nine-target package appears to have overwhelmed Pakistan’s defensive capability. Pakistan subsequently claimed to have retaliated by targeting India’s S-400 system, though these claims were contested by India. The twenty-three minutes exposed a capability gap in Pakistan’s air defenses that will likely drive significant Pakistani investment in upgraded Chinese or indigenously developed defensive systems.

Q: What was the role of the S-400 during the operation?

The S-400 air defense system, purchased from Russia and delivered between 2021 and 2023, did not play a direct role during the twenty-three-minute strike phase, as the strikes were offensive rather than defensive. Its importance emerged in the subsequent days when Pakistan launched retaliatory drone attacks, missile strikes, and aerial engagements. India claimed in August 2025 that the S-400 had engaged a high-value Pakistani airborne platform at a range approaching three hundred kilometers. AirForces Monthly described this claim as prompting “ripples of disbelief” due to the absence of supporting evidence. The S-400’s actual performance during the broader conflict remains disputed, though its presence as a defensive umbrella influenced Indian operational planning by providing confidence that retaliatory strikes could be intercepted.

Q: What was the aerial engagement that followed the strikes?

Following the initial twenty-three-minute strike campaign, the Indian and Pakistani air forces engaged in what has been described as the largest beyond-visual-range aerial engagement in the subcontinent’s history. Approximately one hundred fourteen aircraft were involved, seventy-two from the Indian Air Force and forty-two from the Pakistan Air Force. Indian fighters deployed Rafales, Sukhoi Su-30MKIs, and MiG-29s, while Pakistan scrambled JF-17 Thunder and J-10C fighters armed with PL-15 long-range missiles. Neither side’s aircraft crossed the international border, engaging instead in a stand-off confrontation at distances exceeding one hundred kilometers. The aerial engagement resulted in confirmed losses on both sides, though the exact numbers remain contested between the two governments.

Q: How long did the broader India-Pakistan conflict last?

The broader conflict lasted approximately eighty-eight hours, from the initial strikes at 0400 hours on May 7 to the ceasefire on May 10, 2025. This period encompassed four distinct phases: the initial twenty-three-minute precision strike campaign, Pakistan’s retaliatory shelling and drone attacks on May 8 and 9, India’s counter-offensive strikes on Pakistani air bases on the intervening night of May 9 and 10 using fifteen BrahMos missiles, and the ceasefire negotiations through the DGMO hotline and US mediation that produced the May 10 ceasefire. The complete timeline of events is covered in the day-by-day conflict chronology.

Q: What was Pakistan’s Operation Bunyan-un-Marsoos?

Pakistan launched what it termed Operation Bunyan-un-Marsoos (Iron Wall) as its retaliatory campaign following India’s initial strikes. Pakistan claimed to have targeted Indian military installations including the Udhampur airbase, Pathankot airfield, brigade headquarters in Uri, and a BrahMos missile storage facility in Beas. Pakistan also claimed to have destroyed India’s S-400 air defense system at Adampur using hypersonic CM-400AKG missiles fired from JF-17 jets. India acknowledged that Pakistan attempted to engage targets at more than twenty-six locations but stated that the majority of these attempts were intercepted by India’s integrated air defense network.