Aviation Incident Archives

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai International Airport late Tuesday night, August 11, after its left engine became inoperative shortly before landing. The aircraft was carrying 224 passengers and crew members. A full emergency was declared at Chennai Airport at 11:29 p.m. IST, with emergency response teams placed on standby. The aircraft subsequently landed safely on Runway 25 at 11:37 p.m., with all 224 people on board safe and no injuries reported. The flight was scheduled to arrive at 11:30 p.m., making the actual landing seven minutes later than scheduled. According to officials from the Airports Authority of India (AAI), the aircraft reported the technical problem while approaching Chennai. The pilot noticed that the left engine had failed while preparing for landing and alerted air traffic control. Following the alert, airport authorities activated the emergency response arrangements to facilitate the aircraft's safe arrival. The emergency was formally withdrawn at 11:47 p.m., around 10 minutes after the aircraft touched down. Chennai airport authorities said normal operations continued following the incident, with no disruption to airport operations reported. The declaration of a full emergency was a precautionary measure that allowed airport fire, rescue and other emergency services to remain ready for the aircraft's arrival. The aircraft landed without an accident, and there was no reported evacuation, casualty or injury among the 224 people on board. At present, the specific technical cause of the left-engine failure has not been publicly established. The available reports describe the condition as a left-engine failure or a “left engine inoperative condition” and do not provide details about the nature of the malfunction, engine damage or whether a particular component failed. Further technical examination of the aircraft is expected to establish the cause.

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

Aviation Today News Desk / August 12, 2026

Chennai, India: An IndiGo Airbus A321neo operating flight 6E-723 from Kolkata to Chennai made a precautionary emergency landing at Chennai […]

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina to Charlotte Douglas International Airport in North Carolina, made an emergency return to Myrtle Beach on Monday, August 10, after reportedly striking a flock of birds shortly after takeoff and experiencing an engine malfunction. The aircraft took off from Myrtle Beach at about 8:11 a.m. local time and was only minutes into the flight when the crew reported the problem to air traffic control. According to air traffic recordings obtained through LiveATC.net, the pilot declared a Mayday, saying, “Mayday, mayday, mayday. We’ve got an engine problem here.” The crew subsequently reported an engine malfunction as the aircraft turned back toward Myrtle Beach. Reports indicate the aircraft had struck birds during its climb, with another pilot who witnessed the event telling air traffic control, “I saw he took up birds, it looked like, at least in the left side engine.” The reported bird ingestion involved the aircraft’s left engine, beneath the left wing. Passengers recorded video showing bright orange flames and sparks appearing from the left side of the aircraft beneath the wing. Passenger Patrick Gotwalt captured footage of the event, while witnesses on the ground also reported hearing several loud popping sounds and seeing orange flashes from the aircraft’s left side. Lindsey Mackey, who was on the ground near the beach, told CNN that she heard loud popping noises before noticing orange flashes coming from the aircraft’s left wing. The visual evidence showed what appeared to be flames or sparks coming from the area around the left engine as the aircraft continued flying back toward the airport. As the Boeing 737-800 returned, airport emergency personnel prepared for its arrival. Workers subsequently found substantial bird remains and debris on the runway. Radio communications from the airport included the statement, “We’ve got a lot of bird debris out here. We’re going to grab as many big pieces as we can.” The debris provided physical evidence consistent with reports that the aircraft had struck birds. Flight 1760 landed safely back at Myrtle Beach at approximately 8:40 a.m., after spending roughly 15 minutes in the air, according to reports. The aircraft taxied to the gate under its own power, allowing passengers to disembark normally. No injuries were reported. The flight was carrying 172 passengers/customers and nine crew members, according to the New York Post, although the airline's statement cited by The U.S. Sun referred specifically to the 172 customers aboard. American Airlines said the aircraft was removed from service for a maintenance inspection following the incident. In a statement, the airline said, “The aircraft landed safely and has been taken out of service to be inspected by our maintenance team.” The airline added, “Our team worked to get customers on their way to Charlotte (CLT) on a replacement aircraft.” American also thanked its employees for their professionalism and passengers for their understanding. The aircraft was therefore not continued to Charlotte after the emergency landing. American arranged a replacement aircraft so the affected passengers could continue their journey to Charlotte. Although video footage showed flames coming from the left engine area, the New York Post reported that there was no internal engine fire, indicating that the visible flames did not necessarily represent a sustained fire inside the engine. The aircraft was nevertheless removed from service for inspection. The Federal Aviation Administration confirmed that the aircraft landed at Myrtle Beach at about 8:40 a.m. and said it would investigate the incident. The investigation is expected to establish the precise nature of the engine malfunction and assess the bird-strike evidence. The bird remains recovered after the incident are also significant because wildlife remains from aircraft strikes can be examined to determine the species involved. The FAA's Smithsonian Feather Identification Lab program routinely analyzes bird remains from aircraft strikes to help identify the species and improve airport wildlife-management measures.

