Airbus A321neo Archives - Aviation Today

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.

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

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

Airbus

IndiGo Becomes World’s First Airline To Take Delivery Of 500 Airbus Aircraft

Aviation Today News Desk / April 13, 2026

Gurugram, India: India’s largest airline, IndiGo, has become the first airline globally to receive 500 Airbus aircraft directly from Airbus,

Incidents

Singapore Airlines Plane Clips Spirit Aircraft During Taxi At Newark, No Injuries

Aviation Today News Desk / March 5, 2026

New Jersey, United States: A Singapore Airlines aircraft clipped the tail of a Spirit Airlines jet while maneuvering on the

Kaohsiung, Taiwan: Cathay Pacific Airways flight CX449, bound for Hong Kong from Kaohsiung International Airport in Taiwan, was forced to return to its departure airport on Sunday morning after an engine system alert indicated a possible technical issue, airline and aviation sources confirmed. The Airbus A321neo, scheduled to depart at 7:45 am local time with about 200 passengers on board, took off as planned but turned back shortly after take-off when cockpit instruments showed an abnormal reading related to one of the engines. The aircraft landed safely back in Kaohsiung at around 8:26 am to 8:49 am under standard safety procedures, according to reports. Preliminary inspections by technical teams at Kaohsiung indicated that a lubricant (engine oil) leak in one engine likely caused the pressure anomaly and triggered the warning that prompted the turn-back. Maintenance crews estimated around two hours would be needed to clear any spilled oil and carry out targeted system checks before deciding on the aircraft’s next steps. Cathay Pacific described the incident only as a “technical issue” in its official comment, without confirming specific engine fault details in its public statement, while emphasising that safety considerations guided the decision to return. Taiwanese media reports also referenced the engine oil leak as the apparent cause. All passengers disembarked normally after the aircraft returned to Kaohsiung. Cathay Pacific ground staff assisted travellers by rebooking them onto alternative flights to Hong Kong later the same day. Ground teams reportedly provided meal vouchers and refreshments and worked to restore schedule stability by deploying aircraft with higher seating capacity where possible. The airline also issued an apology to affected customers and thanked them for their patience while disruptions were managed. The A321neo involved in the flight has been grounded at Kaohsiung while further detailed inspections and any necessary engineering work are carried out. Safety officials and airline engineers are continuing to examine the affected engine to determine the full technical cause of the pressure and oil leak anomaly. Cathay Pacific said the crew followed standard procedures in responding to the alert, underlining the airline’s commitment to operational safety.

Incidents

Cathay Pacific Flight A321neo Turns Back To Kaohsiung After Suspected Engine Oil Leak

Aviation Today News Desk / February 2, 2026

Kaohsiung, Taiwan: Cathay Pacific Airways flight CX449, bound for Hong Kong from Kaohsiung International Airport in Taiwan, was forced to

Florida, United States: JetBlue Airways flight B61058, operating from Oranjestad, Aruba (AUA) to New York’s John F. Kennedy International Airport (JFK), was forced to divert and make an emergency landing at Fort Lauderdale-Hollywood International Airport (FLL) on Sunday, January 18, 2026, after suffering an engine failure shortly after takeoff, airline and flight tracking sources confirmed. The aircraft, an Airbus A321neo registered N2086J, departed Aruba’s Queen Beatrix International Airport at approximately 1:59 PM Atlantic Standard Time (AST). Shortly after leaving the runway, pilots reported a “loud bang” and identified a malfunction in the right engine, prompting an immediate emergency declaration using the internationally recognized distress transponder code 7700, according to aviation reports. Following standard safety protocols, the flight crew elected to maintain a holding pattern near Aruba to burn and, as necessary, dump fuel to reduce weight ahead of landing. Once stabilized and in communication with air traffic control, the decision was made to divert to Fort Lauderdale, a major JetBlue maintenance hub with full emergency response capabilities. The aircraft landed safely at 5:21 PM local time (EST). Emergency response teams were positioned on standby at the airport, though no injuries were reported among the 180 passengers and six crew members aboard. Passengers were subsequently disembarked and provided assistance, with the airline arranging rebooking or alternative flights to New York to minimize disruption to travel plans. In the aftermath of the diversion, the aircraft was moved to a secure area of FLL where JetBlue’s technical personnel, supported by federal and aviation authorities, began a detailed inspection to determine the exact cause of the engine failure. The investigation will assess whether the issue stemmed from a mechanical fault within the engine, a related component malfunction, or other technical factors. JetBlue has placed the aircraft out of service pending completion of this assessment. It is standard practice in such incidents for airlines to work with regulatory and manufacturer stakeholders to analyze flight data, conduct engine examinations, and ensure that corrective actions or maintenance directives are implemented as needed.

Incidents

JetBlue Flight Makes Emergency Landing In Florida After Mid-Air Engine Failure

