ATC Archives - Page 3 of 4

Union Strike Disrupts Kenya’s Main Airport For Two Days Before Return-To-Work Deal

Aviation Today News Desk / February 18, 2026

Nairobi, Kenya: A strike by aviation workers at Jomo Kenyatta International Airport (JKIA), Kenya’s largest and busiest aviation hub that […]

Incidents

British Airways Flight Declares Emergency Due To Technical Issue Minutes After Takeoff

Aviation Today News Desk / February 12, 2026

Glasgow, United Kingdom: A British Airways passenger jet bound for London Heathrow declared an emergency shortly after taking off from

Incidents

American Airlines Flight Makes Emergency Return To Barbados Post Burst Tyre On Takeoff

Aviation Today News Desk / February 11, 2026

Bridgetown, Barbados: An American Airlines Boeing 737-823, operating Flight AA1284 from Bridgetown to Miami, was forced to make an emergency

Aircraft Crashes

Plane Makes Emergency Landing After Engine Failure, Hits 3 Cars On Georgia Road

Aviation Today News Desk / February 10, 2026

Gainesville, United States: A small single-engine aircraft was forced to make an emergency landing on a busy Gainesville roadway Monday

Brussels, Belgium: A Scandinavian Airlines (SAS) Airbus A320neo operating flight SK2590 from Brussels Airport (BRU) to Copenhagen (CPH) narrowly avoided a serious runway incident on Thursday evening after pilots inadvertently initiated a takeoff roll on a taxiway rather than the designated runway, aviation tracking data and eyewitness reports confirm. The flight, cleared for departure from Runway 07R shortly after 21:00 UTC, taxied toward the runway but instead turned onto a parallel taxiway (identified as E1/V1) and began accelerating as if commencing a normal departure. Flightradar24 data shows the aircraft reached approximately 107 knots (around 198 km/h) before the crew recognised the error and aborted the takeoff, applying heavy braking and reverse thrust to bring the aircraft to a stop near the end of the taxiway and adjacent grassy area. All 135 passengers and crew disembarked safely, and there are no reported injuries. Airport fire and rescue services assisted passengers, who were later rebooked onto alternate flights to Copenhagen. SAS’s Head of Communications, Alexandra Lindgren Kaoukji, confirmed the incident to Danish broadcaster TV 2, stating that the flight from Brussels to Copenhagen was canceled due to an “irregularity.” She confirmed the airline’s account of an aborted departure and that passengers were accommodated on subsequent services. Belgian civil aviation authorities have initiated a formal investigation into the circumstances that led to the aircraft taking the wrong surface for departure. Investigators will review air traffic control communications, flight crew procedures, and airport surface signage and lighting, particularly given the complex layout of taxiways and runways at one of Europe’s busiest hubs. The taxiway departures are rare and emphasise the importance of rigorous cross-checks by flight crews and air traffic controllers to ensure correct runway alignment before high-speed acceleration. Any final determinations about human factors or procedural issues will await the outcome of the official investigation

Incidents

SAS A320neo Narrowly Avoids Runway Incident After Taxiway Takeoff Attempt In Brussels

Aviation Today News Desk / February 6, 2026

Brussels, Belgium: A Scandinavian Airlines (SAS) Airbus A320neo operating flight SK2590 from Brussels Airport (BRU) to Copenhagen (CPH) narrowly avoided

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding the December 22, 2025, crash of a Mexican Navy medical flight in Galveston Bay that killed six people and left two seriously injured, according to the preliminary report released by the U.S. National Transportation Safety Board (NTSB). The Beechcraft B300 aircraft, registered ANX1209 and operated by the Mexican Navy, was on a humanitarian medical mission coordinated with the Michou y Mau Foundation. The flight was transporting a severely burned pediatric patient from Mérida, Mexico, to Shriners Children’s Hospital in Galveston, Texas, when it crashed into West Bay during its approach to Scholes International Airport shortly before 3:15 p.m. local time. According to the NTSB preliminary report, Houston Approach Control cleared the flight crew for an RNAV (GPS-based) approach to Runway 14 but did not clear the aircraft to land. The flight crew’s initial readback mistakenly stated they were “cleared to land,” prompting controllers to twice clarify that the aircraft was cleared only for the approach and not for landing. Controllers then directed the crew to contact the tower. Despite repeated clarifications, the crew’s responses indicated persistent misunderstanding. During the final stages of the approach, air traffic controllers issued multiple low-altitude alerts, but received no further communication from the flight crew before radar contact was lost. The preliminary report and weather observations confirmed dense fog and severely restricted visibility during the aircraft’s final descent. Controllers advised the crew that cloud ceilings near the airport were approximately 300 feet, a condition that significantly limits visual reference and places heavy reliance on instrument procedures. Local weather data and witness accounts indicate visibility at times was as low as approximately a quarter mile with heavy sea fog common along the Texas Gulf Coast under certain conditions further complicating the approach. The aircraft impacted the waters of West Galveston Bay approximately half a mile from the shoreline. Six occupants including the pilot, co-pilot, two flight crew members and two passengers were fatally injured. Two passengers, reported to be a flight nurse and the mother of the pediatric patient, survived with serious injuries. Search and rescue operations immediately following the crash involved the U.S. Coast Guard, Texas Department of Public Safety, Galveston County Sheriff’s Office and local first responders. The wreckage was located in shallow water, facilitating recovery efforts. The NTSB’s preliminary report is part of an ongoing investigation to determine all contributing factors. These factual reports do not assign probable cause but document the circumstances surrounding the accident based on available data, including air traffic control communications and radar information. Federal investigators will continue to analyze cockpit voice recordings, flight data, maintenance records and meteorological data. A final report typically released 12–24 months after an accident will include a probable cause determination and safety recommendations aimed at preventing similar tragedies.

