(DEFENCE SECURITY ASIA) — An Indian Navy frontline warship, suspected to be the Kolkata-class guided-missile destroyer INS Kolkata, and Pakistan Navy vessel PNS Hunain collided in international waters on 15 September 2026, marking the first reported overt naval contact since the May 2025 conflict.

The contact occurred during rough conditions in the North Arabian Sea, approximately 220 kilometres east of Oman, where overlapping surveillance patrols increasingly place two nuclear-armed rivals within tactical distances capable of turning navigational misjudgement into strategic escalation.

India alleges PNS Hunain shadowed its unnamed warship, ignored repeated warnings over VHF Channel 16, accelerated suddenly and crossed the vessel’s bow from starboard before its forward section brushed the Indian ship during the high-risk manoeuvre.

Although neither major structural damage nor casualties were reported, the collision exposed how peacetime surveillance, aggressive shadowing and ambiguous command intentions can compress naval decision-making timelines, particularly when commanders operate beneath unresolved political hostility and heightened post-conflict military readiness.

India’s Ministry of External Affairs characterised the Pakistani naval conduct as “unacceptable and unprofessional,” arguing that the manoeuvre directly contravened Article 10 of the 1991 bilateral agreement requiring opposing naval vessels to maintain three nautical miles of separation.

New Delhi summoned Saad Ahmad Warraich, Charge d’Affaires of the Pakistan High Commission, on 16 September, lodged a “strong protest” and demanded that Pakistani military units exercise due care while respecting established bilateral risk-reduction mechanisms.

India simultaneously instructed its Charge d’Affaires in Islamabad to protest through Pakistan’s Ministry of Foreign Affairs, demonstrating a calibrated two-capital response designed to preserve escalation control while formally documenting what New Delhi considers a deliberate maritime safety violation.

Pakistan had not released an official explanation during the initial reporting period, leaving unanswered whether PNS Hunain’s actions reflected an authorised intimidation tactic, an attempted surveillance position, navigational error, misjudged ship-handling in rough seas or circumstances omitted from India’s account.

Although emerging assessments identify the Indian vessel as the suspected INS Kolkata, New Delhi has not confirmed its identity, while no video, photographs, Automatic Identification System tracks or bridge recordings have been released for independent reconstruction of the collision.

Those evidentiary gaps require equal scepticism toward operational claims, because the available narrative derives principally from India, while Pakistan has neither acknowledged the incident nor supplied sensor data, communications records or an alternative account capable of testing New Delhi’s allegations.

Nevertheless, physical contact between frontline units has strategic importance beyond visible damage, because it demonstrates that India–Pakistan competition now extends across an Arabian Sea battlespace where surveillance missions, expanding fleets and political signalling increasingly intersect at close range.

The central danger is therefore not this limited collision alone, but the precedent it establishes: repeated aggressive encounters could normalise unsafe manoeuvring, erode confidence-building rules and create conditions in which the next contact triggers weapons activation, reinforcement or retaliatory deployment.

(CLICK HERE): Indian Navy P-8I Poseidon Hunts Pakistan’s New Hangor Submarine Near Karachi as Arabian Sea Underwater Rivalry Intensifies

How the North Arabian Sea Encounter Unfolded

The unnamed Indian warship was reportedly conducting routine surveillance when PNS Hunain began shadowing it, a standard naval intelligence practice that becomes destabilising when the observing vessel closes distance rapidly, obstructs manoeuvring space or communicates hostile tactical intent.

According to India’s account, its bridge repeatedly transmitted warnings through VHF Channel 16, the international maritime distress and calling frequency, establishing that PNS Hunain’s crew had opportunities to recognise the developing navigational risk before physical contact occurred.

Indian descriptions maintain that the Pakistani vessel nevertheless increased speed and crossed ahead from the Indian ship’s starboard side, creating a dangerous bow-crossing geometry in which limited reaction time, hydrodynamic effects and rough seas could amplify relatively small handling errors.

The Pakistani ship’s bow then reportedly grazed or brushed the Indian warship, although official Indian terminology describes the event as a collision, a distinction that affects perceptions of severity without altering the underlying failure to preserve safe separation.

Both vessels moved away after contact, and the absence of escalation indicates that their commanders retained sufficient tactical control to disengage, conduct damage assessments and avoid allowing an already hazardous encounter to develop into weapons employment or coercive pursuit.

