(DEFENCE SECURITY ASIA) — A Pakistani aviation commentator revived an unverified claim that India shot down Pakistan International Airlines Flight PK404, after a teenager’s satellite imagery video renewed interest in the 1989 disappearance of the airliner and its 54 occupants.

The video points to possible debris near the Wakhan Corridor, far north of the Gilgit–Islamabad route, while the military allegation hinges on an alleged diversion toward Indian-controlled airspace, leaving two distinct claims to be tested against the incomplete flight record.

Saad, a Pakistani aviation commentator who describes himself as a Boeing 737NG/Max type rating examiner, alleged that India’s Western Command shot down the aircraft and asserted that PIA pilots knew what happened, without producing evidence connecting the flight to an engagement.

Faseeh Ali Rajput, a 17-year-old Pakistani student, interpreted features in historical Google Earth imagery as a debris trail that might include a cockpit section, an identification that depends on scale, image integrity and a plausible route to the glacier.

The case begins with a scheduled domestic flight on 25 August 1989, when a Fokker F27-200 Friendship left Gilgit for Islamabad, made a routine radio report and disappeared in mountains where terrain could mask radar coverage and impede searches.

The aircraft carried 49 passengers, including five infants, and five crew members, all presumed dead, while the absence of recovered wreckage, flight recorders or remains has denied investigators physical evidence needed to distinguish among competing explanations.

Pakistan deployed C-130 transports, helicopters and airline aircraft with ground search parties, while the Indian Air Force independently searched on its side of the Line of Control, extending the response beyond the Pakistani search area.

The International Civil Aviation Organization recorded the disappearance in its accident reporting system, but no public investigation report establishes a cause, leaving the airliner’s presumed loss on record and the allegation of Indian military responsibility without an official finding.

The November post repeated an accusation Saad aired in September 2024, describing a flight through Babusar Pass, an identification failure and Indian recovery of debris, a sequence requiring evidence from flight tracking, military command and recovery logistics.

A failure of identification friend or foe, commonly abbreviated IFF, underpins the allegation, yet the public record contains no authenticated documentation connecting a radar contact, an identification decision and the missing civilian aircraft to an Indian air defence unit.

The strategic stakes stem from the allegation of military force against a civilian flight near the contested India–Pakistan frontier, where uncertainty about a flight track can become a dispute over responsibility, intent and what either government knew.

Defence Security Asia’s assessment weighs the departure and radio chronology, the reported search effort and the absence of recovered evidence, because each places a different limit on what can be inferred from the renewed allegation and the glacier imagery.

(READ) Pakistan’s 100,000 Merküt FPV Drone Deal With Türkiye Puts India’s Drone Defences in Focus

PK404’s Last Call and the Line of Control

PK404 departed Gilgit at approximately 07:36 local time on a flight of roughly 190 miles, scheduled to take about 55 minutes, making the first minutes of its climb the firmest part of an otherwise incomplete flight record.

At about 07:40, the crew gave a routine position report, expected to reach reporting point Bravo at 07:59 and estimated arrival in Islamabad at 08:32, placing the last known transmission well before either point in the planned flight sequence.

Accounts place the aircraft near Bunji, southeast of Gilgit along the Indus, although descriptions of the final call differ, limiting how precisely investigators can estimate the flight’s subsequent heading, altitude or distance from the Line of Control.

Contact was reportedly lost around 07:45, roughly nine minutes after departure, but that timestamp marks a loss of contact, leaving the time of any impact, the duration of any further flight and the aircraft’s final position open to investigation.

The regular Gilgit–Islamabad route did not cross the Line of Control, so the allegation of an incursion depends on establishing when the Fokker deviated from its track, where it headed and how long it remained airborne after the last call.

One published reconstruction places Bunji 80 to 100 kilometres from the Line of Control and puts the additional off-course flight at 15 to 20 minutes, figures that depend on the assumed starting point and can help test the hypothesis.

The earlier allegation placed the supposed Babusar Pass episode two days after the disappearance, a timing gap that would require independent documentation of the aircraft’s whereabouts between the morning it vanished and the alleged military engagement.

Saad named Captain Hassan Bilgrami, Captain Zubair and First Officer Sohail Iqbal in a follow-up, but accounts of Bilgrami’s training or check-flight role differ, leaving it unclear who was handling the aircraft at the time of the last transmission.