Incidents

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

Aviation Today News Desk / August 12, 2026

Myrtle Beach, United States: American Airlines Flight 1760, a Boeing 737-800 operating from Myrtle Beach International Airport in South Carolina

Baramati, India: A Cessna 172S training aircraft operated by Academy of Carver Aviation Pvt. Ltd. veered off the runway during a training exercise at Baramati Airfield in Maharashtra’s Pune district on Sunday, August 9, 2026. The aircraft, registered VT-SEX, had two people onboard flight instructor Captain Chirag Shashikant Doifode and cadet Abhijeet Jundre. Both escaped unharmed. The incident occurred at about 12:30 pm. The four-seat aircraft was conducting a Circuit and Landing Emergencies training exercise, during which the trainee was required to practise landing following an emergency scenario. Police and aviation authorities said the aircraft was involved in rejected-take-off exercises as part of the training sequence. According to the Ministry of Civil Aviation, the DGCA-approved Academy of Carver Aviation aircraft “suffered a runway excursion at Baramati Airfield.” The ministry said the aircraft “was involved in a Circuit and Landing Emergencies (CL Emergencies) training exercise” and was unable to stop within the paved runway surface before veering onto the extended paved area beyond the runway threshold. A DGCA Air Safety team was sent to the site to conduct a preliminary investigation. Police said the aircraft initially entered the runway through Link Bravo and lined up at the threshold of Runway 29, where it carried out a rejected take-off exercise. It was subsequently positioned at the threshold of Runway 11 for another rejected take-off exercise. During the sequence, the aircraft could not be brought to a complete stop and continued beyond the runway before veering onto the grassy area. Police said the aircraft travelled roughly 20 feet beyond the runway end before entering the grass. Inspector Narayan Pawar said, “The brakes of the aircraft seem to have not worked,” while adding that the situation was under control. Pune Rural Deputy Superintendent of Police Chaitanya Kadam confirmed that both occupants were safe. The aircraft sustained damage during the runway excursion. The Ministry of Civil Aviation said, prima facie, damage was found to the propeller, engine cowling and nose landing gear, with a detailed assessment to be conducted by the competent authorities. The cause of the incident has not yet been established. Police said investigators were examining whether the aircraft developed a technical problem or whether another factor contributed to the runway excursion. A senior police official said, “It is too early to comment on anything,” as the investigation was still at an early stage. Pune Rural Superintendent of Police Sandip Singh Gill said the aircraft skidded while landing. In a statement reported by Economic Times, Gill said: “An aircraft VT-SEX was involved in a runway excursion incident at Baramati Airfield during a training exercise, with Capt Chirag Shashikant Doifode and Cadet Abhijeet Jundre on board. No injuries have been reported.” The aircraft involved was a Cessna 172S, a four-seat single-engine trainer. The DGCA’s list of approved flying training organisations as of March 30, 2026, lists VT-SEX as a Cessna 172S operated by Academy of Carver Aviation Pvt. Ltd., whose flying base is near Baramati Airport. Carver Aviation’s own fleet information also lists VT-SEX among its training aircraft. There was therefore no injury to the cadet, no injury to the instructor and no fatality in the August 9 incident. The aircraft was not carrying passengers beyond the two flight-training occupants, and the incident occurred during a scheduled training exercise rather than a passenger operation. The incident has nevertheless renewed scrutiny of safety conditions at Baramati. Hindustan Times described it as the seventh aircraft accident or incident linked to Baramati’s aviation and flight-training operations since 2022, prompting calls for a broader review of infrastructure, operational systems and oversight. Aviation expert Dhairyashil Vandekar said the latest incident should trigger a comprehensive review of the airfield. “It is important that the safety and confidence of trainee pilots must be paramount,” Vandekar said, adding that Baramati’s infrastructure and operational systems need to keep pace with the volume of flying activity. He called for appropriate air traffic services, modern navigation and communication systems and stronger emergency-response infrastructure. The DGCA is now examining the circumstances and contributing factors behind the August 9 runway excursion. At present, authorities have not attributed the incident to a confirmed brake failure, mechanical defect, pilot error or any other specific cause. The investigation is expected to establish what led the Cessna 172S to leave the paved runway during the training exercise.