The Indian vessel reportedly sustained no major structural damage, casualties or loss of operational capability, suggesting low-energy contact rather than a forceful ramming event, although undisclosed damage to hull fittings, sensors or external equipment cannot be independently excluded.

PNS Hunain’s condition also remains unknown because Pakistan had issued no initial account, leaving an incomplete operational picture regarding damage, crew injuries, mission continuation or whether its command considered the encounter accidental, defensive or attributable to the Indian ship.

Rough seas materially complicate the assessment because wind, swell, yaw and reduced deck visibility can affect ship handling, yet adverse conditions simultaneously increase commanders’ obligation to maintain conservative distances and avoid rapid close-crossing manoeuvres around another warship.

Without navigational plots, bridge audio or imagery, determining responsibility requires more than political statements, because course alterations, relative velocity, collision-avoidance decisions and the precise sequence of radio exchanges would establish whether either vessel departed from recognised seamanship standards.

The incident therefore represents an unresolved navigational event with confirmed diplomatic consequences, not independently established proof of deliberate ramming, and responsible analysis must distinguish India’s detailed accusation from verified outcomes and Pakistan’s still-absent version of events.

PNS Hunain Brings Combat Capability to a Maritime Policing Hull

Indian reporting identified the Pakistani vessel as PNS Hunain, pennant number F-273, a Romanian-built Yarmook-class offshore patrol vessel commissioned in 2024 and designed to combine persistent maritime security missions with modular combat capability and extended regional presence.

Although classified principally as an offshore patrol vessel, PNS Hunain possesses anti-ship and anti-air warfare potential, giving it greater military relevance than a lightly armed constabulary platform and allowing Pakistan to employ it across surveillance, escort and maritime-interdiction missions.

Its ability to embark a helicopter expands the ship’s surveillance horizon, identification reach and targeting support, enabling the vessel to monitor surface traffic beyond direct visual range while sustaining presence across the geographically dispersed approaches of the North Arabian Sea.

That combination of endurance, aviation capacity and combat adaptability makes the Yarmook class valuable for Pakistani force posture, particularly when larger surface combatants must prioritise fleet defence, strategic escort responsibilities or readiness against the numerically superior Indian Navy.

PNS Hunain’s reported participation demonstrates how offshore patrol vessels can become frontline instruments of strategic signalling, because their lower operating costs support persistent shadowing while their weapons and military sensors preserve credible escalation options during contested encounters.

For Pakistan, deploying a newer patrol combatant near an Indian frontline warship may communicate surveillance reach and unwillingness to concede operational space, but excessive proximity risks converting presence operations into an avoidable test of command discipline and seamanship.

India’s decision not to identify its own vessel restricts comparative assessment of displacement, propulsion, turning characteristics, sensor coverage and survivability, all of which would clarify whether the contact exposed meaningful operational vulnerability or merely caused superficial damage.

The secrecy may reflect routine operational security surrounding surveillance missions, yet it also limits public scrutiny of the Indian ship’s manoeuvres and prevents analysts from determining whether its size, speed or tactical position contributed materially to the collision geometry.

Neither ship’s capabilities made physical contact inevitable, because modern navigation radar, electro-optical systems, bridge teams and radio communications should provide sufficient awareness to preserve separation, especially when the vessels were operating in international waters rather than confined channels.

The military-technical lesson concerns command judgement rather than platform performance: advanced sensors cannot prevent collision when tactical signalling encourages commanders to accept shrinking safety margins, particularly in rough seas where minor calculations can produce disproportionate strategic consequences.

Three Nautical Miles, COLREGs and the 1991 Naval Safety Framework

India’s protest centres on Article 10 of the April 1991 Agreement on Advance Notice of Military Exercises, Manoeuvres and Troop Movements, which obliges Indian and Pakistani naval ships and submarines to remain at least three nautical miles apart internationally.

Three nautical miles equal approximately 5.56 kilometres, providing a substantial buffer intended not merely to prevent collisions, but also to reduce misinterpretation, inhibit simulated attack profiles and preserve decision time when opposing military platforms encounter one another beyond territorial waters.

If PNS Hunain physically contacted the Indian warship, the ships were necessarily far inside that bilateral threshold, although establishing which vessel initiated or sustained the prohibited proximity still requires evidence unavailable in the initial public record.

