airport emergency 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 […]

Chicago, United States: Southwest Airlines Flight 1243 experienced a landing incident at Chicago Midway International Airport on the morning of August 3 after both nose landing gear tires lost air pressure during touchdown, prompting an emergency response from airport and city fire crews. The aircraft was safely brought to a stop on the runway, and no injuries were reported. According to Southwest Airlines, Flight 1243 was operating from Southwest Florida International Airport (RSW) in Fort Myers, Florida, to Chicago Midway International Airport (MDW) when the incident occurred during landing. The airline said both nose landing gear tires lost air pressure while the aircraft was landing in Chicago. Chicago Fire Department crews responded to the aircraft shortly after it came to a stop on the runway. Video from the scene showed emergency vehicles surrounding the aircraft as first responders assessed the situation. The aircraft remained on the runway while emergency personnel and airline maintenance teams carried out initial inspections. Passengers described smelling burnt rubber and seeing light smoke after the aircraft stopped. Passenger Mya Castro told ABC7 Chicago, "I realized we stopped and we weren't close to getting off the plane, and then I could smell the burnt rubber." Another passenger, Brian Rigsby, said, "Once we did come to a stop, we could see smoke coming. Not excessive, but we knew something was wrong." Southwest Airlines confirmed that maintenance personnel replaced the damaged nose gear tires before the aircraft was towed from the runway to the terminal gate. The airline said passengers were able to deplane normally after the aircraft reached the gate. In a statement, Southwest Airlines said: "Both nose gear tires lost air pressure while landing in Chicago." The carrier added that mechanics replaced the tires and the aircraft was subsequently towed to the gate. The airline did not disclose what caused the loss of tire pressure, and no indication has been given that a mechanical failure beyond the tires was involved. The response was precautionary, and no evacuation was reported. Emergency crews completed their assessment without incident, and no injuries among passengers or crew were reported. Chicago Midway International Airport continued normal operations following the response, while Southwest worked to return the aircraft to service after replacing the affected tires. The incident remains under review, with Southwest yet to provide further details on what led to the loss of air pressure in both nose landing gear tires during landing.

Incidents

Southwest Flight 1243 Lands Safely At Chicago After Nose Gear Tires Lose Pressure

Aviation Today News Desk / August 4, 2026

Chicago, United States: Southwest Airlines Flight 1243 experienced a landing incident at Chicago Midway International Airport on the morning of

Montreal, Canada: An Air Canada aircraft arriving from Los Angeles veered off a taxiway after landing at Montréal–Pierre Elliott Trudeau International Airport on Thursday, temporarily shutting down one of the airport's runways, disrupting flight operations and prompting an emergency response. No injuries were reported among passengers or crew. The incident occurred after the aircraft landed safely and was taxiing toward the terminal. While exiting the runway via a high-speed taxiway, the aircraft left the paved surface and came to rest with its landing gear in the adjacent grass. Images from the scene showed the aircraft upright with no visible signs of major structural damage or fire. Airport emergency vehicles responded immediately and surrounded the aircraft as a precaution while crews assessed the situation and ensured there were no fuel leaks or fire hazards. Passengers remained safe throughout the incident, and no injuries were reported. The aircraft remained stranded on the grassy area for several hours while recovery operations were carried out. The excursion forced Montréal-Trudeau Airport to temporarily close its north runway, reducing airport capacity and triggering delays, cancellations and operational disruptions across Air Canada's network. Several arriving aircraft were delayed or held while the affected runway remained unavailable. The disruption also impacted flights to and from several Canadian cities, including Vancouver, with airlines adjusting schedules as airport crews worked to remove the aircraft and restore normal operations. Although some reports noted wet weather and rain in the Montreal area around the time of the occurrence, aviation authorities have not indicated whether weather played any role in the incident. Likewise, there has been no official confirmation regarding any mechanical issue or flight crew-related factor. The event is being classified as a taxiway excursion rather than a runway accident. The aircraft landed safely before leaving the paved taxiway during ground movement, distinguishing the occurrence from an accident during takeoff or landing. The incident comes as airlines and airport operators continue to emphasize the importance of safe ground operations, where taxiway excursions, although relatively uncommon, can still cause significant operational disruption despite causing no injuries. Airport operations gradually resumed after recovery crews removed the aircraft and the affected runway was returned to service.

Incidents

Air Canada Jet Veers Off Taxiway After Landing At Montreal Airport, Disrupting Flights

Aviation Today News Desk / July 10, 2026

Montreal, Canada: An Air Canada aircraft arriving from Los Angeles veered off a taxiway after landing at Montréal–Pierre Elliott Trudeau

