Flight DL-333 | Registration: N534DT
Date: 3 April 2025 | Location: Las Vegas Harry Reid International Airport (KLAS), USA
Flight Details
Aircraft Type: Airbus A321-271N (A321neo) Engines: 2 × Pratt & Whitney PW1133G-JM Operator: Delta Air Lines Registration: N534DT Flight Number: DL-333 Callsign: DAL333 Route: Las Vegas, Nevada (KLAS) to New York John F. Kennedy (KJFK), New York Date of Incident: 3 April 2025 Total Occupants: Estimated 200 (passengers and crew) Weather Conditions: Visual Meteorological Conditions at departure
Introduction
On 3 April 2025, Delta Air Lines flight DL-333 was forced to return to Las Vegas shortly after departure following an engine issue involving a suspected compressor stall on the left-hand Pratt & Whitney PW1133G engine. The aircraft, an Airbus A321neo registered N534DT, had just departed from runway 01R and was climbing through 9,000 feet when the crew reported the malfunction and initiated a return. The aircraft landed safely on runway 26L approximately 30 minutes after take-off.
Passenger accounts described a loud bang and visible flame from the left engine. Although no fire was detected upon landing, the incident was handled as a precautionary return. Emergency services met the aircraft and conducted a post-landing inspection. The flight was cancelled, and passengers were rebooked. The aircraft returned to service three days later after necessary repairs and inspections.
Sequence of Events
The aircraft departed Las Vegas at approximately 08:10 local time, climbing normally through initial altitudes. Upon contacting departure control, the flight crew reported an issue with the left-hand engine, subsequently identified as a compressor stall.
Compressor stalls are characterised by:
Abnormal noise (bang or pop) Temporary loss of thrust Visible flame or smoke from the exhaust Airframe vibration or yaw
Several passengers near the left wing observed a brief burst of flame and heard a loud bang, consistent with a stall event. The flight crew immediately levelled off at 9,000 feet, declared a return to field (RTF), and coordinated vectors for an approach to runway 26L.
The aircraft landed without further incident and vacated the runway. Fire and emergency crews inspected the engine upon arrival and reported no visible fire or oil leak. The aircraft taxied to the gate under its own power.
Crew & Communication
The flight crew acted in accordance with Airbus and airline procedures for engine performance anomalies and compressor stall events. Standard cockpit response would have included:
Thrust reduction on the affected engine Engine monitoring via ECAM and EGT parameters Decision-making via QRH checklist for engine malfunction in climb Communication with ATC for priority handling and return clearance
The crew’s decision to return as a precaution despite no apparent ongoing issue aligns with best practice, especially given the nature of long-haul transcontinental operations over remote terrain.
The cabin crew maintained control, and no emergency evacuation was initiated. Passengers remained onboard until normal disembarkation.
Aircraft Systems & Technical Analysis
The Pratt & Whitney PW1100G family has had a history of early in-service issues, particularly involving:
Compressor stalls and surges Fan blade degradation Bearing compartment oil leaks
In this case, the suspected compressor stall did not cause visible damage but warranted a full inspection, which likely included:
Borescope inspection of LP and HP compressor stages Engine vibration analysis via ACMS data Verification of oil pressure and temperature stability Assessment of FADEC fault messages
The fact that the aircraft was returned to service after three days suggests that the stall was transient or resulted in minor component degradation, not requiring engine replacement.
Passenger Experience & Cabin Conditions
Passengers reported startling sounds and flames visible from the window seats near the left engine. Despite the dramatic symptoms, the crew remained composed and provided announcements regarding the precautionary return.
There were no injuries, no smoke or pressurisation issues, and no emergency procedures executed in the cabin. Passengers were re-accommodated on later flights to New York.
Emergency Response & Aftermath
Upon landing, the aircraft was met by fire and rescue units as standard protocol for an in-flight engine anomaly. Visual inspection found no active fire, leaks, or external damage.
The aircraft was towed to a remote stand where Delta maintenance personnel conducted further diagnostics. The flight was cancelled, and passengers were rebooked.
Delta’s operations team arranged a fleet swap or reallocation to manage the impact of the grounded aircraft. N534DT remained out of service for three days, indicating minor damage or system resets were sufficient.
Investigation Status
The incident was not classified as an accident or serious incident requiring formal investigation by the NTSB. However, Delta and Pratt & Whitney engineers likely conducted an internal review, particularly given the engine type’s previous service bulletins (SBs) related to stall margins and component wear.
Root Cause & Contributing Factors
Probable Cause:
Suspected compressor stall in the left PW1133G engine during climb, resulting in loss of thrust and return to departure airport.
Contributing Factors:
Possible hot section temperature instability Sudden throttle input or altitude transition during climb Early signs of compressor blade wear or imbalance
Although no permanent engine damage was reported, transient anomalies in the PW1100G powerplant remain an area of industry focus.
Safety Recommendations & Industry Impact
This incident highlights the need for:
Continued monitoring of PW1100G series engines, particularly for compressor performance issues Flight crew training for engine stall recognition and ECAM/QRH response Improved data logging and engine health monitoring, especially post-stall events Predictive maintenance programmes using vibration trend analysis
No regulatory action has been taken, but Delta and other operators may review compressor stall recovery procedures and engine trend monitoring strategies.
Conclusion
Delta flight DL-333 illustrates the complexity of managing engine anomalies in new-generation aircraft. The crew’s prompt response and adherence to protocol ensured passenger safety, while technical analysis confirmed that modern engine systems, even when showing signs of failure, can be safely managed with rigorous processes in place.
This event serves as a reminder that while next-gen engines offer fuel efficiency and noise reduction, their tight tolerances and advanced systems demand meticulous oversight and rapid decision-making in flight.
Disclaimer
This article is based on publicly available information and reports at the time of writing. While every effort has been made to ensure accuracy, we cannot guarantee the completeness of the information provided.
If you are the rightful owner of any referenced content or images and wish them to be removed, please contact takedown@cockpitking.com.