Incidents

Cessna 172S Suffers Runway Excursion At Baramati During Training, 2 Escape Unhurt

Aviation Today News Desk / August 10, 2026

Baramati, India: A Cessna 172S training aircraft operated by Academy of Carver Aviation Pvt. Ltd. veered off the runway during

Atlanta, United States: Delta Air Lines Flight 2204 returned to Hartsfield-Jackson Atlanta International Airport on August 8 after fumes were reported in the flight deck shortly after departure, prompting an emergency landing and evacuation on the taxiway. The Boeing 757-200 was operating from Atlanta to Orlando International Airport in Florida when the flight crew detected the fumes and followed procedures to return to Atlanta. According to the Federal Aviation Administration, the aircraft landed safely at about 8 a.m. local time. The aircraft was carrying approximately 200 passengers and six crew members. After landing, passengers were evacuated using the aircraft’s emergency slides onto the taxiway rather than remaining onboard. Video shared by a passenger on TikTok showed passengers moving toward the exits and sliding onto the tarmac, while crew members could be heard directing them to leave their belongings behind and evacuate. A passenger, Jordan Conlin, who was traveling with his family, told Fox 5 Atlanta that the pilot announced that he and the co-pilot were wearing oxygen masks because of fumes in the cockpit and that the aircraft was turning back to Atlanta. Conlin also recalled the pilot instructing passengers to “brace” during the landing, describing the evacuation as chaotic as passengers left the aircraft. One crew member and one passenger received medical attention following the incident, while the remaining passengers were transported by ground crews to the terminal. Delta subsequently arranged a replacement aircraft to take the passengers to Orlando. Delta confirmed that the crew followed established procedures after reports of fumes in the flight deck and said a slide evacuation took place on a taxiway. The airline apologized to passengers, saying safety remained its top priority. The FAA said it is investigating the incident. The agency confirmed that Flight 2204 returned safely to Atlanta after reported smoke in the cockpit and that passengers evacuated via emergency slides onto the taxiway. The aircraft was taken for inspection following the incident. No fatalities were reported, and the available reports indicate that the aircraft landed safely before the evacuation was carried out. The precise source of the fumes or smoke has not been established publicly. The FAA investigation and aircraft inspection are expected to provide further information about what caused the reported condition in the flight deck.

Incidents

Delta Flight 2204 Makes Emergency Return To Atlanta After Fumes Reported In Cockpit

Aviation Today News Desk / August 10, 2026

Atlanta, United States: Delta Air Lines Flight 2204 returned to Hartsfield-Jackson Atlanta International Airport on August 8 after fumes were

California, United States: A United Airlines Boeing 737-800 operating Flight 1189 from San Francisco to Los Cabos, Mexico, returned to San Francisco International Airport (SFO) on Thursday after one of its tires was damaged during the takeoff roll, prompting the aircraft to turn back shortly after departure. Few media, citing air traffic control audio, reported that the tire burst during the takeoff roll, while United officially described the incident as damage to one tire. Flight-tracking data showed the aircraft turning back after roughly an hour in flight before landing safely at SFO at about 11:44 a.m. The aircraft was a Boeing 737-800 carrying 165 passengers and eight crew members. Despite the reported tire damage during departure, the aircraft completed the return flight and landed safely at its departure airport. United said there were no reported injuries among those onboard. United Airlines confirmed the incident in a statement, saying, “United flight 1189 sustained damage to one tire while departing San Francisco and safely returned to the airport.” The airline did not specify whether the tire failure was caused by a mechanical defect, debris, wear or another factor, and it did not identify the exact tire involved. Passengers were not taken directly into the terminal after landing. Instead, United said customers “deplaned via airstairs on the tarmac and were taken by bus to the terminal.” The procedure followed the aircraft’s return to SFO while the aircraft and the damaged tire were being inspected. United said it arranged another aircraft to continue the passengers’ journey to Los Cabos later that afternoon, stating, “We've arranged for a different aircraft to take them to Los Cabos later this afternoon.” This allowed the affected passengers to continue their original trip after the Boeing 737-800 was taken out of service for inspection. The incident also affected airport operations, the blocked runway caused delays to some other flights at SFO. There was no reported crash or emergency landing accident, but the circumstances surrounding the tire damage remain under review. The Federal Aviation Administration has said it will investigate the incident. As of the latest available update there are no further FAA findings and official cause has not been released.

