AirTrafficControl Archives

Sydney, Australia: A Jetstar Airbus A320 and a Qatar Airways Boeing 777 came dangerously close to a collision while moving on the ground at Sydney Airport on Sunday morning, August 9, after the Jetstar crew was forced to brake abruptly to avoid the Qatar aircraft. The incident occurred at about 7:00am local time at Sydney Kingsford Smith Airport. The Jetstar A320, operating flight JQ402 from Sydney to Gold Coast Airport, was taxiing for departure when its crew observed the Qatar Airways Boeing 777 being towed by an aircraft tug on a crossing taxiway. The ATSB said both aircraft were brought to an abrupt stop, preventing a collision. According to Australian media reports, the Jetstar aircraft stopped about 50 metres from the Qatar 777. The sudden braking caused a rear cabin crew member aboard the Jetstar aircraft to fall and suffer a broken wrist. No Jetstar passengers were injured. JQ402 was carrying 151 passengers and six crew members, according to Australian media reports. The flight was subsequently cancelled and passengers were rebooked onto later services. The Qatar Boeing 777 was not operating a passenger departure at the time. It had arrived at Sydney from Doha and was being repositioned under tow after passengers had disembarked. The aircraft therefore had no passengers onboard during the near-collision. The precise sequence that brought the two aircraft into such close proximity remains under investigation. Jetstar said its aircraft was following air traffic control instructions when its pilots were forced to brake firmly after another aircraft came into close proximity. The airline has also begun its own investigation. The ATSB said there was damage to the connection between the Qatar 777's nose landing gear and the aircraft tug. Investigators will examine data from both aircraft and air traffic control, while interviewing the flight crew, tug operators, air traffic controllers and other witnesses. CCTV and other recorded information will also be reviewed. ATSB Chief Commissioner Angus Mitchell said it was too early to determine where the communication or coordination breakdown occurred. Investigators will establish what instructions were issued, how they were understood and why the aircraft came so close before the final stop. The incident has also drawn attention to air traffic-control staffing pressures at Sydney Airport. ABC reported that air traffic control was operating under restrictions between 6:00am and 8:00am on Sunday, limiting the number of aircraft moving through the airport. More than 150 flights had also been affected by roster constraints in the days leading up to the incident. However, there is currently no official finding that the staffing situation caused the near-collision. The ATSB investigation will determine whether communication, coordination, ground movements, procedures or other factors contributed. Two people involved in the ground operation, an air traffic ground controller and the tug operator were stood down for mandatory drug and alcohol testing, which the federal transport minister described as standard post-incident procedure. Their stand-down should not be interpreted as a finding of fault. The ATSB has asked anyone with video of Sunday's incident or its immediate aftermath to provide footage to investigators. The investigation remains ongoing.

Jetstar A320 And Qatar 777 Narrowly Avoid Collision During Taxiing At Sydney Airport

Aviation Today News Desk / August 10, 2026

Sydney, Australia: A Jetstar Airbus A320 and a Qatar Airways Boeing 777 came dangerously close to a collision while moving […]

Atlanta, United States: The U.S. Federal Aviation Administration (FAA) is investigating a serious runway separation incident involving two Delta Air Lines aircraft at Hartsfield-Jackson Atlanta International Airport after the jets came into close proximity during simultaneous arrival and departure operations late on July 27. The incident involved Delta Air Lines Flight DL1568, arriving from Pittsburgh, and Delta Air Lines Flight DL2472, departing for Rochester, New York. According to the FAA and flight-tracking data, Flight 1568 was on final approach when the crew initiated a go-around after the departing aircraft had not cleared the runway environment in time. As the arriving aircraft climbed away from the runway, it came into conflict with the departing Delta jet. Both flight crews received Traffic Collision Avoidance System (TCAS) resolution advisories, prompting immediate evasive action. Air traffic controllers instructed the departing aircraft to turn and continue climbing while the arriving aircraft followed its missed-approach procedure. The crews complied with the alerts and ATC instructions, allowing both aircraft to safely regain separation. According to publicly reported flight data, the aircraft came within approximately 1,800 feet horizontally and 600 feet vertically at their closest point before increasing separation. No injuries were reported, and both flights continued safely after the event. Flight 1568 subsequently entered a holding pattern before landing safely in Atlanta, while Flight 2472 continued its scheduled flight to Rochester. Air traffic control audio reviewed by multiple media outlets captured the urgency of the event. Controllers quickly issued revised instructions after recognizing the developing conflict, while one pilot was heard expressing surprise at how close the aircraft had come. The communications indicate that both the controllers and flight crews acted promptly in response to the TCAS warnings, helping prevent a more serious incident. The FAA confirmed it is investigating the occurrence to determine the sequence of events, including runway occupancy, aircraft spacing and air traffic control actions. As of the latest update, the agency has not released preliminary findings or identified a probable cause. No damage to either aircraft has been reported, and no onboard injuries have been disclosed. The airline's operating crews followed established safety procedures, including compliance with TCAS resolution advisories and ATC instructions, allowing both flights to continue safely.

