Air Traffic Control Archives

NSIB Preliminary Report Finds Safety Gaps In Enugu Air Benin Airport Runway Overrun

Aviation Today News Desk / August 25, 2026

Benin City, Nigeria: The Nigerian Safety Investigation Bureau (NSIB) has identified several safety gaps at Benin’s Oba Akenzua II Airport […]

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Incidents

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Aviation Today News Desk / August 17, 2026

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after

New Mexico, United States: The U.S. National Transportation Safety Board (NTSB) has revealed that a U.S. military GPS jamming exercise was underway when a Beechcraft C90 King Air air ambulance crashed into mountainous terrain near Lincoln, New Mexico, killing all four people on board. The findings were released in a preliminary report, meaning investigators have not yet determined the probable cause or contributing factors of the accident. The accident occurred at 0015 local time on May 14, 2026, after the aircraft, registered N249CP and operated by Generations Jets under Part 135 as an air ambulance flight, departed Roswell Air Center (ROW) to Sierra Blanca Regional Airport (SRR) in Ruidoso to pick up a patient for transport to Albuquerque. The flight was crewed by two pilots and carried two flight nurses employed by Trans Aero Medical Services. The crash claimed the lives of Captain Keelan Clark, First Officer Ali Kawsara, and flight nurses Sarah Clark and Jamie Novick. According to the NTSB, GPS jamming activities conducted by the U.S. military were active over the accident area during the flight. Shortly after departure, the aircraft was cleared to 12,000 feet under instrument flight rules (IFR). At 0000:26, air traffic controllers advised the crew that the aircraft had climbed to 13,000 feet, 1,000 feet above its assigned altitude. The pilot responded that the aircraft had lost GPS capability and requested headings from air traffic control. The crew initially requested the RNAV (GPS) Runway 24 approach into Sierra Blanca Regional Airport but, after losing GPS navigation, switched to the ILS Runway 24 approach. At 0001:17, the Albuquerque Air Route Traffic Control Center (ARTCC) controller contacted the operations supervisor and requested that the military stop the GPS jamming. The aircraft continued north while controllers provided radar headings. During the same period, three other aircraft also reported GPS outages, with one crew requiring additional assistance to identify a ground-based navigation aid. At about 0005, the ARTCC operations supervisor again contacted the military to stop the jamming, after which ADS-B transmissions returned to normal. At 0008, the accident crew reported having Ruidoso in sight and requested to continue visually. Controllers cleared the aircraft for a visual approach and advised the crew they could cancel IFR after descending below 9,000 feet or after landing. The pilots acknowledged the clearance and stated they would cancel IFR "in just a couple of minutes." No further radio transmissions were received. The aircraft then turned southwest toward Sierra Blanca Regional Airport. Between the airport and the aircraft lay the Capitan Mountains, which rise to 10,201 feet. Around 0010, after being informed the aircraft was on a visual approach, the military resumed the GPS jamming exercise. The King Air began descending before briefly climbing again. The final Spidertracks data point recorded the aircraft at 9,823 feet, 150 knots ground speed, and a heading of 250 degrees. Seconds later, it struck terrain at an elevation of about 9,950 feet, approximately 730 feet east and 230 feet below the Capitan Mountains Summit Radio Facility, triggering a post-impact fire that ignited a forest fire. Investigators also found that the crew's ForeFlight weather briefing included active NOTAMs warning that military GPS jamming would affect GPS, WAAS, GBAS and ADS-B navigation over a wide area encompassing the accident flight path and altitudes. Additional NOTAMs advised that Sierra Blanca Regional Airport's automated weather observation system (AWOS) was out of service, while the weather briefing indicated no METAR or TAF was available for the destination airport. The airport's published RNAV and ILS Runway 24 approach procedures also state that the procedures are not authorized when the local altimeter setting is unavailable. The NTSB emphasized that the report is preliminary and subject to change, and that it does not determine the accident's probable cause.

Investigation

Military GPS Jamming Was Underway During Fatal Air Ambulance Flight, NTSB Says

