Air Traffic Control Archives

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

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

Laredo, United States: Federal investigators have launched an inquiry after a NetJets-operated Cessna Citation Latitude business jet crashed onto a major highway in Laredo, Texas, on the night of June 16, leaving one person dead and several others injured. The aircraft, identified as a Cessna Citation Latitude (Model 680A), was carrying six people when it went down on Loop 20 near the Clark Boulevard exit and the City Hall Annex shortly before 10:00 p.m. local time. Authorities confirmed one fatality, while the remaining occupants survived the accident with varying injuries. According to local officials, the aircraft was approaching the Laredo area after departing from Los Cabos, Mexico. Preliminary information indicates the flight crew reported mechanical difficulties before communication with air traffic control was lost. Moments later, emergency services received reports that an aircraft had crashed onto the highway. The impact triggered a major emergency response as the jet came to rest on the roadway and caught fire. Witness videos circulating online showed motorists stopping to assist survivors as flames engulfed portions of the aircraft. Several bystanders attempted to gain access to the cabin and cockpit while emergency responders rushed to the scene. Authorities said debris from the aircraft struck at least one vehicle traveling on Loop 20 during the accident. The occupants of that vehicle sustained injuries and were transported to a hospital. Their injuries were not believed to be life-threatening. Five officers from the Laredo Police Department were also hospitalized for smoke inhalation after helping remove occupants from the wreckage. Officials later reported that the officers were in stable condition. The identity of the deceased has not yet been released pending notification of next of kin. Authorities have also not publicly identified the remaining occupants aboard the aircraft. Videos recorded at the scene showed a heavily damaged fuselage with extensive fire damage. Witnesses and first responders were seen assisting passengers out of the wreckage as emergency crews worked to extinguish the fire and secure the crash site. The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have opened an investigation into the accident. The NTSB will lead the inquiry and is expected to examine the aircraft's maintenance history, flight data, cockpit communications, weather conditions, and any potential mechanical issues reported before the crash. At this stage, investigators have not determined the cause of the accident. While early reports indicate the crew reported a mechanical problem before the crash, officials have stressed that it is too early to draw conclusions regarding what led to the aircraft's loss of control and subsequent impact. Laredo Mayor Dr. Victor Treviño expressed condolences to those affected and urged the public to avoid speculation while investigators conduct a thorough examination of the circumstances surrounding the accident.

Aircraft Crashes

One Killed And Several Injured After Business Jet Crashes Onto Texas Highway In Laredo

Aviation Today News Desk / June 17, 2026

Laredo, United States: Federal investigators have launched an inquiry after a NetJets-operated Cessna Citation Latitude business jet crashed onto a

Detroit, United States: A Delta Air Lines Connection flight operating from Madison, Wisconsin, to Detroit, Michigan, declared a medical emergency after the co-pilot briefly lost consciousness during the aircraft’s approach and landing phase, according to airline statements and air traffic control (ATC) communications. The incident occurred on May 23, 2026, aboard a flight operated by Endeavor Air, a wholly owned regional subsidiary of Delta Air Lines. The aircraft departed from Dane County Regional Airport and was arriving at Detroit Metropolitan Wayne County Airport when the emergency unfolded. According to ATC audio, the captain informed controllers that the first officer had become incapacitated during the approach. In the transmission, the captain stated: “Declaring a medical emergency, my first officer’s incapacitated.” Air traffic controllers subsequently cleared the aircraft for priority landing. The aircraft landed safely in Detroit without further incident. Delta confirmed that paramedics met the flight after it taxied to the gate and that the first officer had regained consciousness by the time emergency personnel boarded the aircraft. The co-pilot was then transported to a hospital for medical evaluation. Flight tracking data indicated the flight completed the journey in approximately one hour and arrived around 20 minutes ahead of schedule despite the emergency declaration. No passengers or cabin crew members were reported injured during the incident. In a statement, Delta said safety remained its highest priority and praised the crew’s handling of the situation. The airline stated that the professionalism of the Endeavor Air crew and the response of emergency personnel helped ensure the flight concluded safely. The airline did not disclose the medical cause behind the co-pilot’s temporary loss of consciousness. There was also no indication of any technical or mechanical issue involving the aircraft itself. The incident also came days after another unrelated pilot medical emergency involving a Jet2.com flight traveling from Tenerife, Spain, to Birmingham, United Kingdom, which diverted to Porto, Portugal, after one of the pilots reportedly became unwell mid-flight.

Incidents

Delta Connection Flight Declares Emergency After Co-Pilot Loses Consciousness During Landing

Aviation Today News Desk / May 27, 2026

Detroit, United States: A Delta Air Lines Connection flight operating from Madison, Wisconsin, to Detroit, Michigan, declared a medical emergency