Incidents

FAA Investigates Close Call Between Two Delta Air Lines Aircraft At Atlanta Airport

Aviation Today News Desk / July 30, 2026

Atlanta, United States: The U.S. Federal Aviation Administration (FAA) is investigating a serious runway separation incident involving two Delta Air

Miami, United States: An American Airlines flight bound for Bermuda aborted its takeoff at Miami International Airport after a business jet entered the active runway without authorization, prompting pilots to reject the departure and averting what could have become a serious runway collision. The incident occurred at approximately 6:00 p.m. local time on Friday, June 26, when American Airlines Flight 308, an Airbus A319 operating from Miami to Bermuda, had already been cleared for takeoff from Runway 8R. The aircraft was carrying 112 passengers and had accelerated to about 60 mph (approximately 52 knots) when the flight crew spotted another aircraft crossing the runway ahead. The crew immediately initiated a rejected takeoff, bringing the aircraft to a safe stop. According to the Federal Aviation Administration (FAA), the two aircraft came within approximately one-third of a mile (530 metres) of each other before the American Airlines pilots successfully avoided a potential collision. The second aircraft involved was NetJets Flight EJA434, a business jet that was being operated by a third-party maintenance vendor at the time of the incident. NetJets later clarified that the aircraft was not under the company's operational control during the runway incursion. Air traffic control (ATC) recordings revealed confusion over runway crossing instructions immediately after the incident. The controller told the business jet crew, "You just crossed an active runway." The pilot responded, "You just told me to cross the runway, sir." The controller replied, "No, we said Amerijet 461," indicating that the clearance had been issued to another aircraft rather than the NetJets-operated jet. The FAA confirmed that the business jet entered the runway without authorization and has launched an investigation into the runway incursion. American Airlines said in a statement that Flight 308 discontinued its takeoff after the crew observed another aircraft on the runway and thanked its pilots for their quick response. No injuries were reported among the 112 passengers or crew members aboard the American Airlines aircraft, and no injuries were reported to those aboard the business jet. The FAA has not publicly disclosed how many people were on board the business jet. Following the incident, Flight 308 remained on the ground while inspections were carried out before departing approximately two to two-and-a-half hours later. The aircraft subsequently arrived safely in Bermuda at about 11:40 p.m. local time. In a separate aviation safety incident the same day, a United Airlines Boeing 737 operating Flight 1513 from Key West, Florida, to Newark Liberty International Airport reported a near collision with a drone while descending toward Newark. The aircraft, carrying 106 passengers and five crew members, was at approximately 2,000 feet when the flight crew reported that they had "almost hit a drone," estimating it passed roughly 100 feet below the aircraft's flight path. Another pilot approaching Newark also reported seeing the drone. The flight landed safely, passengers deplaned normally, and no injuries were reported. The FAA has opened an investigation and reiterated that unauthorized drone operations near airports pose significant safety risks and may result in substantial fines or criminal penalties.

Incidents

American Airlines Aborts Takeoff At Miami After Unauthorised Jet Crosses Active Runway

Aviation Today News Desk / June 30, 2026

Miami, United States: An American Airlines flight bound for Bermuda aborted its takeoff at Miami International Airport after a business

Investigation

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Aviation Today News Desk / June 1, 2026

New Delhi, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a