Aviation Today News Desk / August 6, 2026

New Mexico, United States: The U.S. National Transportation Safety Board (NTSB) has revealed that a U.S. military GPS jamming exercise

Sydney, Australia: The Australian Transport Safety Bureau (ATSB) has launched an investigation into a serious runway incursion involving two Qantas-operated aircraft at Sydney Airport after an air traffic control clearance resulted in one aircraft being instructed to cross an active runway while another was still landing. The incident occurred on 27 July 2026 at approximately 08:14 local time, and although no collision occurred, the safety watchdog has classified it as a breakdown in coordination and opened a formal investigation. According to the ATSB, the occurrence involved Qantas Flight QF124, a Boeing 737-800 registered VH-XZG, which had arrived from Queenstown, New Zealand, and QantasLink Flight QLK424D, a De Havilland Canada Dash 8 Q400 registered VH-QOC, arriving from Canberra, Australian Capital Territory. Preliminary information released by the ATSB states that after landing on Runway 25, the Boeing 737 was instructed by air traffic control to taxi and cross Runway 34L. At the same time, the Dash 8 Q400 had been cleared to land on Runway 34L and was still completing its landing roll along the active runway. As the Boeing approached the runway crossing point, air traffic controllers recognised the developing conflict. The ATSB said the 737 crew stopped the aircraft before entering Runway 34L, while the Dash 8 continued its landing roll on the runway. Because the Boeing halted short of the runway, the two aircraft remained separated and no collision occurred. No injuries or aircraft damage were reported, and both aircraft subsequently continued normal ground operations. The ATSB has not released the number of passengers or crew on board either flight. The safety bureau has opened investigation AO-2026-086 to determine the factors that led to the runway incursion. Investigators will examine the sequence of air traffic control clearances, coordination between controllers, recorded radio communications, surveillance data, aircraft movements, human factors and operational procedures. The investigation will also assess whether any broader systemic issues contributed to the occurrence. In its initial investigation notice, the ATSB described the event as involving a breakdown of coordination between aircraft movements on intersecting runways. The agency noted that evidence collection is underway, including interviews with relevant personnel and analysis of operational data. A final report is expected before the end of 2026, although the timeline may change depending on investigative findings. The incident has renewed attention on staffing pressures within Australia's air traffic control system. Recent media reports have highlighted controller shortages and increased workload at Sydney Airport, with industry representatives raising concerns over staffing levels. Airservices Australia has acknowledged workforce challenges and said it is recruiting and training additional controllers, while noting that qualification training takes several years before recruits can work independently in complex airspace. Airservices Australia confirmed it is cooperating fully with the ATSB investigation and said safety remains its highest priority. The organisation has not provided further comment while the independent investigation is ongoing. Qantas also confirmed it is assisting the ATSB and stated that both flight crews were operating in accordance with air traffic control instructions issued during the event.

Incidents

ATSB Investigates Runway Incursion Involving Two Qantas Aircraft At Sydney Airport

Aviation Today News Desk / August 5, 2026

Sydney, Australia: The Australian Transport Safety Bureau (ATSB) has launched an investigation into a serious runway incursion involving two Qantas-operated