Fresno, United States: A Delta Air Lines regional flight operating from San Francisco International Airport (SFO) to Los Angeles International Airport (LAX) made an emergency landing at Fresno Yosemite International Airport (FAT) on Monday after the crew reported an engine-related issue. Delta Flight DL2725, diverted to Fresno as a precaution after experiencing engine problems during the short domestic flight. The aircraft landed safely at Fresno Yosemite International Airport shortly before 4:00 p.m. local time. According to Delta Air Lines, the aircraft taxied to the gate under its own power after landing. The airline confirmed that all 158 people on board 152 passengers and six crew members were safe, and no injuries were reported. Video from the airport showed the aircraft parked between two American Airlines aircraft following the emergency landing. Emergency response personnel were present as a standard precaution, but no evacuation was required. While initial reports described the event as being caused by engine issues, Delta later clarified that the diversion followed an engine indication warning. The airline has not disclosed the specific nature of the indication, and the aircraft has been removed from service for inspection by maintenance personnel. Passengers were safely deplaned after arriving at the gate, and Delta said it was working to re accommodate customers on alternate transportation to Los Angeles. The U.S. Federal Aviation Administration (FAA) is expected to review the incident as part of standard procedures for in-flight emergencies. The exact cause of the engine indication remains under investigation.

Incidents

Delta Flight Bound For Los Angeles Diverts To Fresno After Engine Warning Mid-Flight

Aviation Today News Desk / July 8, 2026

Fresno, United States: A Delta Air Lines regional flight operating from San Francisco International Airport (SFO) to Los Angeles International

New York, United States: A Delta Air Lines Airbus A321neo landed safely at New York’s John F. Kennedy International Airport (JFK) on June 16 after reports of a possible nose-wheel tire issue prompted a large-scale emergency response from airport and city authorities. Delta Flight 1966 was operating a scheduled service from San Juan, Puerto Rico, to New York-JFK when concerns emerged regarding the aircraft’s nose landing gear during its approach into the airport. Initial reports received by emergency responders indicated that the inbound aircraft may have been experiencing issues involving its front tires, leading authorities to prepare for a potential emergency landing. According to the New York City Fire Department (FDNY), a call was received at approximately 4:45 p.m. local time reporting that the aircraft had "two flat front tires." In response, the department initiated a precautionary second-alarm standby deployment, dispatching 46 units and 141 fire and emergency medical personnel to JFK Airport. The aircraft, an Airbus A321neo operated by Delta Air Lines, was carrying 170 passengers along with six crew members, consisting of two pilots and four flight attendants. Flight tracking data shows the aircraft landed safely at JFK at approximately 5:31 p.m. local time. Emergency vehicles were positioned alongside the runway as a precaution while the aircraft completed its landing. Following touchdown, the aircraft remained under observation before being cleared to continue taxiing to the terminal. The aircraft was subsequently escorted to Terminal 4, where it arrived without incident. No injuries were reported among passengers or crew. Following the landing, Delta Air Lines clarified that the situation was less severe than initially reported. The airline stated that maintenance inspections identified damage and tread wear to one tire rather than multiple flat or blown tires. "There was some damage to one tire, but not a major situation given the maintenance team determined the aircraft was suitable to continue taxiing over to the gate for the tire replacement rather than having to do so on the taxiway," Delta said in a statement. The airline added that the aircraft was able to taxi under its own power and that the emergency response proved largely precautionary. Video footage captured by local news helicopters after the landing appeared to show the aircraft’s nose-wheel tires still inflated, further supporting Delta’s assessment that the tire had sustained damage rather than a complete failure. No evacuation was required, and passengers disembarked normally after arrival. Delta has not indicated any further operational impact resulting from the incident. The circumstances surrounding the tire damage have not been publicly disclosed, and there has been no indication of any broader safety issue involving the aircraft.

Incidents

Delta Lands Safely At JFK After Tire Damage Report Triggers Major Emergency Response

Aviation Today News Desk / June 18, 2026

New York, United States: A Delta Air Lines Airbus A321neo landed safely at New York’s John F. Kennedy International Airport

Syracuse, United States: An American Eagle regional flight operating from Rochester, New York, to Philadelphia made a precautionary diversion to Syracuse Hancock International Airport after crew members reported fumes in the cockpit, prompting a response from emergency services upon landing. The incident occurred on June 14 when American Eagle Flight AA5907, operated with an Embraer ERJ-145LR regional jet, departed Frederick Douglass Greater Rochester International Airport at approximately 7:30 p.m. local time. The aircraft was bound for Philadelphia International Airport when the flight crew detected an unusual odor in the cockpit shortly after takeoff. According to airport officials and emergency response reports, the crew elected to divert the aircraft to nearby Syracuse Hancock International Airport as a precaution. The aircraft landed safely shortly after 8:00 p.m., roughly 30 minutes after departing Rochester. Emergency vehicles and medical personnel were positioned to meet the aircraft on arrival. Several passengers and crew members underwent medical evaluations following the landing. Reports from emergency dispatch communications indicated that the pilots experienced nausea after being exposed to the reported fumes. American Airlines later stated that the aircraft experienced a possible mechanical issue. The airline said maintenance personnel would inspect the aircraft before it returned to service. No injuries were reported during the incident, and the landing was completed without further complications. Flight tracking data showed the Embraer ERJ-145LR, registered N931AE, remained overnight in Syracuse before departing the following morning and continuing to Philadelphia after maintenance inspections were completed.