Incidents

United Flight 1189 Returns To SFO After Tire Damage During Takeoff, FAA Probes

Aviation Today News Desk / August 7, 2026

California, United States: A United Airlines Boeing 737-800 operating Flight 1189 from San Francisco to Los Cabos, Mexico, returned to

New Delhi, India: An Air India Airbus A320 operating flight AI2379 from Phuket, Thailand, to New Delhi encountered severe turbulence on Tuesday, August 4, leaving several passengers and cabin crew with minor injuries before the aircraft landed safely at Indira Gandhi International Airport (DEL). The incident occurred during the flight's final phase, although reports differ on the exact timing. While early media reports said the turbulence struck during the aircraft's descent into Delhi, Air India later clarified that the aircraft encountered turbulence while in cruise, resulting in a brief change in altitude. The Airbus A320, carrying 134 passengers, landed safely shortly after 11:00 a.m. IST. All passengers and crew disembarked normally after arrival, with Air India's airport and medical teams meeting the aircraft at the gate. According to PTI, 12 people, including passengers and cabin crew, sustained minor injuries during the turbulence event. Other reports indicated that around 10 passengers and two cabin crew members were taken to the Medanta medical facility at Delhi Airport for precautionary medical assessment. Seven passengers were later moved to Fortis Hospital in Vasant Kunj for further evaluation, scans, and observation. Air India said there were no serious injuries. Some early reports stated the aircraft experienced a sudden altitude drop of approximately 300 feet during the turbulence, causing unrestrained occupants to be thrown against the cabin interior and resulting in minor injuries. Air India, however, described the event as a "momentary change in altitude" without confirming the reported altitude deviation. Speaking to news agency ANI, a passenger on board the flight claimed the aircraft experienced a sudden jolt about an hour and a half into the journey while most passengers were asleep. According to the passenger, the aircraft abruptly dropped and swayed violently for nearly two to three minutes, leaving several people injured. In an official statement, Air India said, "The safety and well-being of our passengers and crew remain Air India's highest priority." The airline added that a small number of passengers and crew members requiring medical assessment were taken to the airport medical facility as a precaution and confirmed that it is providing all necessary assistance while cooperating with the relevant authorities reviewing the incident.

Incidents

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

Aviation Today News Desk / August 4, 2026

Update 05 August, 2026: Air India has since confirmed that flight AI2379 experienced a sudden loss of altitude during cruise

Tokyo, Japan: An All Nippon Airways (ANA) flight arriving from Shanghai carried out a precautionary go-around during its approach to Tokyo Haneda Airport on Tuesday morning after the aircraft's onboard Traffic Collision Avoidance System (TCAS) issued a Resolution Advisory, prompting the flight crew to discontinue the landing and climb away. Japan's Ministry of Land, Infrastructure, Transport and Tourism (MLIT) confirmed that one of the ministry's Civil Aviation Bureau flight inspection aircraft had departed from Haneda's Runway D and was operating in the vicinity when the TCAS alert occurred. The ministry said it is investigating the circumstances surrounding the event. The incident involved ANA Flight NH968, operating from Shanghai Pudong International Airport to Tokyo Haneda Airport, at approximately 6 a.m. local time on August 4. According to ANA, the pilots followed the TCAS instruction as designed, executing an immediate climb before later returning to land safely. No injuries were reported among passengers or crew, and the aircraft landed without further incident. Flight-tracking data published by Flightradar24 indicated that NH968 was on final approach to Haneda's Runway C while the Civil Aviation Bureau aircraft had departed from the intersecting Runway D shortly beforehand. The available tracking data showed the two aircraft operating in close proximity, although authorities have not released the minimum separation distance or determined whether air traffic separation standards were breached. Japanese media reported that the inspection aircraft departed as the ANA flight was established on approach, resulting in the collision avoidance system issuing its warning. However, aviation authorities have not yet published a preliminary investigation report detailing the sequence of events or identifying any operational errors. The incident did not result in damage to either aircraft, and airport operations continued after the go-around. Authorities have not announced whether the occurrence will be classified as a serious incident or whether a formal safety investigation will be conducted by the Japan Transport Safety Board. At the time of publication, Japanese authorities had not released further findings, and the investigation remains ongoing.

Incidents

ANA Flight Performs Go-Around At Haneda After TCAS Alert Near Government Aircraft

