Date: 4th December 2024
Location: Phoenix Sky Harbor International Airport, Arizona, USA
Aircraft: Boeing 737-800, registration N965NN
Operator: American Airlines
Flight Number: AA-1037
Route: Phoenix, AZ (USA) to Reno, NV (USA)
Occupants: Unknown
Injuries: None reported
Summary of Events
On 4th December 2024, American Airlines flight AA-1037, a Boeing 737-800 operating from Phoenix to Reno, experienced a tyre separation during departure from runway 25R at Phoenix Sky Harbor International Airport. Shortly after takeoff, a ground observer reported seeing a tyre separate from the aircraft. A subsequent runway inspection confirmed tyre debris. The crew was informed of the issue, stopped their climb at FL240, and decided to return to Phoenix for a safe landing on runway 26 approximately 35 minutes after departure.
Aircraft Information
The Boeing 737-800 is a narrow-body, twin-engine jetliner widely used for short- to medium-haul operations. It is equipped with a dual-wheeled main landing gear system designed to manage significant loads during takeoff and landing. Tyre failures or separations can pose risks to aircraft systems and operations.
Sequence of Events
1. Takeoff Roll:
• The aircraft departed Phoenix’s runway 25R on a routine climb to Reno.
2. Runway Inspection:
• Tower personnel queried other departures about possible foreign objects (FOD) on the runway, receiving negative responses.
• A runway inspection revealed tyre debris, prompting immediate notification of the crew.
3. Crew Awareness:
• Ground observers reported witnessing a tyre separation during the aircraft’s departure.
• The crew acknowledged the report and decided to level off at FL240 to assess the situation.
4. Return to Phoenix:
• After evaluating the potential risk, the crew chose to return to Phoenix for a precautionary landing.
• The aircraft landed safely on runway 26 approximately 35 minutes after departure.
Initial Findings
Tyre Separation
• The debris found on the runway confirmed a tyre separation occurred during the departure roll.
• Possible contributing factors include:
• Tyre Overstress: Excessive loading during takeoff, possibly linked to operational factors.
• Undetected Damage: Prior wear, cuts, or punctures not identified during pre-flight inspections.
Aircraft Systems and Performance
• There were no reports of systems failure or additional damage resulting from the tyre separation.
• The crew effectively managed the situation and executed a safe return to the airport.
Safety Risks
1. Debris Hazards:
• Detached tyre fragments pose a risk to other aircraft during departure or landing and can damage airport infrastructure.
2. Landing Gear Damage:
• Tyre separation can lead to structural damage to the landing gear or surrounding components.
3. Operational Risk:
• The event required an unplanned return, increasing the operational complexity and workload for the flight crew and air traffic control.
Recommendations
1. Tyre Inspection and Maintenance:
• Enhance routine pre-flight inspections to identify and address signs of tyre wear or potential failure points.
2. Runway Surveillance:
• Implement advanced FOD detection systems to minimise risks posed by debris on runways.
3. Training and Response Protocols:
• Ensure crews are trained to handle tyre failure scenarios, including post-takeoff assessments and safe return procedures.
4. Incident Analysis:
• Conduct a thorough investigation to determine the root cause of the tyre separation, focusing on maintenance records and operational factors.
Safety Lessons
This incident highlights the importance of robust landing gear maintenance and monitoring systems to detect potential issues before they escalate into in-flight complications. The crew’s decision-making and coordination with air traffic control ensured the safe return of the aircraft, demonstrating the value of effective communication and standard operating procedures.
Disclaimer
If you are the rightful owner of the photo and wish it to be taken down, please email takedown@cockpitking.com.
Our investigation reports are based on all the evidence and facts available at the time of writing and posting. We apologise if any details are missed or are not fully accurate.