Aviation Today News Desk / January 22, 2026

Florida, United States: JetBlue Airways flight B61058, operating from Oranjestad, Aruba (AUA) to New York’s John F. Kennedy International Airport

Orlando, United States: A United Airlines flight traveling from Chicago’s O’Hare International Airport to Orlando International Airport experienced a significant mechanical issue upon landing on Sunday afternoon, resulting in one of the aircraft’s nose wheels detaching and temporarily blocking the runway, authorities confirmed. United Airlines Flight UA2323, operated with an Airbus A321neo registered N14502, departed Chicago at approximately 8:55 a.m. CST and was scheduled to arrive at Orlando International Airport (MCO) at 12:35 p.m. EST. Shortly after touchdown on Sunday, January 18, video footage shared on social media captured the aircraft making contact with the runway under what appeared to be challenging weather conditions. During the landing sequence, one of the forward nose wheels detached from the aircraft and rolled off the runway surface. Eyewitness video shows the aircraft’s main wheels touching down, followed by a series of uneven bounces. The aircraft veered slightly, and the separated wheel can be seen rolling away from the plane. The aircraft ultimately came to a stop on the runway. United Airlines reported that there were 200 passengers and six crew members on board at the time of the incident. Despite the severity of the landing and the mechanical failure, no injuries were reported. Passengers were safely disembarked and transported to the terminal via buses after being unable to reach the gate normally. Immediately following the incident, the Federal Aviation Administration (FAA) and airport authorities issued a ground stop at MCO, temporarily halting all departing and arriving flights to allow emergency crews to secure the scene and clear debris. The ground stop was later adjusted to a ground delay as operations gradually resumed later in the afternoon. Orlando International Airport is one of the busiest travel hubs in Florida, and the runway closure led to delays and logistical disruptions across scheduled flights during peak travel hours. Preliminary accounts noted gusty and windy conditions at the time of landing, with reported wind gusts above typical operational norms. While weather may have contributed to the severity of the landing, authorities have not confirmed whether it was a causal factor in the mechanical failure. United Airlines and the FAA have not yet released detailed technical findings, but the aircraft has been removed from service and is undergoing maintenance inspection. Investigators are reviewing whether the failure was due to the hard landing dynamics, mechanical fatigue, weather stress, or a combination of factors. Federal aviation safety teams are continuing their examination of the incident. Official reports from the FAA or the National Transportation Safety Board (NTSB) are expected in the coming days to clarify the precise mechanical cause and any contributing conditions. Final findings will inform whether industry safety procedures or maintenance protocols require updates.

Incidents

United Airlines Flight Loses Nose Wheel On Landing At Orlando, No Injuries Reported

Aviation Today News Desk / January 19, 2026

Orlando, United States: A United Airlines flight traveling from Chicago’s O’Hare International Airport to Orlando International Airport experienced a significant

Florida, United States: A Delta Air Lines flight from Orlando to Los Angeles made an emergency diversion to Tampa International Airport on Saturday, December 27, 2025, after the cabin crew detected an unusual odor onboard, airline officials confirmed. Delta Flight DL504, operated with an Airbus A321neo (registration N503DZ), departed Orlando International Airport (MCO) bound for Los Angeles International Airport (LAX) when the crew identified the scent mid‑flight and elected to divert the aircraft as a precautionary safety measure. The aircraft touched down at Tampa International Airport at approximately 11:30 a.m. local time, with 194 passengers and six crew members onboard. No injuries were reported during the landing or among those who disembarked. Delta officials stated that passengers were re‑accommodated on a different aircraft that later continued to Los Angeles. “At Delta, the safety of our customers and crew comes before anything else, and we appreciate our customers’ patience,” the airline said in a written statement. At the time of reporting, the airline had not disclosed the cause or specific nature of the odor detected onboard. Aviation safety databases indicate that the flight was en route over Florida when the issue emerged and the diversion was initiated out of an abundance of caution

Incidents

Delta Flight DL504 Diverts To Tampa After Cabin Crew Detects Unusual Odor Onboard

Aviation Today News Desk / December 31, 2025

Florida, United States: A Delta Air Lines flight from Orlando to Los Angeles made an emergency diversion to Tampa International