London, United Kingdom: A technical fault on a British Airways aircraft after landing at London Gatwick Airport in the early hours of 15 July 2026 triggered significant disruption across southern England, forcing the temporary closure of the airport's single runway and leading at least nine inbound passenger flights to declare emergencies as fuel levels became critical following prolonged airborne holding. The disruption began shortly after midnight when a British Airways flight arriving from Palma de Mallorca, Spain, landed safely at Gatwick at approximately 00:12 BST. After touchdown, the aircraft experienced what the airline later described only as a technical fault, leaving it unable to immediately vacate the runway. Airport rescue and firefighting vehicles were dispatched as a precaution while the aircraft remained stationary on the runway. British Airways confirmed that the aircraft landed safely and that passengers were not placed in danger. "Our flight landed safely and customers disembarked normally following reports of a technical fault with the aircraft," a British Airways spokesperson said. Although the airline has acknowledged the technical issue, it has not disclosed the nature of the fault, the aircraft type, or the aircraft registration. Gatwick Airport has likewise not released further technical information regarding the incident. Because Gatwick operates with a single main runway, the disabled aircraft temporarily prevented arriving flights from landing while emergency responders assessed the situation and efforts were made to clear the runway. During the closure, aircraft already inbound to Gatwick were instructed to enter holding patterns while air traffic controllers worked to manage the growing congestion. As delays lengthened, at least nine inbound flights declared emergency or urgency conditions after fuel reserves fell to operationally critical levels. Flight tracking data cited by multiple media outlets indicated the declarations were associated with low-fuel situations resulting from the extended airborne holding rather than mechanical problems aboard the affected aircraft. Nine flights squawked the 7700 emergency transponder code, reportedly due to low fuel after extended holding. An additional five flights were also diverted to alternate airports. Of the 14 affected flights, five landed at London Luton Airport, four at London Stansted Airport, and one at London Heathrow Airport. The remaining diversions were outside London, with three flights landing at Birmingham Airport and one at Bristol Airport. Several of the affected flights had departed popular Mediterranean holiday destinations, including Lanzarote, Rhodes and Tenerife, before being forced to abandon their approaches to Gatwick. Some aircraft diverted to London Stansted Airport, while others were rerouted to London Luton Airport after determining they no longer had sufficient fuel to continue holding safely. One passenger travelling from Tenerife, whose flight diverted to Stansted instead of Gatwick, posted on social media that passengers remained on board awaiting instructions while airline staff determined the next steps. The traveller said the journey had become considerably longer than normal because of the diversion. The runway was eventually reopened after the British Airways aircraft was moved, allowing Gatwick to resume normal operations. However, the temporary closure caused knock-on delays affecting arrivals and departures during the overnight and early morning operating period. No injuries have been reported in connection with either the British Airways aircraft or any of the diverted flights. Authorities have not announced an investigation beyond the airline's technical inspection of the aircraft, and the exact cause of the fault remains unknown. As of the latest available updates, British Airways has not released additional operational details.

Incidents

BA Technical Fault Shuts Gatwick Runway, Nine Flights Declare Low-Fuel Emergencies

Aviation Today News Desk / July 15, 2026

London, United Kingdom: A technical fault on a British Airways aircraft after landing at London Gatwick Airport in the early

Shannon, Ireland: United Airlines Flight UA509, a Boeing 767-400ER operating from Rome Fiumicino Airport (FCO), Italy, to Newark Liberty International Airport (EWR), New Jersey, was forced to divert to Shannon Airport (SNN), Ireland, on July 11 after the flight crew reported right-engine vibrations and an unusual odor in the cabin while crossing the North Atlantic. The aircraft was carrying 227 passengers and crew, and all landed safely with no injuries. The aircraft, registered N76065, departed Rome at 1:36 p.m. local time for the scheduled transatlantic service to Newark. Approximately three hours into the flight, while cruising at FL340 (34,000 feet) over the Atlantic and around 400 kilometres south of Ireland about 550 kilometres from Shannon Airport the pilots detected abnormal vibrations from the aircraft's right General Electric CF6 engine. The crew also reported a noticeable smell inside the cabin, prompting them to discontinue the oceanic crossing and request an immediate diversion to Shannon, one of the primary diversion airports for North Atlantic flights. According to reports, the affected engine remained operational but was reduced to idle thrust as a precaution. Air traffic controllers cleared the aircraft to divert, after which the crew descended from cruise altitude to facilitate the approach into Shannon. Because of the amount of fuel still onboard, the pilots advised they would be conducting an overweight landing, a procedure in which an aircraft lands above its normal maximum landing weight when an immediate landing is considered the safest course of action. At Shannon Airport, emergency procedures were activated before the aircraft's arrival. Airport authorities alerted their fire and rescue service after the crew requested emergency vehicles to be positioned alongside the runway. The Boeing 767 landed safely on Runway 06 at approximately 3:57 p.m. local time after more than four hours in the air. Fire and rescue vehicles escorted the aircraft along the runway before it stopped briefly on a taxiway, where firefighters carried out a visual inspection of the right engine. Given the overweight landing, emergency personnel also examined the aircraft's undercarriage and landing gear to ensure there was no overheating caused by the heavier-than-normal touchdown. Following the inspections, the aircraft taxied under its own power to the terminal while accompanied by emergency vehicles. United Airlines confirmed that the diversion was carried out "to address an issue with one engine." The airline said all 227 occupants disembarked safely without injury. Passengers were provided with hotel accommodation, compensation where applicable, and were rebooked on the next available flights to their destinations. Flight tracking data showed the aircraft remained on the ground in Shannon following the incident while maintenance personnel conducted inspections to determine the cause of the reported engine vibrations and cabin odor. The remainder of Flight UA509 to Newark was cancelled. As of the latest available updates, aviation authorities had not released findings on the cause of the technical issue, and the aircraft continued to undergo maintenance evaluation before returning to service.

