‘Extended Taxi’ Blamed for 737 Brake Fire

The Boeing 737 MAX 9 – registered as N37560 – experienced a rejected takeoff and subsequent brake fire, resulting in substantial damage.

United 737 MAX 9
A United 737 MAX 9 aircraft (Photo: AirlineGeeks | William Derrickson)
Gemini Sparkle

Key Takeaways:

The National Transportation Safety Board has released its final report on an incident involving United flight 329 at Denver International Airport on Sept. 30, 2023. The Boeing 737 MAX 9 – registered as N37560 – experienced a rejected takeoff and subsequent brake fire, resulting in substantial damage but no injuries to the 173 people on board.

The NTSB’s investigation revealed that the probable cause was overheated brakes due to a so-called “extended taxi” at higher power settings. This was an attempt by the flight crew to burn off excess fuel to achieve the proper takeoff weight.

According to the report, the flight crew noticed before departure that the aircraft was over the maximum allowed takeoff weight for the runway conditions at the time. After multiple flight plan revisions from dispatch, including removing cargo and passengers, the crew opted to burn off about 1,000 pounds of extra fuel during an extended taxi.

The captain reported noticing abnormal acceleration during the takeoff roll, leading to an immediate rejection of the takeoff. The tower then observed and reported smoke and fire on the right side of the aircraft.

Substantial Damage

An inspection later found significant damage to the aircraft’s tires, wheel assemblies, and other components. The Nos. 1 and 2 tires had deflated, while the Nos. 3 and 4 tires had separated from their wheel assemblies. Tire fragments had impacted various areas of the airframe, and there was evidence of the right engine nacelle scraping the runway.

The NTSB noted that the Boeing 737 lacks a brake temperature monitoring system, which might have alerted the crew to the overheating issue. The captain mentioned that other Boeing aircraft they had flown were equipped with such systems.

Following the incident, the aircraft remained out of service for approximately two weeks.

Ryan Ewing

Ryan founded AirlineGeeks.com in February 2013 and has spent more than a decade covering the airline business. His work has been featured by CNN, WJLA, CNET, and Business Insider. His aviation experience spans airport operations, Part 135 regulatory compliance, and airline crew workforce planning, along with time behind the yoke of a Cessna 172 and interviews with airline executives. Ryan now serves as Group President of Firecrown Media’s Aviation Group. He holds a B.S. in Air Transportation Management and an MBA from Arizona State University and teaches Airline Management at Embry-Riddle Aeronautical University.
Sign-up for newsletters & special offers!

Get the latest stories & special offers delivered directly to your inbox

SUBSCRIBE

Uh-oh! It looks like you're using an ad blocker.

Our website relies on ads to provide free content and sustain our operations. By turning off your ad blocker, you help support us and ensure we can continue offering valuable content without any cost to you.

We truly appreciate your understanding and support. Thank you for considering disabling your ad blocker for this website