What happened to the Air India Express flight in Goa? India's air accident investigators have now explained it, and the answer comes down to two words: "expect backtrack." On the morning of April 3, an Air India Express Boeing 737 MAX with 171 people on board rolled onto the runway at Goa's Dabolim Airport while an Indian Navy fighter plane was taking off from the same runway. The fighter lifted off with the airliner a little over half a mile ahead. Nobody was hurt, but investigators warned that if anything had gone wrong during that takeoff, the outcome could have been catastrophic.
An Airport Shared With Fighter Planes
Dabolim isn't a typical airport. It's also an Indian Navy air base, so tourist flights to India's favorite beach state share a runway with military planes, and the Navy runs the control tower. That setup adds an extra layer of coordination between civilian and military controllers, and the report found that layer was part of the problem.
Like many smaller airports, Dabolim doesn't have a taxiway running the full length of its runway. So planes sometimes have to "backtrack," which means taxiing along the runway itself to reach the far end before turning around to take off.
What Went Wrong
Air India Express flight 1109 was heading to Delhi with 165 passengers and six crew. The pilots were told to expect a backtrack on the runway and to hold short of it until they were cleared. The first officer, a trainee, read back the taxi instruction but left out the part about holding. The ground controller didn't catch the missing words.
The plane stopped near the runway for about 16 seconds while the crew asked for their departure clearance again. In that window, the Navy cleared a fighter plane to take off. The airliner's crew was then told to switch to the Navy's radio frequency, and the captain read back the frequency and said they were entering the runway. Nobody acknowledged that call, and the plane rolled onto the active runway and began taxiing toward the end where the fighter was already speeding down.
According to the report, the captain had taken "expect backtrack" as permission to go. "Expect" is meant to be a heads-up about what's coming, never a clearance.
How Close It Got
The Navy tower spotted the airliner during the fighter's takeoff run and warned the pilot. He couldn't see the plane at first because of a slope in the runway, and by then he was already going too fast to stop safely. The fighter lifted off about 2,000 meters down the runway, with the Air India Express plane roughly 900 to 1,000 meters away, and climbed to about 450 feet as it passed over the area.
The report found there was little runway left for the fighter to abort its takeoff. In other words, once the warning came, the safest option was to keep going and hope the climb cleared everything ahead.
Who's to Blame
Investigators pointed to the cockpit first. The captain read "expect backtrack" as a clearance and didn't confirm it, and the crew entered the runway without holding or getting in touch with the Navy tower. The trainee first officer was busy with takeoff calculations and leaned heavily on the captain, who the report said seemed to be in a hurry to spend as little time on the runway as possible.
The controllers share some of the blame too. The ground controller didn't correct the incomplete readback, and the civilian and Navy controllers were on different radio frequencies and didn't know about each other's traffic. The recommendations cover all of it: more training for the captain, tighter radio language for controllers, Goa's taxiway flagged as a known danger spot and a formal system for civilian and military controllers to share information.
What It Means for You
If you're flying to Goa, this shouldn't scare you off. Close calls like this are rare, and changes are already coming to how Dabolim's controllers and crews talk to each other. Goa's newer Mopa airport, which opened in 2023, also handles a growing share of the state's flights, and it's purely civilian.
The bigger lesson is how much modern flying still depends on a few words being heard exactly right. It isn't just an India problem, either. In the US, the NTSB just released its own report on a JFK near-miss this week, where two controllers heard the phrase "one at each" in two different ways.