India has additionally framed the bow crossing as incompatible with international collision-prevention principles, because safe navigation requires vessels to assess collision risk, communicate intentions and take timely, substantial action rather than rely upon last-second adjustments during close approaches.

The bilateral agreement and international navigation rules serve different functions: the 1991 mechanism creates a specific military separation obligation, while collision regulations establish broader responsibilities governing safe conduct, lookout, risk assessment and avoidance between vessels at sea.

New Delhi’s decision to invoke Article 10 transforms the encounter from an isolated seamanship dispute into a test of India–Pakistan confidence-building measures, signalling that ageing agreements remain politically useful when formal diplomatic relations and military trust are severely constrained.

The framework has survived because both governments benefit from predictable boundaries even during confrontation, alongside mechanisms including military communications and annual exchanges involving nuclear facilities, which preserve limited institutional continuity when substantive political dialogue remains frozen.

Yet uneven observance weakens deterrence against unsafe conduct, because commanders may treat the three-nautical-mile rule as aspirational rather than operationally binding, particularly when surveillance objectives reward proximity and neither side expects meaningful penalties beyond diplomatic protest.

A credible review would require navigation data, communications logs, commanding-officer reports and damage inspections from both ships, allowing investigators to separate intentional tactical pressure from poor ship handling, adverse weather effects or reciprocal manoeuvres that progressively reduced separation.

Absent such transparency, Article 10 will function primarily as competing diplomatic ammunition, while the deeper safety problem persists: neither navy can depend upon contested public narratives to manage encounters where seconds, metres and perceived hostile intent determine escalation.

From the 2011 PNS Babur Collision to the 2025 Conflict

The closest precedent occurred in June 2011 when INS Godavari and PNS Babur operated near the recently released merchant vessel MV Suez, producing another close-quarters encounter involving allegations of aggressive manoeuvring, physical contact and violations of maritime safety rules.

India alleged PNS Babur approached from astern at high speed and brushed INS Godavari, damaging a helicopter safety net, while Pakistan accused the Indian frigate of dangerous actions that obstructed a humanitarian escort mission around the released merchant ship.

Both governments summoned diplomats, invoked Article 10 and cited international collision-prevention obligations, establishing a pattern in which tactical confrontations generate rival legal narratives but remain contained through formal protest rather than retaliatory naval deployments or weapons employment.

The 2026 collision is more strategically sensitive because it followed the May 2025 India–Pakistan conflict, which demonstrated that terrorism allegations, precision strikes and reciprocal military action can compress escalation from political crisis into multidomain combat within days.

That crisis began after the 22 April Pahalgam attack in Indian-administered Kashmir killed 26 civilians, prompting India to blame Pakistan-based Lashkar-e-Taiba and Jaish-e-Mohammed before launching Operation Sindoor during the night of 6–7 May.

India described its precision strikes as attacks against terrorist infrastructure in Pakistan and Pakistan-administered Kashmir, while Pakistan conducted its own operations under names including Marka-e-Haq, producing four days of missile, drone and air-defence activity between nuclear-armed states.

A ceasefire emerged on 10 May through military-to-military communication and external diplomatic pressure, but both governments claimed success, leaving competing victory narratives, unresolved grievances and elevated force readiness across air, land and maritime operating environments.

The September 2026 collision therefore cannot be assessed as strategically identical to 2011, because present commanders operate in the psychological aftermath of recent combat, where surveillance activity may be interpreted through expectations of renewed coercion or pre-attack positioning.

If reports of another close-manoeuvre episode within the preceding six months are accurate, recurrence would indicate an operational pattern rather than an isolated accident, although that claim remains unconfirmed and should not be treated as established evidence.

The strategic continuity between 2011 and 2026 is nevertheless unmistakable: competitive shadowing, disputed manoeuvres and diplomatic summons repeatedly substitute for effective naval deconfliction, preserving short-term containment while leaving the underlying collision mechanism substantially unchanged.

Diplomatic Signalling, Force Posture and Escalation Risks

India’s decision to summon Saad Ahmad Warraich for approximately 30 minutes elevated the collision above routine naval communications, ensuring that New Delhi’s accusation entered the diplomatic record while demanding central Pakistani authorities restrain future military manoeuvres.

Because India and Pakistan have not exchanged ambassadors since downgrading relations over Kashmir in 2019, their Charges d’Affaires carry responsibility for crisis communication, making coordinated protests through New Delhi and Islamabad particularly important when normal political access remains restricted.

