{"id":104106,"date":"2025-07-21T21:35:27","date_gmt":"2025-07-21T16:05:27","guid":{"rendered":"https:\/\/aviationa2z.com\/?p=104106"},"modified":"2025-07-31T19:29:18","modified_gmt":"2025-07-31T13:59:18","slug":"air-india-a321-pilots-abort-take-off-at-delhi-airport","status":"publish","type":"post","link":"https:\/\/aviationa2z.com\/index.php\/2025\/07\/21\/air-india-a321-pilots-abort-take-off-at-delhi-airport\/","title":{"rendered":"Air India A321 Pilots Abort Take-off at High Speed at Delhi Airport"},"content":{"rendered":"\n

NEW DELHI-<\/strong> An Air India (AI)<\/a> flight AI2403 from New Delhi (DEL) to Kolkata (CCU) aborted takeoff after a technical issue was detected during acceleration, forcing pilots to apply brakes at a high speed of 155 km\/hr.<\/p>\n\n\n\n

The incident occurred on July 21, 2025, around 5:30 PM, at Delhi\u2019s Indira Gandhi International Airport (DEL). The aircraft was rescheduled for departure later the same evening, following standard safety protocols.<\/p>\n\n\n\n

\"Air
Photo: By Anna Zvereva – Air India, D-AZXH\/VT-RTE, Airbus A321-251NX, CC BY-SA 2.0, https:\/\/commons.wikimedia.org\/w\/index.php?curid=133549115<\/figcaption><\/figure>\n\n\n\n

Air India Pilots Abort Take-off<\/h2>\n\n\n\n

Air India Flight AI2403, scheduled from Delhi (DEL)<\/a> to Kolkata (CCU), was accelerating on the runway when pilots identified a critical technical anomaly.<\/p>\n\n\n\n

Following established Standard Operating Procedures (SOP), the cockpit crew aborted the takeoff and executed an emergency braking maneuver at 155 km\/hr.<\/p>\n\n\n\n

The airline released a statement confirming the decision to abort takeoff, citing the detection of a technical issue during the takeoff roll itself. Air India emphasized that all passengers safely disembarked and received assistance from ground staff in Delhi. The airline expressed regret over the inconvenience, reiterating that passenger safety remains its top priority.<\/p>\n\n\n\n

\"Air
Photo: Harsh Tekriwal AvgeekwithLens, Go follow him on its social media<\/figcaption><\/figure>\n\n\n\n

Other Air India Incident Today<\/h4>\n\n\n\n

This aborted takeoff marks the second safety-related event for Air India on July 21, 2025.<\/p>\n\n\n\n

Earlier in Mumbai (BOM)<\/a>, another Air India flight arriving from Kochi (COK) veered off the rain-soaked runway during landing. The aircraft suffered visible damage, including grass stuck to its rear and damage to one engine.<\/p>\n\n\n\n

Airport authorities confirmed that all passengers were safe despite the runway excursion, which also damaged signage boards and runway edge lights. The aircraft involved was grounded for inspection, and the pilots were derostered pending inquiry.<\/p>\n\n\n\n

\"An
Vistara A321neo D-AZXG VT-TVJ MSN 11323 8.5.23 XFW Photo: spottingatxfw<\/figcaption><\/figure>\n\n\n\n

Regulatory Scrutiny and Past Safety Concerns<\/h4>\n\n\n\n

These incidents come amid heightened regulatory scrutiny of Air India\u2019s safety practices. Over the past six months, the Indian Civil Aviation Ministry disclosed that nine show cause notices were issued to Air India concerning five documented safety violations. One enforcement action has been completed so far.<\/p>\n\n\n\n

Additionally, following the tragic Boeing 787 Dreamliner crash in Ahmedabad (AMD) last month, where 260 lives were lost, the Directorate General of Civil Aviation (DGCA) ordered inspections of Air India\u2019s Boeing 787-8\/9 fleet. Out of 33 aircraft, 31 underwent inspection, with minor issues found in eight jets \u2014 all rectified before returning to service.<\/p>\n\n\n\n

The DGCA continues comprehensive oversight, having executed 254 enforcement actions up to April 2025 alone. These actions range from warnings and fines to suspensions and cancellations, underscoring intensified vigilance on aviation safety.<\/p>\n\n\n\n

\"\"
Photo: By Kambui – Air India Airbus A321-211 VT-PPO, CC BY 2.0, https:\/\/commons.wikimedia.org\/w\/index.php?curid=58290476<\/figcaption><\/figure>\n\n\n\n

Government and Legislative Oversight<\/h4>\n\n\n\n

Minister of State for Civil Aviation Murlidhar Mohol confirmed to Parliament that no adverse reliability trends were observed in recent months for Air India, aside from these identified violations.<\/p>\n\n\n\n

Additionally, the government assured that investigations, including possibilities of sabotage in past accidents, are ongoing to determine root causes comprehensively.<\/p>\n\n\n\n

The heightened oversight reflects growing concerns over Air India\u2019s operational safety following consecutive incidents and the fatal Ahmedabad crash.<\/p>\n\n\n\n

The aviation regulator remains actively engaged in ensuring compliance and safeguarding passenger safety across all Indian airlines.<\/p>\n\n\n\n

\"A
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Similar Incidents<\/h2>\n\n\n\n

A United Airlines (UA)<\/a> Boeing 767-300 operating Flight UA12 from Zurich Airport (ZRH) to Chicago O’Hare International Airport (ORD) aborted takeoff at high speed on June 24, 2025.<\/p>\n\n\n\n

The aircraft, carrying 142 passengers and crew, performed the rejected takeoff at approximately 145 knots, well above the standard decision speed (V1). Emergency teams evacuated all onboard safely with no injuries reported.<\/p>\n\n\n\n

Rare High-Speed Rejected Takeoff at Zurich<\/h4>\n\n\n\n

United Airlines (UA)<\/a> Flight UA12, scheduled to depart Zurich Airport (ZRH) at 09:50 local time for Chicago O\u2019Hare (ORD), was forced to abort its takeoff roll on Runway 16 after reaching about 145 knots. The aircraft, a Boeing 767-300 registered N684UA, came to a complete stop just beyond the intersection with Runway 28.<\/p>\n\n\n\n

During the emergency stop, several main landing gear tires deflated due to the intense braking required at such speeds. Zurich Airport\u2019s emergency services promptly responded, and passengers were evacuated via mobile stairs directly on the runway surface.<\/p>\n\n\n\n

Initial communication between the UA12 flight crew and Zurich Tower revealed that the pilots initially believed they could vacate the runway after the stop. However, airport authorities instructed the aircraft to hold its position while emergency responders secured the area.<\/p>\n\n\n\n

Though United Airlines (UA) did not release detailed technical specifics, a spokesperson confirmed to Swiss media that a \u201ctechnical issue\u201d necessitated the rejected takeoff. The airline also began rebooking affected passengers on alternate flights to minimize disruption.<\/p>\n\n\n\n

The aircraft remained stationary on the runway for nearly four hours before being towed to a remote stand. Despite the incident, Zurich Airport (ZRH) managed to continue operations via alternate runways with minimal delays to overall air traffic.<\/p>\n\n\n\n

\"United
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Understanding V1 and the Significance of High-Speed Aborts<\/h4>\n\n\n\n

V1 speed is the critical decision threshold during takeoff. For the Boeing 767-300, this speed is typically below 140 knots, varying based on aircraft weight and environmental conditions. Pilots are trained to continue takeoff beyond V1 unless encountering severe, flight-critical failures.<\/p>\n\n\n\n

Flight tracking data from Flightradar24 indicated that UA12\u2019s rejected takeoff occurred between 143 and 145 knots, marking it within the rare 2% of takeoff aborts that occur at or above 120 knots. Aborting beyond V1 is uncommon and executed only when a system failure poses an immediate risk to the flight.<\/p>\n\n\n\n

Swiss aviation authorities, along with United Airlines engineers, are expected to investigate the incident to determine the exact cause behind the high-speed rejection.<\/p>\n\n\n\n

\"Emirates
Photo: Cl\u00e9ment Alloing<\/figcaption><\/figure>\n\n\n\n

Related Incidents Involving Takeoff Aborts<\/h3>\n\n\n\n

Earlier on June 8, 2025, an Emirates Airline (EK)<\/a> Boeing 777 scheduled from Chennai International Airport (MAA) to Dubai International Airport (DXB) aborted takeoff while taxiing. Pilots identified a technical anomaly around 9:50 AM IST and returned the aircraft to the gate. Despite diagnostic efforts, the issue persisted, leading to the cancellation of the flight and impacting 312 passengers.<\/p>\n\n\n\n

Similarly, on May 24, 2025, a United Airlines (UA) service from Wilmington International Airport (ILM) to Newark Liberty International Airport (EWR) aborted its takeoff due to a complete engine shutdown just before liftoff. That flight, already delayed over five hours, was rescheduled for the next morning.<\/p>\n\n\n\n

Stay tuned with us. Further, follow us on social media for the latest updates.<\/p>\n\n\n\n

Join us on\u00a0Telegram Group\u00a0<\/a>for the Latest Aviation Updates. Subsequently, follow us on\u00a0Google News<\/a><\/p>\n\n\n\n

\n
Air India 787 Pilots Abort Takeoff at High Speed at Delhi, London Flight Delayed<\/a><\/blockquote>