Aviation Today News Desk / August 4, 2026

Tokyo, Japan: An All Nippon Airways (ANA) flight arriving from Shanghai carried out a precautionary go-around during its approach to

Gujarat, India: An IndiGo flight operating from Dubai to Mumbai made a precautionary emergency landing at Rajkot International Airport in Gujarat on Monday, July 27, after the crew reportedly detected a smoke alert from the aircraft's cargo hold area. All 194 people onboard, comprising 187 passengers and seven crew members, safely disembarked after the Airbus A321 landed at Rajkot. The flight, IndiGo 6E 1452, was operating from Dubai International Airport to Chhatrapati Shivaji Maharaj International Airport in Mumbai. The aircraft departed Dubai at around 11:30 a.m. IST before being diverted to Rajkot as a precaution following the reported smoke indication from the cargo hold. An airport official said, "Flight IGO1452, aircraft type A321, operating from Dubai to Mumbai, was diverted to Rajkot due to smoke detected in the cargo hold area." Airport authorities were alerted to the situation at around 2:45 p.m., following which a full emergency was declared at Rajkot International Airport. Emergency response teams, including fire tenders, ambulances, rescue vehicles and medical personnel, were deployed as part of the airport's emergency procedures. Local hospitals and police authorities were also alerted and kept on standby. The flight crew initially detected smoke indicators in the cargo hold during the mid-air journey, prompting the diversion to Rajkot as a precaution. IndiGo, however, said in a statement: “IndiGo flight 6E 1452, operating from Dubai to Mumbai, was diverted to Rajkot International Airport today as a precautionary measure due to a technical issue. The aircraft landed safely at Rajkot, and all passengers have deboarded securely. An inspection of the aircraft is currently underway before it is cleared to resume operations,” the spokesperson said. The Airbus A321 landed safely at Hirasar International Airport, also known as Rajkot International Airport, at approximately 3:27 p.m. Police, security personnel and firefighters were present at the airport as the aircraft arrived. No injuries were reported among the passengers or crew. Sources at the airport said IndiGo was arranging another aircraft to carry the affected passengers onward to Mumbai. The exact cause was not immediately established, and reports did not confirm whether an actual fire occurred in the cargo compartment. Authorities were expected to examine the aircraft to determine the cause. The incident triggered the airport's full emergency response protocol, but the aircraft completed the landing without any reported damage or injuries.

Incidents

IndiGo Dubai-Mumbai Flight Makes Emergency Landing After Reported Cargo Hold Smoke

Aviation Today News Desk / July 28, 2026

Gujarat, India: An IndiGo flight operating from Dubai to Mumbai made a precautionary emergency landing at Rajkot International Airport in

Eugene, United States: An Alaska Airlines Boeing 737-800 operating Flight AS471 from Santa Ana, California, to Seattle, Washington, safely diverted to Eugene, Oregon, on July 23, 2026, after the crew received a low oil quantity and pressure warning involving the aircraft's left-hand CFM56 engine. The aircraft, registered as N563AS, was cruising at 36,000 feet (FL360) when the issue occurred approximately 90 nautical miles south-southeast of Eugene, Oregon. In response to the low oil pressure indication, the flight crew precautionarily shut down the affected engine and initiated a diversion to Eugene Airport (EUG). Flight AS471 was carrying 161 passengers and six crew members at the time of the incident. Following the engine shutdown, the pilots continued the flight safely with the remaining engine operating and diverted to Eugene as a precaution. The aircraft landed safely on Runway 34L at Eugene Airport approximately 25 minutes after the diversion was initiated. No injuries were reported among the passengers or crew following the landing. The aircraft was subsequently taken out of service for inspection and maintenance to determine the precise cause of the low oil quantity and pressure indication. The incident involved one of the aircraft's two CFM56 engines, with the left-hand engine being shut down as a precaution. Passengers were later transferred to a replacement Boeing 737-800, registered as N597AS, to continue their journey to Seattle. The replacement aircraft eventually arrived in Seattle approximately four hours later than the original scheduled arrival time. The incident demonstrates the procedures followed by flight crews when an engine-related warning occurs during cruise. Boeing 737-800 aircraft are designed and certified to continue flight safely following the loss or shutdown of one engine, allowing pilots to divert to a suitable airport while maintaining control of the aircraft. The aircraft's diversion to Eugene allowed the crew to land safely and have the affected engine inspected before the aircraft could return to normal operations. No injuries were reported in connection with the incident.