Muscat, Oman: A Turkish Airlines flight from Istanbul to Muscat International Airport (MCT) became the centre of an unusual aviation exchange on Sunday when the aircraft’s flight crew and Muscat air traffic control (ATC) disagreed over a descent clearance during the approach phase. The Airbus A321neo was being vectored for an Instrument Landing System (ILS) approach when Muscat ATC instructed the crew to descend to 2,200 feet, identified by controllers as a minimum safe altitude suitable for sequencing and terrain clearance in that segment of airspace. The pilot responded that the airline’s company-approved navigation charts did not list 2,200 feet as an acceptable minimum altitude in that sector and that his flight crew could only descend to 3,600 feet in accordance with their procedures and published minimum vectoring altitudes (MVAs). In recorded ATC transmissions that have circulated within aviation safety analysis communities, the exchange became tense as the pilot repeatedly stated he was “unable to accept vectors” below the charted limit. The controller, while asserting that “our minimum safe altitude is 2,200,” urged the flight crew to comply with ATC instructions. Despite the firm tone in radio exchanges, both sides maintained professional conduct, and the disagreement did not escalate into an unsafe operational situation. The pilot proposed alternative vectors that would allow the aircraft to remain at or above 3,600 feet while aligning for the approach sequence. Minimum vectoring altitude and minimum safe altitude figures are critical safety parameters that provide required terrain and obstacle clearance during radar vectoring. Air traffic controllers and pilots derive these altitudes from different sources controllers from their local surveillance and obstacle databases, and pilots from company-approved charts often supplied by third-party aeronautical data providers. International aviation regulations and standard operating procedures emphasise that the pilot in command retains ultimate responsibility for the safety of the aircraft. When an ATC-issued clearance conflicts with a pilot’s verified safety limits, the flight crew may lawfully decline and request clarification or alternative instructions. The Turkish Airlines aircraft remained at or above the altitude the crew could accept until it was safely established on the final approach. There were no reported safety incidents, and the flight landed without further operational disruption.

Incidents

Turkish Airlines Pilot Disputes Descent Clearance With Muscat ATC, Flight Lands Safely

Aviation Today News Desk / December 29, 2025

Muscat, Oman: A Turkish Airlines flight from Istanbul to Muscat International Airport (MCT) became the centre of an unusual aviation

Hanoi, Vietnam: Vietnam’s civil aviation sector has grounded 28 commercial aircraft as part of a broader global engine shortage that continues to disrupt airline fleet operations and maintenance timelines, industry sources and official data confirm. According to figures released by the Civil Aviation Authority of Vietnam (CAAV) and industry reporting, the affected aircraft represent approximately 13.1 per cent of Vietnam’s operational commercial fleet, underscoring the depth of the ongoing supply chain challenge. The grounding stems from an extended recall and repair cycle for Pratt & Whitney’s PW1000G geared turbofan engines, which power a large portion of narrow‑body jets such as the Airbus A321neo. These engines have been subject to global maintenance and availability constraints, affecting multiple airlines worldwide. Of the aircraft currently out of service in Vietnam: 24 are Airbus A321neo aircraft Three are Airbus A350s One is an Airbus A320ceo Despite reduced fleet availability, carriers based in Vietnam have maintained core route operations, both domestically and internationally. Hanoi (HAN) and Ho Chi Minh City (SGN) continue to serve as major aviation hubs, linking close to 50 domestic routes across 20 airports. On the international front, Vietnamese airlines operate over 110 scheduled routes to more than two dozen countries, while foreign carriers maintain robust connections with Vietnam through over 140 services. Strong travel demand has bolstered resilience across the sector. Preliminary data estimates that international passenger numbers will reach around 46.9 million in 2025, marking roughly a 13.3 per cent increase compared with the previous year. Domestic passenger traffic also rose, with nearly 36.6 million travellers, reflecting sustained demand across segments. Total passenger traffic is seen growing by upwards of 6.7 per cent, while cargo volumes have climbed by 4.6 per cent over the same period. Vietnam’s aviation regulator and airline operators have initiated strategies to mitigate the impact of grounded aircraft, including fleet reallocation, schedule adjustments, and prioritising high‑demand routes. The CAAV has signalled that while the number of grounded jets has eased compared with earlier reports in 2025, supply chain recovery challenges persist. Looking ahead, Vietnam’s air transport sector is pursuing ambitious growth targets for 2026, aiming to accommodate up to 95 million passengers alongside expanded cargo operations, signalling confidence in long‑term traffic growth despite underlying technical challenges

Airlines

Vietnam Grounds 28 Aircraft Amid Global Engine Shortages, Operations Disrupted

Aviation Today News Desk / December 18, 2025

Hanoi, Vietnam: Vietnam’s civil aviation sector has grounded 28 commercial aircraft as part of a broader global engine shortage that

Airbus A321neo

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

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

Singapore Airlines Plane Clips Spirit Aircraft During Taxi At Newark, No Injuries

Cathay Pacific Flight A321neo Turns Back To Kaohsiung After Suspected Engine Oil Leak

JetBlue Flight Makes Emergency Landing In Florida After Mid-Air Engine Failure

United Airlines Flight Loses Nose Wheel On Landing At Orlando, No Injuries Reported

Delta Flight DL504 Diverts To Tampa After Cabin Crew Detects Unusual Odor Onboard

Turkish Airlines Pilot Disputes Descent Clearance With Muscat ATC, Flight Lands Safely

Vietnam Grounds 28 Aircraft Amid Global Engine Shortages, Operations Disrupted

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us