Lucknow, India: An Akasa Air Boeing 737 MAX 8 operating from Bengaluru to Bhubaneswar made an emergency landing at Lucknow’s Chaudhary Charan Singh International Airport on May 27 after the flight encountered adverse weather conditions at its destination and subsequently reported low fuel levels during diversion. The flight, operating as QP1503 and registered as VT-YAJ, was carrying a total of 194 passengers and crew members onboard when the incident occurred. According to multiple media reports and airport officials, the aircraft was initially unable to land at Bhubaneswar due to unfavorable weather conditions. The flight was subsequently diverted to Lucknow at approximately 8:40 PM local time. While approaching Lucknow, the crew reportedly issued a “PAN PAN” call to Air Traffic Control (ATC) at around 9:02 PM after fuel levels became critically low during the extended diversion. In aviation terminology, a “PAN PAN” declaration indicates an urgent situation requiring priority assistance, though it is considered less severe than a “MAYDAY” distress call. The pilot-in-command requested priority handling and a clear approach to ensure the aircraft could land safely in a single attempt amid fuel constraints. Following the alert, Lucknow ATC declared a full emergency and immediately activated standard emergency response procedures. Crash fire tenders and emergency response teams were positioned at designated points along Runway 09 by approximately 9:04 PM as a precautionary measure. The aircraft landed safely at Lucknow International Airport at around 9:21 PM. Shortly after touchdown, the flight crew informed ATC that all aircraft operations were normal and that no emergency assistance was required. Authorities subsequently withdrew the full emergency status at approximately 9:30 PM. Airport officials confirmed that all emergency and safety protocols were executed as per standard operating procedures and that the situation was handled without incident. No injuries to passengers or crew were reported. According to reports, three passengers deboarded the aircraft in Lucknow before the flight later resumed its journey to Bhubaneswar. In an official statement, Akasa Air confirmed that the diversion was caused by adverse weather conditions at Bhubaneswar and stated that the crew followed all established operational and safety procedures throughout the incident. “Akasa Air flight QP 1503 operating from Bengaluru to Bhubaneswar on 27 May 2026 was diverted to Lucknow due to adverse weather conditions, which were not favourable for landing. The pilot followed all established operational and safety protocols in line with standard procedures,” the airline said. The carrier further stated that the flight later departed Lucknow and landed safely in Bhubaneswar at 00:02 hrs on May 28. “At Akasa Air, the safety and well-being of our passengers and crew remain our highest priority. We regret the inconvenience caused due to circumstances beyond our control and appreciate our passengers’ understanding,” the airline added.

Incidents

Akasa Air Flight Diverts To Lucknow After Weather Disruption And Low Fuel Alert

Aviation Today News Desk / May 29, 2026

Lucknow, India: An Akasa Air Boeing 737 MAX 8 operating from Bengaluru to Bhubaneswar made an emergency landing at Lucknow’s

Kirksville, United States: A seasoned private pilot safely executed an emergency landing in northeast Missouri after the windshield of a Cessna 421 Golden Eagle imploded mid-flight at high altitude, triggering a rapid descent and in-flight emergency. The incident occurred just before 6:30 p.m., according to Jeff LaFountain, director of Kirksville Regional Airport. The pilot, who was flying home to Boulder, Colorado, reported an emergency while cruising at approximately 20,000 feet over northeast Missouri. LaFountain said the aircraft’s windshield suddenly imploded following a rapid loss of cabin pressure, exposing the cockpit to extreme airflow conditions. The exact cause of the pressure drop remains unknown. Following the failure, the pilot radioed for an immediate diversion and initiated a rapid descent to 10,000 feet, a standard procedure to reach a breathable altitude in the event of pressurization issues. The aircraft was then successfully landed at Kirksville Regional Airport, where emergency crews had been placed on standby. No injuries were reported, and the pilot was unharmed despite the severity of the incident. The Federal Aviation Administration has been notified. It remains unclear whether a formal investigation will be launched, and officials have not yet released additional technical details. The aircraft will remain at Kirksville until necessary repairs are completed, after which it is expected to continue its journey to Boulder. The pilot responded in accordance with emergency procedures, successfully stabilizing the aircraft and completing the diversion without further incident.

Incidents

Cessna 421 Windshield Failure At 20,000 Feet Forces Emergency Landing In Missouri

Aviation Today News Desk / May 6, 2026

Kirksville, United States: A seasoned private pilot safely executed an emergency landing in northeast Missouri after the windshield of a