Incidents

Alaska Airlines 737 Diverts To Eugene After Engine Oil Warning Prompts Mid-Air Shutdown

Aviation Today News Desk / July 27, 2026

Eugene, United States: An Alaska Airlines Boeing 737-800 operating Flight AS471 from Santa Ana, California, to Seattle, Washington, safely diverted

Dublin, Ireland: An American Airlines Boeing 787-9 Dreamliner operating Flight AA719 from Rome Fiumicino Airport (FCO) to Philadelphia International Airport (PHL) diverted to Dublin Airport (DUB) on July 25, 2026, after several flight attendants reportedly became dizzy and unwell during the transatlantic flight. The aircraft, registered N840AN, landed safely in Dublin after the pilots reported a medical emergency to air traffic control. American Airlines later confirmed that there was a reported odor onboard, although the precise source of the odor and the reason for the crew members' symptoms have not been publicly established. Flight AA719 departed Rome Fiumicino at approximately 12:40 p.m. local time, with other reports placing the departure just before 1 p.m. The Boeing 787-9, a 2019-delivered aircraft, was scheduled to make the roughly eight-and-a-half-hour journey to Philadelphia. According to flight-tracking data, the aircraft climbed to approximately 38,000 to 39,000 feet and continued across France before heading over the North Atlantic. About four hours into the flight, the pilots turned the aircraft toward Ireland after reporting a medical issue onboard. Air traffic control was informed that several flight attendants were feeling sick and that medical assistance would be required on arrival. Dublin was selected as the diversion airport, with the aircraft subsequently landing safely on Runway 28L approximately six hours after leaving Rome. Medical responders were reportedly standing by when the aircraft arrived. Reportedly, six of the nine flight attendants onboard became ill during the flight, although American Airlines has not yet confirmed the report. The available reports also indicate that the affected flight attendants experienced symptoms including dizziness and feeling unwell. There is no indication in the reports reviewed that the crew members were incapacitated. Nevertheless, with a substantial portion of the cabin crew reportedly affected at the same time, the pilots elected to divert rather than continue the flight across the Atlantic. After the aircraft landed in Dublin, the passengers did not immediately continue to Philadelphia. Reports said American Airlines did not have a replacement cabin crew available to operate the onward journey, while the reason for the reported illness remained unclear. The original flight was therefore unable to continue as planned, and the onward service was cancelled. The aircraft remained in Dublin, while reports indicated that passengers were to be accommodated and rebooked for onward travel. A separate recovery flight, identified as AA9601, subsequently appeared in the schedule for the following Monday, although reports also indicated that its departure was later delayed. American Airlines subsequently provided a statement confirming the diversion but did not publicly confirm that six flight attendants had fallen ill. The airline said: "On July 25, American Airlines flight 719, from Rome (FCO) to Philadelphia (PHL), diverted to Dublin (DUB) due to a reported odor onboard. We appreciate the understanding of our customers and thank our team members for their professionalism." The statement establishes the reported odor as the reason for the diversion but does not identify the source of the odor or confirm whether it was directly responsible for the flight attendants' symptoms. No official explanation has so far been released publicly detailing what caused the odor or why multiple members of the cabin crew reportedly became unwell at approximately the same time.

Incidents

American Airlines Flight Diverts To Dublin After Six Cabin Crew Reportedly Became Unwell

Aviation Today News Desk / July 27, 2026

Dublin, Ireland: An American Airlines Boeing 787-9 Dreamliner operating Flight AA719 from Rome Fiumicino Airport (FCO) to Philadelphia International Airport

Aviation Incident

IndiGo Airbus A321neo Makes Emergency Landing In Chennai After Left-Engine Failure

American Airlines Flight 1760 Makes Emergency Landing After Bird Strike Damages Engine

Cessna 172S Suffers Runway Excursion At Baramati During Training, 2 Escape Unhurt

Delta Flight 2204 Makes Emergency Return To Atlanta After Fumes Reported In Cockpit

United Flight 1189 Returns To SFO After Tire Damage During Takeoff, FAA Probes

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

ANA Flight Performs Go-Around At Haneda After TCAS Alert Near Government Aircraft

IndiGo Dubai-Mumbai Flight Makes Emergency Landing After Reported Cargo Hold Smoke

Alaska Airlines 737 Diverts To Eugene After Engine Oil Warning Prompts Mid-Air Shutdown

American Airlines Flight Diverts To Dublin After Six Cabin Crew Reportedly Became Unwell

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us