Investigation

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Aviation Today News Desk / February 5, 2026

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding

Kolkata, India: A Turkish Airlines Airbus A330 on a scheduled service from Kathmandu, Nepal, to Istanbul, Turkey made a full emergency landing at Netaji Subhash Chandra Bose International Airport, Kolkata, on Wednesday afternoon after the crew reported a fire in the aircraft’s right engine shortly after take-off. The flight, operating as THY-727, departed Tribhuvan International Airport at approximately 1:28 PM local time with 236 people on board 225 passengers and 11 crew members. Within four minutes of take-off, the pilots received a warning of a possible fire in the right engine and immediately shut down the affected unit. Following standard emergency procedures, the captain declared a PAN PAN distress call, an international aviation signal indicating an urgent situation and elected to divert the long-haul flight to Kolkata rather than continue towards its planned destination. Air traffic control at Kolkata was informed of the situation, and a full emergency response was activated, deploying firefighting and rescue units ahead of the aircraft’s arrival. The Airbus A330, capable of flying on a single engine, landed safely at around 2:49 PM IST without incident. Officials from both Nepal and Indian aviation authorities confirmed that no injuries were reported among passengers or crew. Tribhuvan International Airport briefly suspended operations for about 15 minutes following the alarm. After landing, the aircraft was parked at Kolkata Airport and underwent detailed technical inspection to determine the exact cause and extent of the engine malfunction. Passengers were reportedly accommodated in local hotels while arrangements were made for onward travel, including plans for a replacement aircraft earlyThursday morning.

Incidents

Turkish Airlines Flight Makes Emergency Landing In Kolkata After Engine Fire Mid-Air

Aviation Today News Desk / February 5, 2026

Kolkata, India: A Turkish Airlines Airbus A330 on a scheduled service from Kathmandu, Nepal, to Istanbul, Turkey made a full

Mumbai, India: Two commercial aircraft operating at Chhatrapati Shivaji Maharaj International Airport (CSMIA) were involved in a ground collision involving their wingtips on Tuesday evening, prompting inspections and an immediate probe by aviation authorities. All passengers and crew onboard both flights were unharmed, officials confirmed. The incident occurred at approximately 7:30 pm IST when Air India flight AI 2732, bound for Coimbatore, was taxiing for departure and the IndiGo flight 6E 791 had just landed from Hyderabad and was taxiing toward the terminal. Both aircraft involved were narrow-body Airbus A320s. According to Air India, the right wingtip of its aircraft made contact with the wingtip of the IndiGo aircraft while maneuvering on the taxiway prior to taking off. The airline said the contact resulted in damage to its aircraft’s wingtip, and the aircraft was immediately grounded for technical checks as a precautionary measure. All passengers were safely deplaned, and ground teams began arranging alternative onward travel. IndiGo released a separate statement confirming that the wingtip of its aircraft operating flight 6E 791 touched the wing of another airline’s aircraft while taxiing after landing. The airline said all passengers disembarked safely, and its aircraft is undergoing maintenance inspection in line with standard protocols. The Directorate General of Civil Aviation (DGCA) dispatched a team from its Mumbai office to the site soon after the incident. DGCA officials confirmed both aircraft returned to their respective bays and were taken out of service pending inspection. The regulator has initiated an inquiry to determine the factors leading to the collision, focusing on ground vehicle and aircraft movement controls at the busy international airport. “No injuries have been reported among passengers or crew,” according to civil aviation sources, highlighting that the low-speed nature of the taxiing incident limited the impact to aircraft structures rather than human safety. The airport, which operates parallel runways and heavy traffic movements daily, did not report any significant disruptions to other flights following the incident. Authorities said that routine operations continued while the affected aircraft were inspected.

Incidents

Air India & IndiGo Aircraft Wingtips Collide At Mumbai Airport, No Injuries Reported

Aviation Today News Desk / February 4, 2026

Mumbai, India: Two commercial aircraft operating at Chhatrapati Shivaji Maharaj International Airport (CSMIA) were involved in a ground collision involving

