Flight Details
Aircraft Type: Boeing 737-932ER Operator: Delta Air Lines Registration: N892DN Flight Number: DL937 Route: Tucson International Airport (TUS), Arizona to Hartsfield-Jackson Atlanta International Airport (ATL), Georgia Date of Incident: 14 April 2025 Total Occupants: Not officially released; typical 737-900 configuration approximately 180–200 passengers, plus 6 crew Weather Conditions: Visual meteorological conditions, calm surface winds, no convective activity reported
Introduction
On 14 April 2025, a Delta Air Lines Boeing 737-900 operating as flight DL937 returned to Tucson International Airport after experiencing a malfunction in its left-hand engine during the initial climb phase. The aircraft was climbing through approximately 16,000 feet when the flight crew decided to halt the ascent and request a return. The aircraft landed safely on runway 29R approximately 40 minutes after departure. No injuries were reported. The Federal Aviation Administration has confirmed the event and initiated a safety investigation.
Sequence of Events
Delta flight DL937 departed Tucson’s runway 11L bound for Atlanta in early afternoon hours local time. Weather conditions were favourable, and the initial climb appeared routine until the crew stopped the ascent at 16,000 feet citing issues with the aircraft’s number one (left) engine, a CFM56-7B26.
Air traffic control received the request for an immediate return, and vectors were provided for a straight-in approach to runway 29R, the opposite-direction parallel runway at Tucson. The aircraft remained stable throughout the return phase and did not declare an emergency or transmit a 7700 squawk.
Landing was carried out without further incident. Ground observers noted no visible smoke or fire from the aircraft, and emergency services were not required to intervene. The aircraft vacated the runway and was directed to a remote stand for technical inspection.
The total flight time from takeoff to landing was approximately 40 minutes.
Crew & Communication
The cockpit crew did not declare a Mayday or Pan-Pan, suggesting that while the engine malfunction was serious, it was not immediately critical. Communications with ATC were consistent with standard engine issue protocol, and the handling of the event was procedural and controlled.
No radio transmissions suggested engine fire or vibration; rather, the crew maintained measured dialogue with ATC, indicating checklists were being completed during the return leg. The cabin crew would have been briefed promptly, with passengers likely informed mid-flight of the decision to return.
Flight crew identity and background have not been disclosed by Delta, but initial review indicates standard operating procedures were followed in managing the failure and ensuring a safe return.
Aircraft Systems & Technical Analysis
The aircraft involved was a Boeing 737-900ER, registered N892DN, powered by two CFM56-7B26E engines. The left-hand engine was identified as the source of the malfunction during the climb. The airline described the fault as a “mechanical issue” and has not elaborated on the exact nature of the failure.
Given the absence of fire or emergency squawk, possible scenarios include an oil pressure anomaly, a low-pressure compressor stall, N1/N2 mismatch, or abnormal vibration prompting the crew to take pre-emptive action.
The CFM56 engine type is known for its reliability but has a zero-tolerance failure policy, meaning any abnormal parameters typically result in an immediate maintenance action. The aircraft was grounded at Tucson for over 19 hours following the incident, confirming that the issue was sufficiently serious to warrant a full technical assessment.
Maintenance technicians likely initiated engine borescope inspection, diagnostic plug reading, oil sample analysis, and vibration trend monitoring. If component degradation or exceedance is confirmed, the engine could require replacement or depot-level overhaul.
Passenger Experience & Cabin Conditions
No disruption or injuries were reported among passengers. It is not known whether the passengers noticed any mechanical symptoms such as unusual noise, vibration, or asymmetrical thrust, though these would be minimal if the issue was caught early in engine monitoring systems.
Cabin crew would have secured the cabin in anticipation of a precautionary return and updated passengers accordingly. No emergency landing procedures were enacted, and passengers deplaned under normal conditions.
It is not known whether Delta rebooked passengers on an alternate service later that day or provided accommodation in Tucson for onward travel.
Emergency Response & Aftermath
There was no activation of Tucson Airport’s full-scale emergency plan. Local aircraft rescue and firefighting (ARFF) units would have been placed on standby but did not engage the aircraft post-landing.
Runway operations at Tucson remained unaffected, and normal airfield traffic resumed shortly after the aircraft cleared the runway.
Delta’s operations team coordinated with local ground handlers and engineering crews to isolate and assess the failed engine. The aircraft was parked at a maintenance position for inspection and remained out of service for at least 19 hours following the incident.
Investigation Status
The Federal Aviation Administration confirmed the occurrence and issued a standard incident notification stating that the crew reported an “engine issue” and that the FAA will investigate. This aligns with Part 830 reporting criteria, under which a return to the airport for mechanical reasons during climb is considered a reportable event.
Delta Air Lines has not released a formal incident report but confirmed that a mechanical problem with the left engine prompted the return. The airline’s internal Flight Safety division, in coordination with Delta TechOps, will submit a detailed technical report to the FAA within the regulatory timeframe.
Initial results of the inspection will determine whether a Service Difficulty Report (SDR) is filed, and whether any airworthiness directives or fleet-wide communications are required.
Root Cause & Contributing Factors
The root cause remains undetermined pending engine teardown and technical analysis. However, the early detection of abnormal performance in the climb phase suggests the aircraft’s engine monitoring systems and crew vigilance played a key role in risk mitigation.
Contributing factors under review will include recent maintenance activity on the number one engine, oil pressure and temperature trends, vibration logs, and any deferred defects recorded prior to departure.
Environmental or bird-related ingestion is not suspected in this case, and there are no reports of weather-induced engine stress or external object damage.
Safety Recommendations & Industry Impact
While the event is unlikely to trigger regulatory change, it underscores the importance of continuous engine health monitoring and the responsiveness of airline crews during the climb phase — a time of high engine workload and power settings.
Delta is expected to reinforce internal engine reliability tracking, possibly increasing scrutiny of CFM56-7B fleet performance for any related symptoms.
Operators industry-wide are reminded of the importance of early intervention during abnormal engine indications, even when not immediately critical, to preserve safety margins and avoid potential escalation.
Conclusion
The return of Delta flight DL937 to Tucson following a left engine malfunction is a textbook case of risk management and procedural flight crew response. The incident was handled professionally, and the aircraft landed safely without injury or structural damage.
The engine’s performance will be evaluated to determine the exact mechanical failure and guide any necessary maintenance adjustments. Until then, the aircraft remains out of service and under investigation.
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.
