IndiGo aircraft turns left after taking off from Delhi, triggers collision alert: AAIB

New Delhi: According to a preliminary report issued by the Aircraft Accident Investigation Bureau, an IndiGo aircraft operating on the Delhi-Hyderabad route turned left after takeoff and came dangerously close to another IndiGo flight from Delhi airport to Raipur in November last year. (AAIB).

IndiGo Airlines Airbus A320 aircraft (Reuters file photo)
IndiGo Airlines Airbus A320 aircraft (Reuters file photo)

The report, uploaded to the AAIB website, said the two aircraft were too close to each other, triggering the Traffic Alert and Collision Avoidance System (TCAS), which monitors the airspace around an aircraft for other aircraft equipped with appropriate transponders. , to issue collision risk warnings to pilots.

“At the nearest vertical separation (400 feet), lateral separation was 1.2 nautical miles. At the nearest lateral separation (0.2 nautical miles), vertical separation was 800 feet,” the report states. No passengers on either aircraft were injured, and the aircraft There was no damage either.

IndiGo has yet to comment on the AAIB’s preliminary findings.

According to the preliminary investigation report, one of IndiGo’s A321 aircraft was scheduled to fly flight 6E 2113 from Delhi to Hyderabad, while the second aircraft was an A320, scheduled to fly flight 6E 2206 from Delhi to Raipur.

The Delhi-Hyderabad flight received takeoff clearance from the Northern Runway System, including Runway 27, at 12 noon and took off at 12:31 noon. Cleared to climb to 8,000 feet. However, the aircraft veered left onto the take-off path of runway 29, part of the Southern Runway System, which would be used by an IndiGo flight to Raipur, AAIB said.

“Meanwhile, 6E 2206 (bound for Raipur) obtained clearance and took off from RWY 29R to climb to 4000 feet… The controller instructed it to climb to 4000 feet,” the report said.

See also  Farmers protest live updates: 'Delhi Chalo' march suspended for two days after protester dies at Haryana border

“During this sequence, a separation breach occurred between 6E 2113 and 6E 2206, triggering a current conflict alert…” the report states.