Air India Runway Excursion at Mumbai Airport: A Comprehensive Analysis of Safety, Infrastructure, and Operational Implications

On July 21, 2025, Air India flight AI2744, an Airbus A320neo (registration VT-TYA), overshot the runway during landing at Chhatrapati Shivaji Maharaj International Airport (CSMIA) amid torrential rainfall, resulting in a runway excursion that caused minor damage to the aircraft and primary runway infrastructure. All 164 passengers and crew disembarked safely without injuries, though the incident led to the grounding of the aircraft, activation of the secondary runway, and an ongoing investigation by India’s Directorate General of Civil Aviation (DGCA).

This event occurred against the backdrop of Mumbai receiving 115mm of rainfall within 12 hours, with the India Meteorological Department (IMD) issuing an orange alert for the region. The incident underscores the complex interplay between seasonal weather challenges, runway safety protocols, and aviation infrastructure resilience. It also arrives at a sensitive time for Air India, following other recent operational disruptions within the Airlines.

Detailed Chronology of the Incident

Sequence of Events

Flight AI2744 departed Kochi International Airport at 7:43 AM IST under standard operating conditions. As the aircraft began its descent into Mumbai around 9:27 AM IST, it encountered heavy rainfall that severely reduced visibility and runway friction. Upon touchdown on Runway 09/27, the aircraft experienced hydroplaning, causing the right main landing gear to veer off approximately 16 to 17 meters into unpaved terrain.

Despite three burst tires and damage to the right engine nacelle, the flight crew managed to regain control and taxi the aircraft to the gate without requiring an emergency evacuation. No injuries were reported among the passengers or crew, and the aircraft was immediately grounded pending further inspection.

Initial observations suggested the aircraft’s deceleration was compromised due to water accumulation on the runway. The auto-brake system was reportedly set to “MED” rather than “MAX,” a configuration now under review by the DGCA as part of its ongoing investigation into crew decision-making under adverse weather conditions.

Emergency Response and Operational Continuity

Airport emergency services responded swiftly, arriving at the site within 90 seconds of the incident. CSMIA’s Airport Rescue and Fire Fighting (ARFF) units secured the area and began initial inspections. Minor surface damage was identified, including the destruction of four edge lights and damage to signage panels.

Runway 09/27 was temporarily closed for safety assessments and minor repairs. To maintain operational flow, air traffic control activated the secondary Runway 14/32. This quick switch helped minimize flight disruptions and avoid cascading delays across the network.

Both pilots were de-rostered as per standard procedure, and the DGCA commenced a formal inquiry, focusing on human performance, aircraft systems, and meteorological influences. The aircraft remained grounded while undergoing detailed inspections for structural and engine damage.

Technical Analysis of Contributing Factors

Meteorological Determinants

The incident occurred during an intense monsoon period, with rainfall rates exceeding 100mm/hour. Mumbai’s primary runway has a known vulnerability to water accumulation due to its slope and drainage limitations. This can significantly reduce braking efficiency, especially during peak monsoon months.

Runway grooving and drainage systems at CSMIA are designed to handle moderate precipitation. However, on this occasion, the rainfall exceeded the system’s capacity. The IMD had issued an orange alert, indicating severe weather risks, yet the flight continued its scheduled landing.

Braking coefficient degradation on wet runways is a known risk. Aircraft systems like the Airbus A320neo’s auto-brake rely on real-time data, but the effectiveness is limited when water depth exceeds 3mm. Weather station data around the airport confirmed such conditions at the time of landing.

Aircraft Performance Limitations

The Airbus A320neo involved in the incident had no recorded technical anomalies. However, performance margins are significantly affected by wet runway conditions. The typical landing distance required for this aircraft under dry conditions is approximately 1,380 meters, but that margin is reduced substantially when the runway is contaminated.

Investigators are reviewing whether the flight crew received updated runway condition reports during their final approach. Surface movement radar had detected increasing water accumulation, raising questions about the adequacy of communication between air traffic control and the cockpit.

Damage to the engine nacelle suggests an asymmetrical application of reverse thrust, potentially as a corrective measure during the excursion. Full data from the flight data recorder will be necessary to confirm this hypothesis.

“Runway excursions account for over 20% of aviation accidents globally, with 80% occurring during landing phases.”, IATA Safety Report

Regulatory and Safety Framework

Runway Excursion Risk Landscape

Runway excursions are among the most frequent types of aviation incidents. Globally, they comprise about 21% of all Accidents, with a significant portion occurring during landing. In India, the monsoon season exacerbates these risks, particularly at high-traffic airports like Mumbai.