Ankara, Turkey: An aircraft carrying Pedro Sánchez was forced to divert and make an emergency landing at Ankara after a technical malfunction disrupted its flight en route to Armenia, officials confirmed. The Spanish Prime Minister was travelling aboard a government-operated Airbus A310, part of Spain’s official state aviation fleet. The aircraft had departed from Madrid and was scheduled to land in Yerevan for the European Political Community summit, a major diplomatic gathering of European leaders. Midway through the flight, the crew detected what officials described as an “unforeseen technical event.” While the malfunction was not publicly specified in detail, it was classified as a precautionary safety concern rather than a critical failure. In accordance with international aviation safety protocols, the pilots immediately requested diversion to the nearest suitable airport. The aircraft subsequently landed safely in Ankara without incident. No injuries were reported among Sánchez or members of his delegation, and there were no signs of panic or emergency escalation during the landing. Authorities confirmed that all passengers disembarked normally and were provided with necessary arrangements upon arrival. Following the diversion, the Prime Minister and his delegation were required to remain overnight in Ankara due to standard diplomatic and operational procedures. The unscheduled stop resulted in a delay to the official itinerary for the European summit in Armenia. Technical teams later inspected the aircraft and resolved the issue that had prompted the diversion. The following day, the aircraft was cleared for further operation, and Sánchez resumed his journey to participate in the summit discussions. The meeting focuses on strengthening political cooperation across Europe, addressing regional security concerns, and coordinating responses to emerging geopolitical challenges. Officials have emphasized that the incident was strictly technical in nature. There were no indications of adverse weather conditions, external interference, or security threats linked to the diversion. Aviation authorities handled the situation in accordance with established safety protocols, ensuring the safe outcome of the flight. The aircraft involved belongs to Spain’s official government fleet used for transporting senior state officials, including the Prime Minister and members of the royal or diplomatic delegation. Unlike commercial flights, such aircraft operate under military aviation command and are deployed for high-level international travel and state duties.

Incidents

Spanish PM’s Aircraft Makes Emergency Landing In Ankara Due To Technical Fault

Aviation Today News Desk / May 5, 2026

Ankara, Turkey: An aircraft carrying Pedro Sánchez was forced to divert and make an emergency landing at Ankara after a

Manchester, United Kingdom: A Jet2 passenger aircraft bound for the Greek island of Crete was forced to carry out an emergency landing at Manchester Airport after it was struck by a flock of geese shortly after take-off, leading to a precautionary diversion and a rapid response from the flight crew. The incident occurred during the initial climb phase of the flight, when the aircraft encountered a bird strike involving geese. Due to the size and potential impact of such birds, the crew immediately assessed the situation for any possible engine or structural damage before deciding to return to the departure airport as a safety precaution. Following standard aviation procedures, the pilots declared an emergency and coordinated with air traffic control to prioritise an immediate return. The aircraft safely landed without further incident, and no injuries were reported among passengers or crew on board. Emergency services were placed on standby as a precautionary measure in line with airport emergency response protocols. However, their intervention was not required after the aircraft came to a safe stop on the runway. Passengers were safely disembarked after landing, and airline staff arranged assistance for onward travel. Jet2 later confirmed that the decision to return was taken strictly in the interest of safety, emphasising that precautionary diversions are standard practice following suspected bird strikes. Bird strikes involving geese are considered more serious than smaller bird impacts due to their size and weight, particularly during take-off and landing when aircraft are operating at lower altitudes and higher thrust settings. In such scenarios, even a single impact can require a full technical inspection before the aircraft is cleared to fly again. The aircraft involved is expected to undergo a detailed engineering inspection to assess any potential damage to engines or external components before being returned to service. Jet2 has maintained that safety remains its highest priority, and that its flight crews are trained to respond immediately to any abnormal situation in accordance with strict operational procedures. Authorities have not released further technical details regarding the extent of any damage, and routine investigations are expected to follow standard aviation safety protocols.

Incidents

Jet2 Flight Made Emergency Landing At Manchester Airport After Geese Strike Mid-Air

Aviation Today News Desk / April 30, 2026

Manchester, United Kingdom: A Jet2 passenger aircraft bound for the Greek island of Crete was forced to carry out an

Nashville, United States: A serious aviation incident involving two Southwest Airlines Boeing 737 aircraft near Nashville International Airport has prompted a federal investigation after the jets came within close proximity following an air traffic control error that placed them on conflicting flight paths. The incident occurred as Southwest Flight 507, a Boeing 737 MAX 8 arriving from Myrtle Beach, initiated a go-around during its approach, while Southwest Flight 1152, a Boeing 737-700, was departing for Knoxville from a separate runway. According to preliminary findings and air traffic control audio reviewed by investigators, a controller issued a turn instruction to the arriving aircraft that inadvertently directed it into the departure path of the other jet, creating an immediate loss of safe separation. Air traffic control communications captured during the event indicate a rapidly escalating situation, with multiple instructions issued in quick succession, including climb directives that were later revised. In the cockpit, one of the pilots indicated the aircraft had already passed the point of conflict, reflecting how little time remained to resolve the situation through conventional means. Both aircraft subsequently received alerts from the onboard Traffic Collision Avoidance System (TCAS), which generated coordinated Resolution Advisories. The system instructed one aircraft to climb while directing the other to descend, allowing the crews to take immediate corrective action. Flight data suggests the jets of Southwest Airlines came within approximately 500 feet of each other, a distance considered a near midair collision under aviation safety standards. Despite the severity of the encounter, both flights continued safely with no reported injuries. Early assessments point to air traffic control error as the primary factor, compounded by the complexity of simultaneous runway operations during a go-around. Weather conditions, including reported gusty winds in the Nashville area, may also have contributed to the challenging operating environment at the time. The Federal Aviation Administration has launched a formal investigation and is expected to review controller actions, radar data, flight recordings, and adherence to separation protocols. Southwest Airlines stated that its flight crews responded in accordance with safety procedures and are cooperating fully with authorities. On April 15, 2026, a near-collision occurred at Charlotte Douglas International Airport when an American Airlines aircraft was forced to abruptly brake on the taxiway after a truck crossed directly in front of it, narrowly avoiding impact. The cockpit radio transmissions captured the crew reporting the close call to air traffic control. No injuries were reported, and the aircraft was able to continue and depart after a brief delay. The incident occurred on the airport tarmac and has drawn attention to ground movement safety, coming shortly after a fatal aircraft-vehicle collision at New York’s LaGuardia Airport, emphasising ongoing concerns over coordination between aircraft and ground vehicles.