Tokyo, Japan: A Skymark Airlines Boeing 737 operating a domestic flight from Tokyo’s Haneda Airport to Fukuoka made an emergency return on Monday after the crew detected a landing gear tire abnormality mid-flight, later confirmed to involve a ruptured tire, according to Japan’s transport ministry and airline officials. The aircraft, carrying 169 passengers and crew, departed Haneda shortly after 3 p.m. local time and proceeded normally for nearly two hours before the flight crew identified a technical issue related to the landing gear system. Following standard safety procedures, the pilots declared an emergency and initiated a precautionary return to Haneda Airport. The aircraft landed safely back at Haneda without any injuries reported among passengers or crew members. The airline confirmed that all onboard remained safe throughout the incident and that the situation was handled in line with established emergency protocols. After landing, inspections conducted by airport authorities and Japan’s Ministry of Land, Infrastructure, Transport and Tourism confirmed that one of the aircraft’s tires had ruptured. Officials have not yet determined whether the damage occurred during takeoff, in-flight, or during landing gear operation after departure. Following the emergency landing, Haneda Airport temporarily closed Runway C to conduct safety inspections and remove any possible debris or rubber residue. The runway was later reopened at around 7:40 p.m. local time after checks confirmed safe operating conditions and no structural damage. Skymark Airlines operates a major domestic network from Haneda, connecting key cities across Japan, including Fukuoka, Sapporo, and Okinawa. The airline has not reported any further operational disruptions related to the incident, though the aircraft will undergo a detailed technical inspection before returning to service. Authorities are continuing to review the cause of the tire rupture as part of standard post-incident safety procedures.

Incidents

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

Aviation Today News Desk / May 26, 2026

Tokyo, Japan: A Skymark Airlines Boeing 737 operating a domestic flight from Tokyo’s Haneda Airport to Fukuoka made an emergency

Investigation

AAIB Flags Civil-Military ATC Coordination Lapses In Air India-Navy Helicopter Near Miss

Aviation Today News Desk / May 24, 2026

Port Blair, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its final investigation report into a serious midair proximity

Kansas City, United States: An American Airlines regional jet operating as American Eagle Flight 5318 made an emergency landing after smoke was reported inside the cabin while the aircraft was approaching its destination in Kansas City, according to airline officials and air traffic control recordings. The flight, operated by PSA Airlines using a Bombardier CRJ-900 regional jet, had departed from Ronald Reagan Washington National Airport and was en route to Kansas City with 76 passengers and crew members onboard. The emergency unfolded shortly before landing when the crew detected smoke inside the aircraft. Air traffic control audio captured the pilot declaring an emergency as the aircraft neared the airport. In the transmission, the pilot stated, “Bluestreak 5318, declaring an emergency. We’re landing,” signaling the urgency of the situation. The aircraft was reportedly about two miles from the runway when the emergency was declared. Emergency response teams were immediately dispatched and positioned along the runway as the jet prepared for landing. The aircraft landed safely without further incident. Following touchdown, passengers were evacuated onto the taxiway as firefighters and emergency personnel inspected the aircraft. Images and videos shared online showed passengers exiting through overwing exits and standing on the tarmac while first responders surrounded the regional jet. Among those onboard was U.S. Congressman Tracey Mann, who later shared details of the incident on social media. In a video posted after the landing, Mann thanked emergency responders and confirmed smoke had been detected onboard the aircraft. “There was smoke on our aircraft and so we landed and are now sitting on the tarmac,” he said in the video, while also expressing appreciation for airport fire and rescue crews responding to the emergency. American Airlines later issued a statement emphasizing that passenger and crew safety remained the airline’s highest priority. The carrier apologized to customers for the disruption and said maintenance teams would inspect the aircraft to determine the source of the smoke indication. The Federal Aviation Administration confirmed it has opened an investigation into the incident. Smoke or fumes inside an aircraft cabin are treated as serious in-flight emergencies because they can indicate electrical malfunctions, overheating systems, or other onboard hazards that may escalate rapidly if not contained. No injuries were immediately reported following the emergency landing, and passengers were later assisted by airline personnel at the airport while arrangements for onward travel were being made.

Incidents

American Airlines Regional Jet Makes Emergency Landing After Smoke Reported In Cabin

Aviation Today News Desk / May 16, 2026

Kansas City, United States: An American Airlines regional jet operating as American Eagle Flight 5318 made an emergency landing after

Airports

FAA Announces $16.5M Nationwide Airport Vehicle Transponder Plan After LaGuardia Crash

Aviation Today News Desk / May 15, 2026

Washington, United States: The Federal Aviation Administration (FAA) has announced a nationwide initiative to equip thousands of airport vehicles with

Air Traffic Control

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

One Killed And Several Injured After Business Jet Crashes Onto Texas Highway In Laredo

Delta Connection Flight Declares Emergency After Co-Pilot Loses Consciousness During Landing

Skymark Boeing 737 Makes Emergency Return To Haneda After Tire Rupture

AAIB Flags Civil-Military ATC Coordination Lapses In Air India-Navy Helicopter Near Miss

American Airlines Regional Jet Makes Emergency Landing After Smoke Reported In Cabin

FAA Announces $16.5M Nationwide Airport Vehicle Transponder Plan After LaGuardia Crash

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us