CSMIA’s intersecting runway configuration poses additional challenges during recovery operations. Since 2010, over two-thirds of runway excursions at the airport have occurred between June and September, aligning with the monsoon season.

Despite their frequency, most runway excursions result in no fatalities. This is largely due to improved aircraft design, better crew training, and rapid emergency response. However, the economic and operational impacts are often substantial.

DGCA’s Evolving Safety Protocols

In response to a 2024 runway collision in Japan, the DGCA implemented new guidelines aimed at enhancing safety during low-visibility and wet runway operations. These include real-time friction index broadcasting and mandatory stabilized approach checks.

Following the July 2025 incident, the DGCA is auditing Air India’s monsoon operating procedures. Key areas under review include landing weight restrictions, go-around protocols, and the use of braking configurations under adverse weather conditions.

The regulator’s focus extends to airport infrastructure as well. There is growing pressure to update older drainage systems and implement the ICAO’s Global Reporting Format (GRF) for runway condition assessments across Indian airports.

Infrastructure and Economic Implications

Runway Damage and Repair Costs

The excursion caused localized damage to a 23-square-meter section of Runway 09/27. Repairs involved resurfacing with polymer-modified asphalt and replacing damaged lighting and signage. While the direct repair costs are relatively low, the indirect costs due to runway downtime are significant.

Each hour of primary runway closure at CSMIA can cost up to $81,000 in operational delays. To mitigate disruption, the airport authority scheduled repairs during nighttime hours and activated contingency funds from its annual maintenance reserve.

These costs highlight the importance of preventive infrastructure upgrades. With climate change increasing the frequency of extreme weather events, airports must invest in more resilient systems to handle higher rainfall volumes.

Operational Impact on Air India

The aircraft involved, valued at over $100 million, remains grounded. If engine ingestion damage is confirmed, repair costs could exceed $2 million. In the meantime, Air India has had to cancel or reschedule multiple flights, affecting thousands of passengers.

This incident adds to operational pressures for the airline, which has faced a series of technical and weather-related disruptions in recent months. Analysts note that while safety was maintained, the reputational and financial toll is non-trivial.

The airline’s response, including timely communication and re-accommodation of affected passengers, will be critical in maintaining customer trust and regulatory compliance.

Broader Aviation Context

Monsoon Preparedness in Indian Aviation

Mumbai’s drainage capacity, currently around 50mm/hour, was overwhelmed by the 115mm recorded in 12 hours on the day of the incident. IMD forecasts suggest that such extreme weather events will become more common in the coming years.

Comparative benchmarks show that airports like Singapore Changi have invested heavily in drainage and water management systems capable of handling higher rainfall volumes. Indian airports may need to follow suit to maintain operational resilience.

The Airports Authority of India has outlined a $120 million plan for monsoon preparedness, including runway grooving and friction-measuring equipment. Implementation timelines will be crucial in determining future safety outcomes.

Technology and Safety Systems

Advanced safety systems like the Runway Overrun Prevention System (ROPS) and Runway Awareness and Advisory System (RAAS) can significantly reduce the risk of excursions. These systems provide real-time alerts and performance calculations during approach and landing.

Currently, adoption of such systems in Indian commercial fleets is limited. Regulatory frameworks do not mandate their use, although post-incident evaluations may prompt reconsideration.

Cost-benefit analyses suggest that while retrofitting aircraft with these systems is expensive, the potential savings in avoided accidents and hull losses are substantial. Incentive programs could help accelerate adoption.

Conclusion and Forward Pathways

The Air India runway excursion at Mumbai underscores the multifaceted nature of aviation Safety, where weather, infrastructure, human factors, and technology all intersect. While the incident ended without injury, it exposed vulnerabilities that require urgent attention.

Looking ahead, a combination of infrastructure upgrades, regulatory reforms, and technology adoption will be essential. As climate variability increases, so too must the agility and preparedness of India’s aviation ecosystem. The DGCA’s final report, expected later this year, will be instrumental in shaping future policy and operational standards.

FAQ

What caused the Air India plane to overshoot the runway?
The aircraft encountered heavy rainfall during landing, leading to hydroplaning and reduced braking efficiency, which caused it to veer off the runway.

Were there any injuries in the incident?
No, all 164 passengers and crew members were safe, and the aircraft taxied to the gate without requiring evacuation.

What is DGCA doing in response?
The DGCA has launched an investigation, grounded the aircraft, and de-rostered the pilots. It is also reviewing Air India’s monsoon operating protocols.

Sources:
The Hindu,
India Meteorological Department,
IATA,
DGCA India,
Mumbai International Airport (CSMIA)