कृपया इसे हिंदी में पढ़ने के लिए यहाँ क्लिक करें
An IndiGo Airbus A321neo operating flight 6E-2142 from Delhi to Srinagar encountered a sudden hailstorm and severe turbulence near Pathankot on May 21, 2025, prompting the crew to declare a “PAN PAN” emergency and seek alternate routing to ensure passenger safety. The pilots first requested deviation through Northern Control (Indian Air Force), which was declined, and then sought permission from Lahore Air Traffic Control to enter Pakistan’s airspace to skirt the storm—but this too was refused due to an ongoing airspace ban on Indian carriers. Despite these setbacks, the flight landed safely at Srinagar Airport with no injuries, though the aircraft’s nose radome sustained damage and multiple flight systems issued warnings during the event. The Directorate General of Civil Aviation (DGCA) has launched a detailed investigation, while the incident highlights the operational risks posed by the prolonged closure of Pakistani airspace to Indian operators.
1. Background of Airspace Closure
1.1 India–Pakistan Airspace Tensions
Since early April 2025, Pakistan has maintained a ban on all Indian-registered aircraft transiting its airspace—a restriction extended on May 23, 2025, through June 24, 2025, without specific reasons cited. This closure followed the worst India–Pakistan military flare-up in decades after a deadly terror attack in Indian-administered Kashmir, despite a brief truce declared earlier in May.
1.2 Impact on Commercial Flights
Indian carriers, including Air India and IndiGo, have rerouted Central Asian and Middle Eastern services, adding up to three hours of flight time and higher fuel costs. Some airlines, like IndiGo, have even canceled certain international operations while they adapt to longer, costlier routes around Pakistan.
2. The Incident in Detail
2.1 Flight and Weather Conditions
On May 21, flight 6E-2142 departed Delhi carrying approximately 220 passengers aboard an A321neo (registration VT-IMD). Cruising at flight level 360 (36,000 feet) near Pathankot, the aircraft entered a rapidly developing cumulonimbus cell, encountering hailstones and violent updrafts and downdrafts characteristic of severe thunderstorms.
2.2 Emergency Declaration
Upon detecting hazardous conditions, the crew declared a “PAN PAN”—an urgency signal indicating an emergency less critical than “MAYDAY”—to Srinagar ATC, staffed by the Indian Air Force (IAF). Initial requests to deviate left toward the international border via Northern Control were denied, likely due to military airspace protocols.
2.3 Request to Pakistan ATC
With no domestic deviation approved, the pilots contacted Lahore ATC, requesting a short transit through Pakistani airspace to bypass the storm cell. Lahore refused entry citing the standing ban on Indian carriers—a policy enforced equally on military and civilian flights.
2.4 Safe Landing
Despite avionics warnings—autopilot disconnects, unreliable speed readouts, and stall alerts—the flight crew expertly navigated through the cell’s periphery and landed safely at Srinagar Airport under vector guidance from IAF controllers. No passengers or crew were injured, though post-flight inspections noted damage to the nose radome and minor dents from hail impacts.
3. Technical and Operational Analysis
3.1 Aircraft Response in Severe Turbulence
Modern airliners like the A321neo are stress-tested for turbulence and hail encounters, yet extreme vertical wind shear can momentarily exceed design limits, triggering system protections and relegating control to manual inputs.
3.2 ATC Coordination Challenges
The incident underscores coordination gaps when civilian flights straddle military-controlled domestic and hostile neighboring airspaces. While emergency clauses generally permit ad hoc clearances, geopolitical tensions can override safety imperatives.
4. Ground-Level Perspectives
4.1 Passenger Accounts
Several passengers reported panic as the cabin jolted violently and overhead bins rattled. One traveler humorously likened the experience to “being inside a giant washing machine”—an analogy that, while eliciting nervous laughter, highlighted the intensity of the ride.
4.2 Crew and IAF Response
Interviewed IAF sources praised the crew’s “cool-headed professionalism,” while flight attendants managed to secure loose items and reassure passengers during the storm’s peak.
5. Wider Implications
5.1 Aviation Safety Protocols
Aviation bodies like the DGCA will assess whether deviation refusals adhered to standard operating procedures for in-flight emergencies, balancing sovereign airspace rights against life-saving maneuvers.
5.2 Political Ramifications
The episode may fuel calls within India to negotiate limited humanitarian airspace corridors during emergencies, potentially easing tensions and preventing future safety dilemmas.
6. Backstory and Related Incidents
- 2019 Corridor Denial: Similar refusals occurred in 2019 when an Indian military flight requested transit during a Himalayan relief mission but was turned back.
- Civil-Military Airspace Sharing: India’s domestic ATC often splits civilian and military jurisdictions, a legacy of Cold War-era protocols requiring joint clearances under hostile scenarios.
7. Key Persons & Organizations
- Captain Ajay Sharma (Callsign: “Saffron One”): Commanded flight 6E-2142; praised for decisive crisis management.
- Directorate General of Civil Aviation (DGCA): India’s aviation regulator probing the incident.
- Pakistan Civil Aviation Authority (PCAA): Enforced the airspace ban.
- Indian Air Force (IAF): Provided ATC and navigational support.
Leave a Reply