Flight AS-474 | Registration: N967AK
Date: 3 April 2025 | Location: Atlanta Hartsfield-Jackson Intl (ATL), Georgia, USA
Flight Details
• Aircraft Type: Boeing 737-9 MAX (B39M)
• Engines: 2 × CFM LEAP-1B
• Operator: Alaska Airlines
• Registration: N967AK
• Flight Number: AS-474
• Callsign: ASA474
• Route: Atlanta Hartsfield-Jackson Intl (ATL) to San Diego Intl (SAN)
• Date of Incident: 3 April 2025
• Total Occupants: 171 (165 passengers, 6 crew)
• Weather Conditions: Not officially released, typical VMC reported at ATL during morning departures
Introduction
On 3 April 2025, an Alaska Airlines Boeing 737-9 MAX operating as flight AS-474 from Atlanta to San Diego suffered a tyre failure during the take-off roll on runway 26L at Atlanta Hartsfield-Jackson International Airport. The aircraft, registered N967AK, continued its flight and landed safely at San Diego International Airport approximately 4 hours and 30 minutes later. The incident was later classified as an operational incident involving tyre and potential engine damage, prompting FAA reporting and maintenance action post-flight. No injuries were reported among the 171 occupants on board.
Sequence of Events
Flight AS-474 departed from gate at Atlanta Hartsfield-Jackson around the scheduled departure time and taxied to runway 26L for departure. During the take-off roll, a tyre on the right wheel of the left main landing gear failed, shedding debris east of taxiway D as the aircraft accelerated past V1.
The crew did not receive any cockpit warnings or alerts regarding abnormal gear status, and the aircraft rotation, lift-off, and climb-out proceeded uneventfully. ATC did not notify the flight of any visible anomalies during departure.
Once airborne, the aircraft climbed normally to cruise altitude, maintaining FL340 en route to San Diego. No performance degradation or vibration abnormalities were reported during cruise. Cabin crew and passengers remained unaware of any issue during flight.
Approximately 4.5 hours later, the aircraft landed safely on runway 27 at San Diego International Airport. Upon post-flight inspection, ground crews discovered damage to the left engine nacelle consistent with debris impact from the failed tyre. The aircraft was immediately withdrawn from service by Alaska Airlines Maintenance for further assessment.
Crew & Communication
There is no publicly available ATC recording indicating that the crew was notified of the blown tyre during or after take-off. Likewise, the crew did not report any abnormal vibration, warning messages, or performance issues during climb or cruise.
No emergency was declared, and the flight continued under normal operating conditions. CVR and FDR data have not been publicly released, but standard post-incident review procedures are expected to have secured the recordings upon landing in San Diego.
Alaska Airlines has not issued a public crew statement, and communication logs between cockpit and maintenance have not been disclosed.
Aircraft Systems & Technical Analysis
Initial assessments suggest the right tyre of the left main landing gear failed during the take-off roll, resulting in high-velocity debris ejection. The force and trajectory of the dislodged rubber and wheel fragments likely impacted the adjacent left engine nacelle.
No engine ingestion or mechanical faults were detected during flight, suggesting that while impact occurred, the damage was limited to the nacelle structure rather than internal engine components.
The Boeing 737-9 MAX’s CFM LEAP-1B engines are protected by reinforced nacelle structures designed to withstand a range of foreign object damage (FOD), although direct impact from tyre debris at take-off velocity can still pose a significant risk.
There is no indication that the landing gear retraction sequence was affected, and no hydraulic or brake anomalies were reported during descent or landing.
Passenger Experience & Cabin Conditions
No injuries occurred during the flight. Passengers did not report any signs of turbulence, vibration, or unusual noise that might have indicated a tyre failure during departure. Cabin crew were not informed of any technical issue until after arrival in San Diego.
Post-landing, the disembarkation proceeded normally. The aircraft was positioned for maintenance assessment immediately after arrival, and passengers were not subjected to emergency measures or delay beyond the scheduled arrival.
Emergency Response & Aftermath
Following the post-flight inspection, the aircraft was declared unserviceable. The left engine nacelle sustained damage from debris, and the affected main gear assembly was scheduled for inspection and possible component replacement.
The aircraft remained grounded at San Diego International Airport for at least 13 hours after landing, pending detailed structural evaluation.
No runway closures or delays were reported at Atlanta following the incident. The location of tyre debris—east of taxiway D—was confirmed by FAA personnel and removed by ground services with no impact to subsequent airport operations.
Alaska Airlines did not announce any delays or flight cancellations as a result of the incident, suggesting that passengers on subsequent flights were either reaccommodated or delays were minimal.
Investigation Status
The incident was reported by the Federal Aviation Administration (FAA) under its mandatory reporting guidelines. Their official statement included reference to:
• Tyre failure during take-off at ATL runway 26L
• Debris field east of taxiway D
• Post-flight damage identified to the left engine nacelle
• Aircraft removed from service by Alaska Airlines Maintenance
As of the time of writing, there is no indication that the National Transportation Safety Board (NTSB) has opened a separate investigation. However, internal engineering review is ongoing under FAA oversight.
FDR and CVR data are likely to be reviewed to confirm take-off roll dynamics, speed at time of failure, and absence of abnormal engine or airframe behaviour during cruise.
Root Cause & Contributing Factors
Pending further technical analysis, the root cause appears to be a structural failure of the right-side tyre on the left main landing gear during high-speed take-off roll.
Possible contributing factors may include:
• Manufacturing defect or internal delamination of the tyre
• Foreign object impact on the runway
• Excessive tyre wear or underinflation (not yet confirmed)
• Heat buildup during taxi and take-off preparation
Further investigation is required to determine whether maintenance practices, tyre age, or environmental conditions at ATL contributed to the failure. Boeing’s recommended inspection intervals for landing gear tyres and brake systems are likely to be reviewed in the course of the inquiry.
Safety Recommendations & Industry Impact
Although no injuries or severe damage were recorded, this event reinforces the importance of:
• Comprehensive tyre inspections pre-flight
• Adherence to manufacturer’s replacement cycles and pressure checks
• Timely replacement of tyres approaching wear thresholds
Airlines operating the Boeing 737 MAX series may be advised to review main landing gear inspection protocols, especially given the higher loads exerted during take-off on longer variants such as the 737-9 MAX.
In light of this incident, Alaska Airlines is expected to conduct a broader fleet-wide inspection of tyres and wheel assemblies and share findings with Boeing and the FAA to determine if further safety advisories are warranted.
Conclusion
This incident involving Alaska Airlines flight AS-474 demonstrates the latent hazards of tyre failures during high-speed take-off. While the aircraft completed its flight without injury or in-flight complications, the post-landing discovery of engine nacelle damage underlines the potential severity of runway debris impacts, even when the source is part of the aircraft itself.
Preventive maintenance, consistent tyre inspection protocols, and strict adherence to OEM service bulletins remain key in avoiding such occurrences. The outcome, in this case, was favourable—but serves as a cautionary reminder of how quickly minor mechanical issues can escalate if undetected.
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.
