On 2 September 2013, a B737 crew were not instructed to go around from their approach by ATC as it became increasingly obvious that an A320 departing the same runway would not be airborne in time for a landing clearance to be issued. They initiated a go around over the threshold and then twice came into conflict with the A320 as both climbed on similar tracks without ATC de-confliction, initially below the height where TCAS RAs are functional. Investigation attributed the conflict to ATC but the failure to effectively deal with the consequences jointly to ATC and both aircraft crews.
Description
On 2 September 2013, a B737-800 (VT-SPJ) being operated by Spicejet on a scheduled domestic passenger flight from Shamshabad to Dehli as SEJ234 initiated a late go around from an approach to runway 28 at destination when it became apparent that a landing clearance would not be issued because an Airbus AIRBUS A-320 (VT-IEB) being operated by Indigo on a scheduled domestic passenger flight from Dehli to Coimbatore was still not airborne from the same runway. The two aircraft subsequently came into close proximity twice as they followed similar flight paths in their respective climbs.
Investigation
An Investigation was carried out in accordance with ICAO Annex 13 procedures by a Committee of Inquiry appointed by the Ministry of Civil Aviation on 11 November 2013. It was noted that this significant event was not reported by the controllers involved using the applicable procedures.
Data from both aircraft FDRs were successfully downloaded as was that from the 737 Cockpit Voice Recorder (CVR) but relevant data from the CVR of the A320 were overwritten. ATC TWR voice recordings and the APP Radar and TWR A-SMGCS recordings were also available.
The full content of this page is available to registered users only. Please Log in or Register