Incidents

American Eagle Flight Diverts To Syracuse After Cockpit Fumes Reported

Aviation Today News Desk / June 16, 2026

An American Eagle regional flight operating from Rochester, New York, to Philadelphia made a precautionary diversion to Syracuse Hancock International

Bangalore; India: A major aviation scare unfolded at Kempegowda International Airport on Tuesday evening after smoke was detected inside an IndiGo Airbus A321neo operating a Bengaluru-Chennai flight, forcing the emergency evacuation of more than 230 passengers and crew members just before takeoff. According to the Directorate General of Civil Aviation (DGCA) and airline officials, the incident involved IndiGo flight 6E 6017, which had begun taxiing towards the runway when smoke was observed inside both the cabin and cockpit, triggering an immediate emergency response. The aircraft had completed pushback and was taxiing for departure to Chennai when smoke was reported onboard. Following the detection, the flight crew immediately halted operations and ordered an emergency evacuation as a precautionary measure. All passengers were evacuated using the aircraft’s emergency escape slides on the taxiway, with airport fire and emergency response teams rushing to assist. The evacuation was completed before the aircraft could line up for takeoff. During the emergency evacuation, two passengers sustained minor injuries, according to DGCA and multiple media reports. They were provided immediate medical attention at the terminal and were reported to be in stable condition. Despite the panic, authorities confirmed that all passengers and crew were safely evacuated. IndiGo confirmed the incident and stated that safety procedures were followed immediately after smoke was detected. “On 26 May 2026, while IndiGo flight 6E 6017 from Bengaluru to Chennai was taxiing toward the runway for departure, smoke was noticed in the aircraft. In the interest of safety, an immediate evacuation was carried out, and all relevant authorities were informed. All customers and crew are safe and have been moved to the terminal, where they are being attended to by our teams to ensure their well-being,” the airline said in its official statement. The airline also arranged an alternate aircraft to operate the Bengaluru-Chennai service and provided assistance to affected passengers. The DGCA confirmed that the aircraft, an Airbus A321neo (VT-IME), has been grounded for inspection and rectification. According to the regulator, smoke was reported shortly after pushback when the aircraft began taxiing, with observations indicating smoke presence in both the cockpit and cabin. A detailed investigation has been initiated to determine the root cause. Authorities are examining possible technical issues, including: Electrical system malfunction Air-conditioning or auxiliary system failure Potential wiring or equipment overheating Passengers described a sudden and alarming situation as smoke filled parts of the aircraft during taxiing. One passenger saidI that smoke appeared shortly after the flight began moving, causing immediate panic among those onboard. Another passenger described “dense smoke” and a strong smell inside the cabin, adding that elderly passengers and children faced difficulties during the evacuation process. Eyewitness accounts also noted that passengers rushed toward exits as crew members guided them through emergency procedures. The exact cause of the smoke remains under investigation, with DGCA expected to release preliminary findings after a detailed technical inspection of the aircraft systems.

Incidents

230 Passengers Evacuated At Bengaluru Airport After Smoke Detected On IndiGo Flight

Aviation Today News Desk / May 27, 2026

Bangalore; India: A major aviation scare unfolded at Kempegowda International Airport on Tuesday evening after smoke was detected inside an

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

Chennai, India: An Etihad Airways flight operating from Chennai to Abu Dhabi was delayed on Tuesday after a technical issue forced the aircraft to return to the gate before departure, prompting emergency response protocols at Chennai International Airport. The incident involved Etihad Airways flight EY343, an Airbus A320, carrying around 280 passengers. Initial reports from local media and airport sources suggested that smoke or fire had been observed near the aircraft’s left wing during take-off preparations. However, the airline later issued a clarification denying that any fire had occurred onboard the aircraft. Engineers detected a hydraulic leak during pre-departure checks while the aircraft was preparing for take-off from Chennai. Following the detection of the issue, the aircraft was declared “Aircraft on Ground” (AOG), indicating that it was temporarily unfit for operations pending inspection and maintenance. Passengers were safely disembarked after the aircraft returned to the stand, and the aircraft was later towed back to the parking bay for technical inspection. No injuries were reported. Fire and rescue services were deployed as a precautionary measure in accordance with airport safety procedures. In its official clarification, Etihad Airways said,“contrary to some media reports, there was no fire onboard the aircraft. The aircraft returned to stand due to a technical issue.” The airline further stated,“emergency services were activated as a precautionary measure, based on the Chennai International Airport (MAA) safety protocols.” Etihad confirmed that flight EY343 returned to the gate prior to departure and passengers were subsequently disembarked safely. The carrier added that the flight was expected to depart approximately three hours behind schedule while technical teams carried out necessary checks. The airline also apologised for the disruption and said its teams were assisting passengers with onward travel arrangements and flight updates.