Incidents

United Boeing 767 Diverts To Shannon After Engine Vibrations On Rome-Newark Flight

Aviation Today News Desk / July 14, 2026

Shannon, Ireland: United Airlines Flight UA509, a Boeing 767-400ER operating from Rome Fiumicino Airport (FCO), Italy, to Newark Liberty International

Mumbai, India: A potentially catastrophic runway collision was averted at Mumbai's Chhatrapati Shivaji Maharaj International Airport (CSMIA) on the night of July 8, 2026, after an Air India flight bound for Delhi was forced to abort its take-off roll when an Air India Express aircraft was still occupying the same runway following its landing, according to multiple media reports. The incident occurred on one of the airport's active runways during routine flight operations. According to aviation sources cited by several media outlets, the Air India aircraft had already begun accelerating for departure after receiving take-off clearance when its crew noticed an Air India Express aircraft ahead on the runway. The Air India Express flight had landed moments earlier but had not yet vacated the runway. Realising the runway was not clear, Air Traffic Control (ATC) immediately instructed the Air India crew to reject the take-off. The pilots carried out a rejected take-off (RTO), bringing the aircraft safely to a halt before reaching the Air India Express aircraft. The prompt response by both the cockpit crew and ATC prevented what could have become one of the most serious runway incidents at India's busiest airport. No passengers or crew members were injured in the incident, and neither aircraft sustained any reported damage. Airport operations continued after the aircraft were safely separated. While authorities have not officially disclosed the flight numbers involved, reports indicate that the departing aircraft was an Air India service from Mumbai to Delhi, while the other aircraft belonged to Air India Express and had just completed its landing at Mumbai. Initial information suggests the Air India Express aircraft had not vacated the runway before the departing Air India flight commenced its take-off roll, raising questions over runway occupancy and the sequencing of aircraft movements. Aviation authorities are expected to examine ATC clearances, communication between controllers and flight crews, runway occupancy procedures and the exact timeline of events to determine how both aircraft came to be on the same runway simultaneously. Earlier last month, on June 24, 2026, another face-to-face aircraft incident occurred at Ahmedabad's Sardar Vallabhbhai Patel International Airport when an Air India Airbus A320 arriving from Mumbai took a wrong turn while taxiing after landing and entered an active taxiway, where it came nose-to-nose with an IndiGo aircraft preparing for departure. ATC immediately halted both aircraft, no injuries or damage were reported, and the DGCA launched an investigation into the incident

Incidents

Air India And Air India Express Come Face-To-Face On Mumbai Runway; Take-Off Aborted

Aviation Today News Desk / July 10, 2026

Mumbai, India: A potentially catastrophic runway collision was averted at Mumbai’s Chhatrapati Shivaji Maharaj International Airport (CSMIA) on the night