Incidents

Southwest Jets In Near Midair Collision Over Nashville After ATC Error, FAA Probes

Aviation Today News Desk / April 21, 2026

Nashville, United States: A serious aviation incident involving two Southwest Airlines Boeing 737 aircraft near Nashville International Airport has prompted

Bengaluru, India: A Fly91 passenger flight operating from Hyderabad to Hubballi was diverted to Bengaluru on Sunday evening after adverse weather conditions over north Karnataka made landing at Hubballi airport unsafe. The aircraft, which had departed Hyderabad in the afternoon, was unable to complete its approach due to poor visibility and intense weather activity in the region, leading to an extended holding pattern for 3 hrs before the crew decided to divert as a precautionary measure resulting in an operational delay of around 2.5 to 3 hours. According to airline confirmation, the flight was scheduled to land in Hubballi around 4:30 pm but encountered deteriorating weather conditions during descent. The aircraft reportedly circled the Hubballi airspace for an extended period as pilots assessed landing feasibility. When conditions failed to improve, the crew diverted the flight to Bengaluru’s Kempegowda International Airport, where it landed safely. Passengers onboard experienced significant anxiety during the prolonged airborne phase, with reports and visual accounts suggesting distress inside the cabin as the aircraft continued holding over the region. Some passengers reportedly expressed concern over the extended circling, while cabin crew maintained communication and reassured passengers throughout the flight. Despite the tense situation, no medical emergencies or injuries were reported. All 22 passengers were reported safe. Fly91, in its official statement, categorically denied any technical malfunction and clarified that the diversion was carried out strictly due to weather-related safety concerns. The airline stated that the decision to hold and subsequently divert the aircraft was in line with standard operating procedures and aviation safety norms. It emphasized that the aircraft was fully serviceable and that the crew followed all regulatory guidelines issued for operations under adverse weather conditions. After diverting to Bengaluru, the aircraft landed safely and was later repositioned once weather conditions over Hubballi improved. The flight subsequently continued operations, ensuring passengers reached their destination. Officials reiterated that the safety of passengers remained the highest priority throughout the incident and that all procedures followed were in accordance with aviation safety protocols.

Incidents

Fly91 Hyderabad-Hubballi Flight Diverts To Bengaluru Amid Severe Weather Conditions

Aviation Today News Desk / April 20, 2026

Bengaluru, India: A Fly91 passenger flight operating from Hyderabad to Hubballi was diverted to Bengaluru on Sunday evening after adverse

AirTrafficControl

Jetstar A320 And Qatar 777 Narrowly Avoid Collision During Taxiing At Sydney Airport

FAA Investigates Close Call Between Two Delta Air Lines Aircraft At Atlanta Airport

American Airlines Aborts Takeoff At Miami After Unauthorised Jet Crosses Active Runway

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Akasa Air Flight Diverts To Lucknow After Weather Disruption And Low Fuel Alert

Cessna 421 Windshield Failure At 20,000 Feet Forces Emergency Landing In Missouri

Spanish PM’s Aircraft Makes Emergency Landing In Ankara Due To Technical Fault

Jet2 Flight Made Emergency Landing At Manchester Airport After Geese Strike Mid-Air

Southwest Jets In Near Midair Collision Over Nashville After ATC Error, FAA Probes

Fly91 Hyderabad-Hubballi Flight Diverts To Bengaluru Amid Severe Weather Conditions

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us