Birmingham, United Kingdom: An Air India Boeing 787‑8 Dreamliner operating flight AI117 from Amritsar, India, to Birmingham, UK, declared a general emergency due to low fuel on the evening of 8 January 2026 after prolonged holding caused by severe winter weather and the temporary closure of Birmingham Airport. The aircraft was safely diverted to London Heathrow Airport where it landed without incident, airline and flight tracking data show. Flight AI117, registration VT‑NAC, was approaching Birmingham in worsening weather as Storm Goretti brought heavy snowfall and dangerously low visibility, leading airport authorities to suspend runway operations. Visibility dipped well below the minima required for a safe landing, forcing the crew to abort the initial approach and enter a holding pattern. With extended time spent circling near the destination, fuel reserves fell toward critical levels. In response, the crew transmitted Squawk 7700 the transponder emergency code indicating a serious onboard issue requiring urgent air traffic control priority signalling a general emergency due to low fuel. This prompted expedited handling and coordination with UK air traffic control for diversion. Air Traffic Control cleared the Boeing 787 to divert to London Heathrow Airport (LHR), chosen for its longer runways and advanced Category III Instrument Landing System (ILS) capable of accommodating landing in degraded weather conditions with enhanced safety margins. The aircraft touched down safely on Heathrow’s runway 09L and subsequently taxied to gate B49 with no reported injuries to passengers or crew. Air India flight operations encountered significant disruption as snow continued to impact Birmingham Airport operations throughout the evening. The airport’s decision to close the runways was part of ongoing safety precautions amid rapid snow accumulation and deteriorating meteorological conditions. A declaration of Squawk 7700, a universal aviation emergency code does not automatically reflect a catastrophic failure; rather, it alerts all air traffic units that the flight requires priority handling due to a critical situation, in this case driven by fuel management considerations following a prolonged holding pattern.

Incidents

Air India 787 Declares Emergency Over Low Fuel, Safely Diverts To London Heathrow

Aviation Today News Desk / January 9, 2026

Birmingham, United Kingdom: An Air India Boeing 787‑8 Dreamliner operating flight AI117 from Amritsar, India, to Birmingham, UK, declared a general

Boston, United States: The Federal Aviation Administration (FAA) is investigating a close-call incident at Boston Logan International Airport on Thursday afternoon, when a Delta Air Lines widebody jet and a Cape Air commuter aircraft came dangerously close to each other on intersecting runways. According to FAA officials, Delta Flight 263 an Airbus A330-900neo operating from Paris Charles de Gaulle to New York-JFK had been diverted to Boston due to weather in the New York area. The aircraft, carrying 284 passengers and 11 crew, was on approach to Logan around 4:15 p.m. ET when air traffic control ordered the pilots to perform a go-around to maintain safe separation from Cape Air Flight 548, which had been cleared for takeoff on an intersecting runway. Audio recordings from LiveATC.net, cited by multiple outlets, captured the tense exchange between the flight crews. As the Delta A330 climbed away from the runway, one of its pilots radioed, “That was close.” Moments later, a Cape Air pilot could be heard responding, “Yeah, man, not cool.” While no collision occurred and both flights landed safely, aviation experts said the proximity of the two aircraft estimated at less than half a mile at one point warranted investigation. “Even when vertical and horizontal separation remains within limits, intersecting-runway operations always carry elevated risk,” one aviation analyst told WCVB Boston. The FAA confirmed that controllers instructed the Delta crew to abort landing to “ensure safe separation” after the Cape Air flight was cleared for departure. The agency has since opened a formal investigation into the event to determine whether procedural, human, or environmental factors contributed. Both airlines confirmed that their pilots followed ATC instructions. “Delta Air Lines is cooperating fully with the FAA’s review,” the company said in a statement, adding that safety remains its top priority. Cape Air also noted that its pilots “acted in accordance with clearance and protocol.” The incident comes amid rising operational pressure on U.S. air traffic controllers, who have faced long shifts and reduced staffing levels exacerbated by the ongoing federal government shutdown. Nearly 13,000 air traffic controllers working without pay and prompting hundreds to take on second jobs to cover essential expenses. The situation, aviation unions warn, is beginning to pose serious risks to both air safety and system reliability.

Incidents

FAA Probes Close Call Between Delta A330 And Cape Air Plane At Boston Logan Airport

Aviation Today News Desk / November 3, 2025

Boston, United States: The Federal Aviation Administration (FAA) is investigating a close-call incident at Boston Logan International Airport on Thursday

ATC

Union Strike Disrupts Kenya’s Main Airport For Two Days Before Return-To-Work Deal

British Airways Flight Declares Emergency Due To Technical Issue Minutes After Takeoff

American Airlines Flight Makes Emergency Return To Barbados Post Burst Tyre On Takeoff

Plane Makes Emergency Landing After Engine Failure, Hits 3 Cars On Georgia Road

SAS A320neo Narrowly Avoids Runway Incident After Taxiway Takeoff Attempt In Brussels

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Turkish Airlines Flight Makes Emergency Landing In Kolkata After Engine Fire Mid-Air

Air India & IndiGo Aircraft Wingtips Collide At Mumbai Airport, No Injuries Reported

Air India 787 Declares Emergency Over Low Fuel, Safely Diverts To London Heathrow

FAA Probes Close Call Between Delta A330 And Cape Air Plane At Boston Logan Airport

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us