A Delta Air Lines Airbus A319 carrying 52 passengers and six crew members landed safely at Chicago Midway International Airport after the crew reported an apparent firework strike during final approach on July 4. While descending through about 200–250 feet, the pilots heard a "big bang" and believed a firework had struck or exploded beneath the aircraft. Fireworks were launched from residential neighborhoods under the airport's approach path during Independence Day celebrations, with air traffic controllers advising that multiple similar reports had been received. The aircraft landed safely without injuries, an inspection found no damage, and the Federal Aviation Administration has launched an investigation into the incident.

Incidents

Delta Flight Lands Safely After Crew Reports Possible Firework Strike Near Chicago

Aviation Today News Desk / July 6, 2026

Chicago, United States: A Delta Air Lines flight carrying 58 people landed safely at Chicago Midway International Airport after the

Burgas, Bulgaria: A LOT Polish Airlines flight bound for Tel Aviv was forced to make an emergency diversion to Bulgaria on June 30 after an inadvertent hijack alert triggered a multinational security response involving fighter aircraft from Bulgaria and Israel. Flight LO155, operated on behalf of LOT Polish Airlines by Bulgarian charter carrier Electra Airways using an Airbus A320, had departed Warsaw Chopin Airport at 11:35 a.m. local time for Ben Gurion Airport in Tel Aviv when the aircraft unexpectedly transmitted transponder code 7500 the internationally recognised emergency squawk indicating unlawful interference or a hijacking. The emergency code prompted air traffic controllers to initiate international aviation security procedures. According to Bulgaria's Ministry of Transport, the aircraft's transponder experienced a technical malfunction that incorrectly transmitted the hijack signal, while LOT Polish Airlines said the emergency code had been mistakenly activated before subsequently being cancelled during further communication with air traffic control. Flight tracking data from FlightAware showed the aircraft continued south over the Mediterranean Sea, where it circled near the coast of Cyprus before abandoning its approach to Israel and diverting toward Bulgaria. The aircraft initially requested permission to land at Paphos International Airport in Cyprus. Bulgarian authorities said the request could not be accommodated because of heavy air traffic, prompting the crew to divert to Burgas Airport instead. During the unfolding incident, the Israel Defense Forces (IDF) scrambled two fighter jets after temporarily losing communication with the aircraft. The military later confirmed radio contact had been restored and stressed there was no indication of a genuine security threat. Bulgarian authorities also responded immediately. A Bulgarian Air Force MiG-29 intercepted and escorted the aircraft while it remained in Bulgarian airspace. After the aircraft crossed into Turkish-controlled airspace, the escort was transferred to two Turkish F-16 fighter jets, which accompanied the flight until it safely returned to Bulgaria. The Airbus A320 landed safely at Burgas Airport at approximately 5:13–5:15 p.m. local time, where it was directed to an isolated parking position away from the terminal and other airport infrastructure in accordance with international aviation security procedures. Business Insider reported that the aircraft was carrying around 180 passengers. Following the landing, passengers disembarked safely and underwent security screening by Bulgarian police before being escorted to a designated holding area while authorities conducted inspections of the aircraft. LOT Polish Airlines later informed passengers that the diversion resulted from the unintentional activation of an onboard security alert, describing the occurrence as an exceptionally rare event. "The diversion of your flight to Burgas was caused by the unintentional activation of an onboard security alert. In accordance with the applicable safety procedures, the aircraft was redirected to an alternate airport so that the situation could be fully clarified with the relevant authorities," the airline said in a statement provided to passengers. The carrier added that incidents of this nature are extremely rare and emphasised that the safety and security of passengers and crew remain its highest priority. Bulgarian authorities subsequently confirmed that the aircraft had not been hijacked and that the emergency signal resulted from a technical failure involving the aircraft's transponder, which falsely indicated unlawful interference. No injuries were reported, and normal operations at Burgas Airport continued throughout the security response.

Incidents

LOT Flight To Tel Aviv Diverts After False Hijack Alert Triggers Fighter Jet Response

Aviation Today News Desk / July 1, 2026

A LOT Polish Airlines flight bound for Tel Aviv was forced to make an emergency diversion to Bulgaria on June