The measured nature of India’s response also matters: New Delhi announced no military retaliation, additional naval deployment or punitive operational measure, suggesting it sought accountability and deterrent signalling without creating pressure for Pakistan to respond symmetrically at sea.

Pakistan’s initial silence may reflect internal investigation, diplomatic caution or a decision to manage the encounter privately, but it also leaves India’s narrative dominant and delays clarification of whether Islamabad disputes the collision, its cause or Article 10’s applicability.

A subsequent Pakistani statement could reject India’s allegations, offer a competing navigational account or affirm private deconfliction, yet unsupported counterclaims would not resolve the evidentiary deficit created by withheld tracks, imagery, bridge recordings and warship identities.

Operationally, both navies possess enduring reasons to patrol these waters, including surveillance, anti-piracy operations, sea-lane protection and regional presence, ensuring that diplomatic hostility cannot be managed simply by separating their fleets into distinct geographic operating zones.

The North Arabian Sea links energy routes, Gulf access and approaches to both countries’ maritime infrastructure, making naval awareness strategically indispensable while simultaneously producing a persistent logistics footprint of patrol ships, helicopters, replenishment requirements and supporting surveillance networks.

As these patrol patterns overlap, commanders must distinguish legitimate observation from intimidation, because shadowing can reveal readiness and movement while aggressive bow crossings may simulate attack geometry, challenge navigational freedom or provoke defensive combat-system responses.

The most dangerous future scenario would involve collision damage, casualties or perceived hostile preparations prompting ships to activate fire-control radars, manoeuvre escorts or request air support, creating an escalation chain faster than diplomatic channels could reliably contain.

Preventing that outcome requires disciplined adherence to separation rules, bridge-to-bridge communication and military hotlines, because the 15 September contact demonstrates that even without gunfire, unsafe manoeuvring can destabilise force posture between nuclear-armed adversaries.

(CLICK HERE): Pakistan Navy’s New Jet LRMP Fleet Signals Major Indian Ocean Power Shift, Expanding Maritime Surveillance and Anti-Submarine Reach

Why This Collision Changes the Arabian Sea Battlespace

The immediate physical consequences were limited, but the operational message is significant: Indian and Pakistani naval units are conducting surveillance close enough for direct contact, indicating a more crowded and politically charged Arabian Sea security environment after the 2025 conflict.

Every future encounter will now carry the memory of this collision, potentially encouraging more conservative navigation but also increasing suspicion that routine course changes, helicopter operations or radar emissions represent deliberate attempts at coercion, intelligence collection or tactical positioning.

India’s invocation of the 1991 agreement seeks to reinforce a rules-based buffer around its warships, while Pakistan’s eventual response will reveal whether both governments still share a common interpretation of the mechanism governing military proximity in international waters.

If Islamabad accepts the framework while disputing the facts, bilateral naval risk reduction remains recoverable; if it rejects India’s interpretation or ignores repeated alleged violations, confidence in Article 10 could erode precisely when fleet interactions are becoming more frequent.

For regional planners, the episode highlights how logistics and persistence shape strategic competition, because vessels capable of remaining deployed longer generate more surveillance opportunities, but also multiply the number of encounters requiring disciplined crews and reliable command oversight.

PNS Hunain illustrates Pakistan’s effort to field flexible, helicopter-capable patrol combatants, while India’s undisclosed frontline vessel reflects New Delhi’s broader maritime surveillance posture, creating asymmetric forces whose mission profiles nevertheless converge across strategically important international sea lanes.

Neither government benefits from uncontrolled escalation at sea, where damage or loss could demand visible retaliation, disrupt commercial confidence and divert naval assets from wider missions, including piracy suppression, Gulf engagement and protection of maritime economic lifelines.

However, mutual interest in restraint does not eliminate tactical risk, because local commanders must interpret incomplete information under time pressure, while national leaders may later frame ambiguous actions through political narratives designed for domestic and international audiences.

The collision consequently changes the battlespace by demonstrating that escalation can begin without missiles or gunfire, emerging instead from surveillance geometry, speed, distance and command decisions made aboard individual ships operating beyond immediate political supervision.

Whether the episode remains contained will depend upon Pakistan’s official response, bilateral communication and future behaviour at sea, but the warning is already clear: ageing safeguards must govern increasingly capable fleets before another close encounter produces irreversible consequences.