Terrain masking limited the reach of ground radar into deep valleys, so even a precise time for the loss of contact would tell investigators little about the onward path without other time-stamped observations along the route.

A reconstruction would have to reconcile the final radio transmission, a defensible track through the mountains and any claimed border crossing before a border crossing could support an assessment of whether a military encounter occurred and which forces were involved.

(READ) Turkey Approves Mecca Pact — Would It Aid Pakistan in a War With India?

India’s Western Command and the Missing Air Defence Record

The allegation names India’s Western Command without identifying a firing unit, an interceptor or a weapon, leaving its central military assertion at command level while the underlying operational decisions and the personnel or systems that would have recorded them remain unspecified.

An air defence account would need to connect detection and track continuity with identification, command decisions and use of force, since one record would leave open whether later decisions concerned the same aircraft or occurred at all.

The IFF claim raises an identification problem because a reported failure to identify a track leaves its nationality, mission and threat status uncertain, and the record contains no military communications showing how personnel classified any such contact.

In peacetime, radio warnings, an intercept or an attempt to direct a straying civilian aircraft to land would ordinarily form part of the response, and no public record links such action to PK404 or establishes what air defence crews saw.

No released radar plot, intercept communication or engagement report ties India’s Western Command to the Fokker, leaving it unclear which air defence assets, if any, were positioned or placed on alert in connection with the flight.

A missile strike could produce airborne breakup and disperse wreckage, but any comparison with terrain impact depends on a debris field, because the search outcome alone supplies neither a distribution of fragments nor damage signatures for examination.

Saad’s 2024 assertion that Indian forces retained debris adds a separate claim about recovery logistics, since moving identifiable aircraft material out of mountain terrain would involve a recovery location, personnel, transport and custody, none of which he publicly documented.

His allegation that then Pakistani Prime Minister Benazir Bhutto knew of the shoot-down would require separate evidence of what she was told, since even proof of an engagement would leave open whether intelligence reached Islamabad or how officials assessed it.

The Indian Air Force’s independent search establishes a documented role on its side of the Line of Control, but a search sortie reveals little about an earlier air defence posture or whether any Indian formation had tracked the aircraft before its disappearance.

With no public confirmation from either government, DSA assesses that the allegation can shape perceptions of military conduct through its circulation, while claims about Indian readiness, Pakistani foreknowledge or a deliberate attack remain contingent on evidence of orders, actions and intent.

The Fokker F27 and Mountain Weather

The missing Fokker F27-200, registered AP-BBF, had twin Rolls-Royce Dart 532-7E turboprop engines and had flown since 1962, giving investigators a defined configuration and operating history for assessing climb performance, maintenance exposure and possible failure modes in mountain terrain.

By its disappearance, AP-BBF had logged about 44,524 flight hours and more than 41,500 pressurisation cycles, making structural condition a legitimate line of inquiry whose relevance would depend on maintenance records and physical evidence of a specific failure.

Clear conditions at Gilgit and reports of poor weather farther along the intended route describe different parts of the operating environment, a distinction that matters for visual navigation and terrain clearance as conditions changed after departure.

Another PIA Fokker left Gilgit minutes earlier and reached Islamabad, demonstrating that the route was passable for that flight while leaving PK404’s precise track, altitude and exposure to localised mountain weather unresolved in the absence of a continuous flight record.

Controlled flight into terrain remains a plausible hypothesis because deteriorating visibility, navigational error or strong downdrafts could erode clearance over rising ground even with an aircraft under crew control, although the case record establishes none of those conditions aboard PK404.

Lee-wave downdrafts near high peaks could exceed the F27’s climb performance in some conditions, but their relevance would depend on the winds, aircraft configuration and flight path at the time, inputs the record does not establish with precision.

Sudden structural or mechanical failure could also explain abrupt radio silence, but without recovered components or flight recorder data, the combination of high airframe usage and a routine final transmission provides grounds for inquiry rather than a diagnosis.

The absence of a Mayday is consistent with several abrupt events and does little to distinguish them, particularly where terrain could also have disrupted communications or where the crew may have had little time to transmit a warning.

Claims that some PIA Fokkers carried sea-type emergency locator beacons could explain the absence of a signal, but the type and condition of equipment aboard AP-BBF remain uncertain, leaving beacon performance a secondary issue in reconstructing the disappearance.

