Skip to content
The Touch and GoThe Touch and Go
Air India Express 737-8 Entered Goa Runway as Navy Fighter Rolled Toward It, AAIB Finds

AI-generated illustration

Aviation Safety

Air India Express 737-8 Entered Goa Runway as Navy Fighter Rolled Toward It, AAIB Finds

India's AAIB says the 737 crew read expect backtrack as a clearance and skipped a hold-short instruction at Dabolim, while a naval fighter already past V1 lifted off roughly 450 feet above the runway.

By The Touch & Go EditorialPublished Nov 22, 12:45 AM4 min read

The gist

A 737-8 with 171 aboard entered Goa's runway without clearance as a Navy fighter took off head-on; the jet cleared it by about 450 feet.

Continuing coverage

All Runway Incursion →

An Air India Express Boeing 737-8 carrying 171 people entered the runway at Goa's Dabolim Airport without authorization on April 3 while an Indian Navy fighter jet was on its takeoff roll in the opposite direction, India's Aircraft Accident Investigation Bureau (AAIB) said in its final report. The bureau concluded that the crew treated the phrase expect backtrack as a clearance and did not comply with an instruction to hold short at the holding point. The aircraft, registered VT-BXL, was operating flight AXB1109 from Goa to New Delhi with 165 passengers and six crew. Nobody was hurt and neither aircraft was damaged.

The flight was a line training sector. The captain, with about 9,500 hours, was training a first officer with 285 hours who had never operated into Dabolim. It was the first time the two had flown together. The AAIB later cited the first officer's excessive reliance on the instructor as a contributing factor.

The investigators traced the sequence back to a controller shift change. At 07:39 the runway in use switched from 26 to 08. The Airports Authority of India (AAI) surface controller who took over at 08:00 was not told. The handover was done verbally and logged with a single dot, which signifies briefing done and all in order. As a result, he cleared the 737 to push back for a departure from runway 26.

The naval tower caught the error, and the two controllers agreed the aircraft would taxi via taxiway N2, which procedures reserve for arriving traffic, and then backtrack along the runway. At 08:12 the surface controller told the crew to expect a backtrack. Four minutes later he cleared them to taxi via N2 and hold short at the runway 08 holding point. The crew read back the taxi routing but left out the hold-short instruction, and the controller did not catch the omission. The 737 stopped on N2 for 16 seconds.

When the first officer read back the instruction to switch to the naval approach frequency of 119.7 MHz, he added entering runway at the captain's request. The surface controller did not respond because he assumed the aircraft was already talking to the Navy. At 08:17:50 the 737 rolled onto the runway without having spoken to either the tower or approach. Once on the runway, the captain asked the first officer to recalculate takeoff data for runway 08, and the first officer became absorbed in the flight management computer. In his statement, the first officer said the crew moved forward because they received no answer and the stop bars were off, and he assumed the controller was busy and had already cleared them.

At that moment the lead aircraft of a two-ship formation of single-seat fighters had already been cleared for takeoff on runway 08. Recorder data showed the pilot passed his V1 decision speed of 100 knots at 1,250 metres. The tower's warning reached him at 1,850 metres, when he was already at 130 knots, his rotation speed. The runway's slope kept the Boeing out of his sight. Knowing he had no runway left to stop, he continued and lifted off about 2,000 metres into the roll, which the naval controller put at 900 to 1,000 metres short of the 737. The fighter crossed roughly 450 feet above the runway abeam taxiway N3. The report does not name the fighter type.

Because the two aircraft were on different frequencies, the tower could warn the fighter but had no way to stop the airliner. The 737 crew called for almost two minutes without a reply, and the jet accelerated to 26 knots as it rolled down the runway. At 08:20 it halted on instruction from the approach controller, exited via N6 and held on N5 while the second fighter departed. The flight took off at 08:35 and landed in Delhi without further incident.

Dabolim is a civil enclave inside the INS Hansa naval air station. Under an agreement signed in 2023, the Navy runs the tower, approach and runway, and the AAI handles civil ground movement. Civil flights are barred from 08:30 to 12:30 Monday through Friday because of naval activity, and April 3 was a Friday. The AAIB named two probable causes: the captain's reading of expect backtrack as a runway entry clearance without seeking clarification, and the crew's failure to stop at the holding point or contact the Navy. The controller's failure to notice the incomplete readback was listed as a contributing factor.

The investigation was hampered by lost evidence. The AAI filed its report on April 6 without mentioning the fighter, and the Navy's report moved slowly up the chain of command. In the interim, videos of the event, apron camera footage and part of the hotline and VHF recordings were erased, and the Navy did not hand over the fighter's recorder data, citing technical reasons. The AAIB recommended that Air India Express train the crew and issue a circular to all pilots, that the AAI review phrases such as expect backtrack and designate N2 a hotspot, and that the Navy list the existing stop bars in the AIP, where they were shown as non-existent, and standardize frequency changes for civil traffic. It asked the DGCA to build, as a priority, a formal framework with the Armed Forces for sharing information and evidence, noting it had made the same recommendation in two earlier investigations without result. The Navy and AAI have since amended taxiway use and handover procedures, and the surface controller now confirms the runway in use and frequency with the naval tower at the start of each day.

Originally reported by Aviacionline

Share

The Daily Touch & Go

The day's best aviation news in your inbox. Free, no spam.