What happened to the IndiGo aircraft that was hit by a hailstorm last month and lost its nose?

On May 21, 2025, an IndiGo flight operating as 6E-2142 from Delhi to Srinagar encountered an intense and unexpected hailstorm while cruising near Pathankot. The Airbus A321 aircraft, which had 227 people onboard including passengers and crew, faced severe turbulence and hail impact during the journey. While flying at around 36,000 feet, the plane’s nose cone—also known as the radome—was violently battered by hailstones. The radome is a critical part of the aircraft housing weather radar systems, and the impact was significant enough to cause visible dents and structural damage.

The hailstorm not only damaged the aircraft’s structure but also triggered multiple alerts and warning messages in the cockpit. These included an Angle of Attack (AoA) fault warning, autopilot disconnection, stall alerts, and other ECAM (Electronic Centralized Aircraft Monitor) notifications. The pilots quickly took manual control and tried to stabilize the aircraft. As per available flight data and ADS-B telemetry, the plane experienced a rapid descent, with initial reports suggesting rates as steep as 8,500 feet per minute, although later data points to around 2,700 feet per minute.

The pilots requested a deviation from their flight path to avoid the storm. However, both Indian Air Force Northern Control and Pakistani Lahore ATC reportedly denied the deviation due to restricted airspace protocols. With no alternative, the pilots had to ride through the storm. They declared a “PAN PAN” emergency call, indicating urgency without immediate danger to life, and continued toward Srinagar. Despite the chaos and the degraded performance due to equipment failure, the aircraft was brought down safely. It landed in Srinagar around 6:30 PM without injuries reported among passengers or crew.

Visuals after landing showed the extent of the damage. The radome was crumpled and dented, appearing as though it had been pummeled by a hammer. There was significant concern about how the aircraft was able to continue operating with such visible structural compromise, but aviation experts noted that the airframe remained intact, and the pilots followed procedures correctly. The aircraft was immediately grounded in Srinagar for detailed technical assessment and repairs, and remains out of service until certified airworthy by IndiGo’s engineering team in coordination with aviation regulators.

The Directorate General of Civil Aviation (DGCA) has taken note of the incident and launched a formal investigation. IndiGo has been asked to submit a comprehensive report detailing the sequence of events, onboard system failures, crew decisions, and communications with ATC. As part of the review, questions are being raised about India’s and Pakistan’s refusal to allow emergency airspace deviation, especially in such dire circumstances. This situation reignites debates around whether emergency routes should always be cleared regardless of military or political tensions, at least on humanitarian or safety grounds.

Aviation analysts have stated that while the crew showed excellent crisis management, the incident could have turned catastrophic under slightly different conditions. Weather avoidance through radar, early route deviation, and better satellite forecasting are being suggested as key areas of improvement. The larger industry view also points to how climate change is contributing to more erratic and violent weather events, including sudden hailstorms at high altitudes.

This incident has prompted internal reviews within IndiGo and across Indian aviation circles. There is increasing support for a revision of inter-border airspace policies to accommodate real-time weather challenges. Some experts have also argued for equipping commercial jets with more advanced radome material that can better withstand severe hailstorms. For passengers, it was a terrifying yet safe experience, with several praising the airline crew for their calm and professionalism.

The first sign of trouble came when the aircraft, cruising at 36,000 ft, began shaking in a sudden collapse of calm. A hail squall had breached the planned flight path near Pathankot, causing the autopilot to disengage. As the aircraft barreled through icy clouds, cracking thunder clapped against its fuselage. Inside, passengers clung to armrests as jolts pitched the plane unpredictably.

Pilots immediately requested a detour—but military authorities controlled the airspace, and both the IAF and Pakistan ATC refused ⟨cite⟩turn0search0⟩turn0search6⟩turn0search8⟩. With few options, the crew chose to press forward, the fastest route toward departing the storm still sweeping ahead. Behind the cockpit doors, the flight crew worked methodically, running emergency checklists and collaborating to maintain aircraft stability.

At one point, the aircraft tumbled rapidly—descent rates reached nearly 8,500 ft/min according to preliminary data ⟨cite⟩turn0search0⟩turn0search2⟩turn0search3⟩. Yet the pilots maintained control, manually adjusting pitch and power as they navigated through violent turbulence. Multiple system warnings blared: Angle of Attack faults, stall alerts, speed warnings, and even a switch to Alternate Law mode ⟨cite⟩turn0search0⟩turn0search1⟩turn0search6⟩turn0search8⟩.

Meanwhile, hailstones pelted the nose radome relentlessly. The composite fairing cracked and crumpled, ice-impact fractures spreading like spiderwebs ⟨cite⟩turn0search6⟩turn0search7⟩turn0search8⟩, yet radar functionality was lost. Despite this, the cabin remained sealed, and passengers experienced only the thunderous sound of ice rebounding against metal—a terrifying symphony, but no structural compromise to the pressurized fuselage.

Once clear of the storm cell, pilots declared a “PAN PAN” (a situation requiring assistance without immediate danger), requesting radar vectors toward Srinagar ⟨cite⟩turn0search2⟩turn0search8⟩turn0news9⟩. Air traffic services—both civil and military—guided the descent path, ensuring a safe runway alignment. The aircraft had easily over twice its normal rate of descent, and yet emerged from the weather strong enough to land under autothrust.

Upon landing around 6:30 PM, rescue crews noticed the battered radome. Its once-smooth contour was now punctured with dents, shards, and impact scars. IndiGo engineers grounded the jet for detailed inspections, replacing the radome before re-certification ⟨cite⟩turn0search6⟩turn0search7⟩. The DGCA opened an investigation, poring through flight-data and cockpit recordings. They will assess weather forecasting protocols, ATC refusal to deviate, and crew decision-making under pressure.

The incident has sparked broader concern in the aviation community. Pilots, regulators, and meteorologists are discussing whether existing systems—onboard radar, satellite weather, and ATC guidance—were sufficient, or if upgrades are needed. Some argue for emergency weather corridors, especially when airspace restrictions become life‑critical ⟨cite⟩turn0search0⟩turn0search3⟩turn0search6⟩.

Passengers praised the flight crew for their calm professionalism under sudden, overwhelming conditions. Social media posts thanked the airline and crew for their composure and swift action during what was called “a narrow escape.” Despite the violent event, all 227 aboard disembarked safe.

As for the aircraft, its makeover awaits. With a new radome fitted, systems retested, and certification by both IndiGo and DGCA, it is expected to return to service in the coming weeks. But it will always bear the memory of that storm and the hail that “stole the nose”—a reminder of how unpredictable weather can be, even modern planes no match for nature’s fury.

• Group Media Publication

1. Construction, Infrastructure and Mining   
2. General News Platforms – IHTLive.com
3. Entertainment News Platforms – https://anyflix.in/