Ahmedabad, India: A potentially serious ground incident was averted at Ahmedabad's Sardar Vallabhbhai Patel International Airport after an Air India aircraft inadvertently entered an active taxiway following landing and came face-to-face with an IndiGo aircraft preparing for departure. Swift intervention by Air Traffic Control (ATC) prevented the situation from escalating, with both aircraft stopping safely before any collision occurred. The incident took place on the evening of June 24 while Air India flight AI2493, operating from Mumbai to Ahmedabad, was taxiing to its assigned parking stand after landing. According to Air India and aviation sources, the aircraft made an unintended turn while taxiing toward its designated bay, entering an active taxiway instead of following its assigned route. At the same time, IndiGo flight 6E5160, scheduled to operate from Ahmedabad to Mumbai, was taxiing for departure toward the runway. The unexpected movement brought the two Airbus A320-family aircraft onto the same taxiway, leaving them positioned directly opposite each other. According to officials, Air Traffic Control immediately instructed both flight crews to stop. The aircraft came to a halt with an estimated separation of around 200 metres, ensuring that no contact occurred between them. Authorities confirmed there were no injuries to passengers or crew and no damage to either aircraft. Following the incident, the Air India aircraft was assisted back to its designated parking bay with ground support, after which the IndiGo aircraft resumed taxiing and departed safely for Mumbai. The IndiGo flight subsequently landed safely at Chhatrapati Shivaji Maharaj International Airport in Mumbai. In an official statement, Air India acknowledged that flight AI2493 had taken an unintended turn during taxiing after landing at Ahmedabad on June 24. "We are aware of an incident where our flight AI2493 operating from Mumbai to Ahmedabad, after landing, inadvertently took a wrong turn during taxiing. There was no compromise on the safety of passengers or crew. The aircraft was subsequently moved to the correct parking bay with ground assistance," the airline said. Air India added that the matter had been reported to the Directorate General of Civil Aviation (DGCA), and an internal investigation had been initiated. IndiGo confirmed that its flight 6E5160 was taxiing for departure to Mumbai when another aircraft entered its taxi path. The airline said both aircraft were stopped immediately as a precaution in coordination with ATC. After the situation was resolved, the flight continued its departure and completed the journey safely. The Directorate General of Civil Aviation has been informed of the incident and has initiated an investigation to determine the circumstances that led to the taxiway deviation. Investigators are expected to examine the sequence of taxi instructions issued by ATC, cockpit communications, pilot adherence to taxi clearances, airport ground movement procedures and other operational factors that may have contributed to the incident. Authorities have not yet determined the cause of the wrong turn, and no findings have been released regarding whether the deviation resulted from pilot error, misunderstanding of taxi instructions, airport signage, or any other contributing factor.

Incidents

Potential Ground Collision With IndiGo Aircraft Averted After Air India Taxiway Error

Aviation Today News Desk / June 26, 2026

Ahmedabad, India: A potentially serious ground incident was averted at Ahmedabad’s Sardar Vallabhbhai Patel International Airport after an Air India

Air Traffic Control

NSIB Preliminary Report Finds Safety Gaps In Enugu Air Benin Airport Runway Overrun

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

Military GPS Jamming Was Underway During Fatal Air Ambulance Flight, NTSB Says

ATSB Investigates Runway Incursion Involving Two Qantas Aircraft At Sydney Airport

BA Technical Fault Shuts Gatwick Runway, Nine Flights Declare Low-Fuel Emergencies

United Boeing 767 Diverts To Shannon After Engine Vibrations On Rome-Newark Flight

Air India And Air India Express Come Face-To-Face On Mumbai Runway; Take-Off Aborted

Delta Flight Lands Safely After Crew Reports Possible Firework Strike Near Chicago

LOT Flight To Tel Aviv Diverts After False Hijack Alert Triggers Fighter Jet Response

Potential Ground Collision With IndiGo Aircraft Averted After Air India Taxiway Error

Quick Links

Navigate

General Support

News Desk Support