DSA considers terrain impact and mechanical failure because either fits the known operating environment without a documented border crossing, while the comparative weight of those explanations remains provisional until a wreckage site or other diagnostic evidence is identified.

Testing Google Earth’s Wakhan Glacier Lead

Rajput’s video followed roughly two years of research with Google Earth and older satellite imagery, focusing on a glacier in the eastern Pamirs near the Wakhan Corridor, where he interpreted an apparent trail and one prominent feature as possible aircraft debris.

The proposed site lies far north of the normal Gilgit–Islamabad route, so identifying a cockpit-like shape would address only one part of the hypothesis, with the direction and duration of any post-contact diversion still requiring a credible reconstruction from the flight record.

Critics raised the possibility that the apparent objects were substantially larger than a Fokker F27, an objection best resolved against image scale and identifiable airframe dimensions because resemblance at a selected zoom level can make features of different sizes look comparable.

Suggestions of image manipulation likewise remain unverified, making the original imagery and acquisition dates important for checking whether the features persist across independent views or whether the apparent outlines depend on a particular rendering, shadow pattern or choice of image.

Glacial burial is physically plausible in the region, as the long concealment of an Indian Air Force An-12 illustrates, but that comparison establishes only that ice can hide aircraft debris for decades and supplies no direct link between PK404 and this glacier.

A terrain impact in steep snowfields could create a concentrated wreckage site susceptible to burial, whereas airborne breakup could disperse fragments, making the distribution and material of independently identified objects more useful than a claimed outline when assessing the mechanism of loss.

The glacier video and the Western Command allegation require different chains of evidence, since the first concerns the identity and location of features on the ground while the second requires an authenticated connection between the airliner and an Indian military engagement.

Even a confirmed fragment bearing a mark traceable to AP-BBF would establish the aircraft’s presence at a site before it established the cause, which would still depend on damage examination, the distribution of wreckage and any records available to reconstruct the flight.

The cross-border setting adds a logistics problem, because a field team would need to establish jurisdiction, secure access and preserve the provenance of any finds, especially if material were recovered in terrain beyond the area covered by the original Pakistani search.

The video’s immediate significance lies in identifying a location that can be checked against original imagery and the flight chronology, while its value as accident evidence depends on resolving scale and provenance before the site can credibly be linked to PK404.

Search Logistics and the Evidence Still Missing

Pakistan’s initial search brought military C-130 transports, helicopters and PIA aircraft into the operation within hours, alongside soldiers, local officials and mountaineers on the ground, a mix that shows the logistical demands of searching steep terrain around the expected track.

The C-130s and airline aircraft contributed aerial coverage, while helicopters and ground teams brought different ways of examining difficult terrain, although the search record does not establish that every valley, snowfield or glacier along plausible routes was examined at comparable resolution.

Nightfall, terrain and weather interrupted the initial search, limiting the windows for aerial observation and ground movement, while the deployment of multiple aircraft and teams measured the scale of the response without establishing how thoroughly every segment of the probable route was covered.

Search parties examined areas around Nanga Parbat, and the Indian Air Force conducted an independent search across the Line of Control, extending the documented footprint across a contested frontier without providing a common track reconstruction or an independently verified point of impact.

Pakistani officials at the time said there was “nothing to indicate foul play,” a contemporaneous judgment about the evidence then available, which records the initial assessment while leaving the accident sequence unresolved as the search drew a blank.

ICAO’s accident record preserves the occurrence and classification, while the absence of a public causal report limits what can be inferred about investigative findings, including which flight paths were considered and which civilian or military records investigators could access.

An authenticated radar track or an air traffic control recording could narrow the search area and test the border-crossing timeline, while an engagement record would carry weight only if its location, timing and track identity could be independently reconciled with PK404.

Identifiable wreckage would permit examination for structural failure, impact damage or external fragmentation, with the location and documented custody of each item crucial to weighing the findings, especially if fragments had moved in ice or had been removed from their original positions.

For India and Pakistan, the enduring civil-military issue is whether separate records of air traffic, air defence and search activity can be reconciled after a civilian aircraft vanishes near contested airspace, where any unsupported assertion of intent can acquire diplomatic weight.

The November revival leaves the families of 54 people with a contested glacier lead and an unverified military allegation, while the evidence that could change the case remains identifiable wreckage, a defensible flight track or authenticated records linking PK404 to an engagement.