The Dabolim airport runway incursion involving an Air India Express flight and a Naval aircraft was not only a communication failure between a cockpit and air traffic control. The Aircraft Accident Investigation Bureau’s final report points to a wider institutional problem: commercial aviation and defence operations sharing airport infrastructure without a sufficiently formal system for exchanging information, coordinating procedures and managing operational risk.
The incident occurred on April 3, 2026, at the Navy’s Dabolim Airport in Goa. An Air India Express flight scheduled to operate to Delhi entered an active runway while a Naval fighter was rolling in the opposite direction. The aircraft did not collide, but the AAIB classified the event as a near miss. The report attributed the occurrence to misunderstanding and miscommunication between the flight deck and air traffic control.
The central concern raised by the report is that Dabolim is not an exclusively civil airport. Commercial flights operate from a defence airfield, creating an environment in which two aviation systems must function together: the civilian framework involving the Directorate General of Civil Aviation, the Airports Authority of India and commercial airlines, and the operational requirements of the defence establishment. The AAIB has sought a formal framework for collaboration between the DGCA, the investigation bureau and defence authorities on a priority basis.
That recommendation matters because the problem identified by the report is not limited to the actions of one flight crew or one controller. It concerns how information moves between institutions that share a runway but may follow different operating procedures, communication arrangements and access protocols. The AAIB has specifically called for the exchange of unclassified information and evidence to support the investigation of incidents and accidents.
In the Dabolim occurrence, the immediate failure was operational clarity. The Air India Express aircraft entered an active runway while the Naval fighter was rolling. The report says the flight deck and air traffic control misunderstood one another. After seeing the Navy aircraft at lift-off, the pilot-in-command reportedly told the trainee first officer that the fighter had conducted a low pass. The cockpit flight recorder recording was cited by the AAIB in describing this exchange.
The report’s recommendations show how a seemingly narrow phrase or incomplete read-back can become a safety risk when aircraft are moving in a constrained shared environment. The AAIB has asked the Airports Authority of India to issue a circular sensitising air traffic controllers to the use of standard phraseology. It has also asked the authority to review phrases such as “expect backtrack”, which ground controllers may use but which can be misinterpreted as an instruction to enter a backtrack.
The recommendation is not a call to remove operational language from aviation communication. It is a warning that wording must be understood in the same way by the controller and the flight crew. The AAIB has instructed air traffic controllers to listen carefully to read-backs and correct factual errors or apparent misunderstandings. In practical terms, the report places emphasis on the final confirmation loop between an instruction and the action that follows it.
The airport’s physical layout also forms part of the safety picture. The investigator has asked that a taxiway at Dabolim be considered a hotspot because it is close to the bays of the civil apron and carries an increased probability of potential ground collisions and runway incursions. This recommendation links the incident to the design and operational management of airport space, rather than treating it solely as a communication lapse.
Shared-use airports can be especially dependent on precise coordination because civil apron activity, taxiing aircraft, runway movements and defence operations may converge within a limited area. The supplied AAIB findings do not establish that the airport’s layout caused the incident. They do, however, identify the taxiway’s proximity to the civil apron bays as a condition that warrants specific attention.
The Navy has also been advised to publish the installation and usage of stop bars at Dabolim. Stop bars are part of the visual and procedural controls used to regulate movement around controlled aircraft areas. The recommendation indicates that the safety system needs clear visibility not only in physical infrastructure but also in the published procedures governing its use.
The AAIB has further asked the Navy to consider a standard frequency changeover procedure for civil traffic moving from the ground frequency to the tower frequency. The report connects the recommendation to the risk of recurring confusion over which frequency should be used. This is another example of how airport safety depends on coordination at institutional boundaries: the aircraft may be operated by a civilian airline, but its movement takes place within an airfield whose wider operations involve the defence establishment.
The report also assigns corrective actions to the flight crew and airline. The crew has been asked to undergo counselling, while the pilot-in-command is to receive training on the safety lapses that resulted in the runway incursion, described by the AAIB as arising from a lack of operational clarity and communication misses. The airline has been asked to issue a circular to sensitise all crew members to the lapses encountered in the occurrence.
These recommendations create three distinct layers of response. The first concerns individual and airline behaviour: training, counselling and crew awareness. The second involves air traffic control: phraseology, read-back discipline and correction of misunderstandings. The third concerns airport governance and infrastructure: coordination between civil and defence authorities, taxiway risk assessment, stop bars and frequency changeover procedures.
That layered approach is important because aviation incidents rarely arise from a single isolated failure. In this case, the AAIB report describes a chain involving an active runway, a moving Naval aircraft, an interpretation of controller communication, the proximity of airport movement areas and the absence of a formal collaboration framework that the bureau now wants established. The supplied report does not state that every link in this chain was equally responsible, but its recommendations clearly spread across people, procedures, infrastructure and institutions.
The governance issue is particularly significant for airports where civil and defence operations coexist. The AAIB has not proposed an informal coordination mechanism or a one-time review. It has sought a formal framework between the relevant civil aviation and defence authorities. That distinction suggests that the bureau sees the need for a repeatable system rather than case-by-case communication after an incident has occurred.
Such a framework would also affect how future incidents are investigated. The AAIB’s recommendation for the exchange of unclassified information and evidence addresses the investigative stage, but it also has a preventive dimension. Better access to operational information can help investigators reconstruct events, identify recurring hazards and determine whether a problem lies in communication, procedure, infrastructure or institutional coordination.
The Dabolim case therefore raises a broader question about how India manages shared aviation infrastructure. The immediate event involved two aircraft on or near the same runway environment. The underlying issue is how civilian and defence authorities define responsibilities when commercial traffic uses a defence airfield, and how those responsibilities are translated into instructions that pilots and controllers can interpret without ambiguity.
The AAIB report confirms the occurrence, identifies the runway incursion as a near miss and sets out recommendations for the Airports Authority of India, the Navy, the flight crew and the airline. It does not, in the supplied material, provide a wider statistical comparison with other shared-use airports or establish whether similar incidents have occurred elsewhere. Those questions remain open.
What is clear is that the corrective response cannot stop at retraining the individuals involved. The report’s recommendations point towards a more integrated safety architecture: formal civil-defence coordination, unambiguous phraseology, disciplined read-backs, clearer frequency transitions, attention to taxiway hotspots and properly published stop-bar procedures. The next test will be whether those recommendations become standard operating arrangements at Dabolim rather than remaining a response to one near miss.
