An IndiGo Airbus A321 Neo carrying 221 passengers aborted its Mumbai takeoff after a technical warning mid-roll, finally reaching Bhopal over two hours behind schedule.

Last-Second Abort on Mumbai Runway

An IndiGo flight bound for Bhopal had a nerve-racking Tuesday afternoon when its pilot was forced to abort takeoff at the last moment after a technical alert flashed in the cockpit system. The aircraft — an Airbus A321 Neo — had already gathered significant speed on the runway at Chhatrapati Shivaji Maharaj International Airport, Mumbai, when the decision was made to abort.

The incident unfolded around 3:50 pm, minutes after the aircraft received clearance from Air Traffic Control and began its takeoff roll. A system-level technical signal prompted the pilot to immediately apply brakes and halt the aircraft before it could get airborne. Aviation safety protocols classify this as an Rejected Takeoff (RTO) — a procedure reserved for exactly such emergencies.

221 Passengers Left Shaken

The sudden jolt of braking on a high-speed runway left many of the 221 passengers on board visibly shaken. Several described the experience as deeply unsettling. Devashish, a frequent flyer on board, said the abrupt halt felt like a hard jolt with no warning. For a few tense minutes, there was visible anxiety inside the cabin before the crew moved to reassure passengers.

Among those on board were approximately 25 pilgrims returning from Haj, whose families had gathered at Raja Bhoj Airport in Bhopal well in advance — only to face an extended and anxious wait.

Aircraft Pulled Back for Inspection

Following the abort, the aircraft was taxied off the runway to a parking bay. A team of engineers carried out a detailed technical inspection of the plane before it was cleared to fly again. Passengers were kept waiting for roughly an hour before they were informed of the situation and told a revised departure was being planned.

Delayed Departure, Late Arrival

After all checks were completed, the aircraft finally took off again at 6:26 pm — nearly two and a half hours behind its original schedule. It touched down in Bhopal at approximately 7:40 pm.

Airline Stays Tight-Lipped

IndiGo has not officially disclosed the exact nature of the technical fault that triggered the abort. The airline issued no detailed statement explaining what the system warning indicated or which component flagged the issue.

Experts Back Pilot's Call

Aviation experts, however, have broadly backed the crew's response. While a high-speed runway abort is not a routine occurrence and can itself carry some risks, specialists note that prioritising caution over schedule is the correct and necessary call under safety norms. The pilot's decision to halt rather than push through is being seen as a textbook response to an in-flight alert.

Passengers eventually reached Bhopal safely, though the unplanned delay left many — particularly the families waiting to receive returning Haj pilgrims — with a far longer evening than anticipated.