Incidents

Etihad Flight EY343 Aborts Departure At Chennai Airport After Hydraulic System Issue

Aviation Today News Desk / May 13, 2026

Chennai, India: An Etihad Airways flight operating from Chennai to Abu Dhabi was delayed on Tuesday after a technical issue

Denver, United States: A Frontier Airlines Airbus A321neo struck and killed a trespasser while departing Denver International Airport late on May 8, triggering an aborted takeoff, an engine fire, smoke inside the cabin, and an emergency evacuation that left 12 people with minor injuries, according to airport authorities, Frontier Airlines, the FAA and the NTSB. The aircraft, operating as Frontier Airlines Flight 4345 from Denver International Airport to Los Angeles International Airport, was carrying 224 passengers and seven crew members when the incident occurred at approximately 11:19 p.m. local time on Runway 17L. Officials said the unidentified individual breached the airport perimeter fence and entered the active runway area shortly before the collision. Denver International Airport confirmed the person was not believed to be an airport employee. Authorities stated the trespasser was struck by the aircraft during the takeoff roll and was pronounced dead at the scene. Frontier Airlines said the pilots immediately rejected the takeoff after reporting that the aircraft had struck a person on the runway. The impact resulted in a brief engine fire and smoke entering the cabin, prompting an emergency evacuation using inflatable slides. Official figures released by Frontier Airlines and cited by the NTSB confirmed that 12 occupants sustained minor injuries during the evacuation. Five people were transported to local hospitals for treatment, while the remaining injured passengers were treated at the airport. No fatalities or serious injuries were reported among passengers or crew. “We are gathering information about the emergency evacuation to determine if it meets criteria for a safety investigation,” NTSB spokesperson Sarah Taylor Sulick said early Sunday, adding that the agency might have more details in a few hours. A spokesman for the Denver Police Department said Sunday the investigation into the incident was ongoing and that the identity of the person on the runway will be confirmed and released by the Denver Office of the Medical Examiner. The CEO of the Denver airport, Phil Washington, said he knows there are questions still to be answered. “As this is an active investigation with numerous other agencies involved, it is going to take some time as we are still confirming what information we can share at this time,” Washington said in a statement. “This was a horrible and preventable tragedy that has affected many due to the actions of one person who apparently trespassed at an airport and lost their life as a result.” Flight tracking data reviewed by Flightradar24 showed the Airbus A321neo accelerated to approximately 127 knots before braking heavily and stopping on the runway. Emergency crews responded immediately and extinguished the engine fire. Passengers were later transported back to the terminal by bus, and Frontier arranged an alternate flight for most travelers. The affected runway remained closed for several hours before reopening Saturday morning. Federal authorities have launched multiple investigations into both the runway incursion and the emergency evacuation process. The National Transportation Safety Board said it is gathering information regarding the evacuation procedures, while the Federal Aviation Administration, local law enforcement and airport security officials are also examining how the individual gained access to the restricted airside area. U.S. Transportation Secretary Sean Duffy described the incident as a serious security breach and stressed that unauthorized access to airport movement areas poses extreme danger to both aircraft operations and public safety.

Incidents

Frontier Flight Kills Trespasser During Denver Takeoff, 12 Hurt In Evacuation

Aviation Today News Desk / May 11, 2026

Denver, United States: A Frontier Airlines Airbus A321neo struck and killed a trespasser while departing Denver International Airport late on

airport emergency

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

Southwest Flight 1243 Lands Safely At Chicago After Nose Gear Tires Lose Pressure

Air Canada Jet Veers Off Taxiway After Landing At Montreal Airport, Disrupting Flights

Delta Flight Bound For Los Angeles Diverts To Fresno After Engine Warning Mid-Flight

Delta Lands Safely At JFK After Tire Damage Report Triggers Major Emergency Response

American Eagle Flight Diverts To Syracuse After Cockpit Fumes Reported

230 Passengers Evacuated At Bengaluru Airport After Smoke Detected On IndiGo Flight

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

Etihad Flight EY343 Aborts Departure At Chennai Airport After Hydraulic System Issue

Frontier Flight Kills Trespasser During Denver Takeoff, 12 Hurt In Evacuation

Quick Links

Navigate

General Support

News Desk Support