Separation issue: Indigo Air and Air India

[edyvw]

OK, this one is close, and IMO, ATC issue.
But, what is Indigo decided to do Go Around? Who goes which direction at such low altitude and proximity?

 

[Kira]

No harm, no foul.
Obviously, the rules experts (thank God for them) will review.

 

[Just a civilian pilot]

That’s both a pilot and ATC mistake.

It’s the Towers ( ATC ) mistake for allowing the aircraft on final to continue its approach, and was obviously given landing clearance. It was the pilots mistake to not break off the approach and tell the tower this isn’t going to work and ask for missed approach instructions.

ATC is responsible for separating aircraft ( safety ) , and the pilots job is to keep their passengers safe.

ATC should have told the aircraft on final to “ pull up , go around” while issuing missed approach instructions ( while aircraft taking off would just fly the departure clearance they were previously given by ATC ).

Had the A320 in this video done a low altitude go around just above the runway, both aircraft TCAS would have issued a “ traffic, traffic” alert ( but TCAS RA is inhibited below around 1100 feet ) but only the aircraft behind would be in a position to decide which way to turn because the departing aircraft can’t see them ( TCAS RA would have barked orders once they were above 1100 if still too close ).

https://simpleflying.com/indigo-airbus-a320neo-lands-close-air-india-a320neo-same-runway-mumbai/

Aviation Herald….

Incident: Indigo A20N and India A20N at Mumbai on Jun 8th 2024, loss of separation on runway

By Simon Hradecky, created Sunday, Jun 9th 2024 11:39Z, last updated Sunday, Jun 9th 2024 11:41Z An Indigo Airbus A320-200N, registration VT-ISV performing flight 6E-5053 from Indore to Mumbai (India), was cleared to land on Mumbai's runway 27. At the same time an Air India Airbus A320-200N, registration VT-RTS performing flight AI-657 from Mumbai to Thiruvananthapuram (India), was cleared to line up runway 27 and subsequently for takeoff. The aircraft entered the runway at 00:44:18Z, was lined up with the runway centerline at 00:44:43Z and accelerated through 30 knots over ground at 00:45:14Z. According to ADS-B Data transmitted by both aircraft the arriving Indigo A20N was about 1.75nm short of the runway threshold and about 600 feet AGL when the India A20N reached the lined up position on the runway. The India Airbus became airborne just before the Indigo touched down at a horizontal distance remaining of about 0.35nm/650 meters/2130 feet. Subsequently the horizontal as well as vertical separation began to increase again. Indigo reported their flight 6E-5053 had received landing clearance and complied with the ATC instructions, continued the approach and landed. The occurrence was reported to India's DGCA. Air India reported their flight AI-657 was cleared to enter the runway and subsequently for takeoff, the crew continued the takeoff procedure in accordance with procedures. The occurrence was reported to DGCA. India's DGCA opened an investigation and de-rostered an Air Traffic Controller. Metars: VABB 080200Z 01005KT 2500 BR SCT015 FEW030CB BKN090 29/25 Q1006 NOSIG= VABB 080130Z 01006KT 2500 TS SCT015 FEW030CB BKN090 29/25 Q1006 TEMPO 1500 TSRA= VABB 080100Z 32008KT 2500 TS SCT015 FEW030CB BKN090 29/26 Q1006 TEMPO 1500 TSRA= VABB 080030Z 35006KT 2500 BR SCT015 FEW030CB BKN090 30/25 Q1005 TEMPO 1500 TSRA= VABB 080000Z 04009KT 2500 BR SCT015 FEW030CB BKN090 29/25 Q1005 TEMPO 1500 TSRA= VABB 072330Z 33006KT 3000 BR SCT020 FEW030CB BKN100 31/26 Q1005 TEMPO 1500 TSRA= VABB 072300Z 31005KT 3000 BR SCT020 FEW030CB BKN100 31/27 Q1004 NOSIG= VABB 072230Z 29004KT 3000 BR SCT020 FEW030CB BKN100 31/27 Q1004 NOSIG= VABB 072200Z 30007KT 3000 BR SCT020 FEW025TCU BKN100 31/27 Q1004 NOSIG=​