Smoke From Landing Gear Forces Southwest 737 MAX Back to Gate at Harry Reid International

LAS VEGAS, OCTOBER 11, 2026

A Southwest Airlines Boeing 737 MAX 8 bound for Chicago Midway never got off the ground Friday at Harry Reid International Airport. Flight WN759 was taxiing for departure when the crew of another Southwest jet, flight WN334 bound for Houston's William P. Hobby Airport, alerted air traffic control that they could see heavy smoke rising from the right main landing gear of the aircraft ahead. The pilots asked for airport fire trucks, describing what appeared to the pilots following behind to be a possible landing-gear fire, damaged brake components, and a trail of fluid on the taxiway. Emergency crews responded. The departure was aborted before the aircraft ever reached the runway, and the jet was towed back to the terminal.

No injuries were reported. Southwest moved the passengers to a replacement aircraft, which departed Las Vegas at 4:44 p.m. against a scheduled 12:15 p.m. departure and touched down at Chicago Midway at 9:40 p.m. — nearly four hours behind schedule. What exactly went wrong is not yet known. Southwest told KSNV News 3, the NBC affiliate in Las Vegas, that it had received no reports of a fire and was looking at a possible hydraulic issue as a concern. As of the weekend, neither the Federal Aviation Administration nor the National Transportation Safety Board had commented on the incident.

How it unfolded

The account comes from the radio. The WN334 crew, taxiing behind the Midway-bound jet, told controllers what they were seeing: heavy smoke from the right main landing gear of WN759, brake material scattered on the taxiway, a trail of fluid nearby. A widely shared air-traffic-control recording from the incident, timestamped October 9 at 1:01 p.m., captures the tower alerting emergency crews after the "right landing gear on fire" report came in. Airport emergency personnel met the aircraft as it was taken out of departure operations.

From there, the response was textbook. Ground crews towed the MAX 8 back to the terminal rather than risking any further movement. Passengers deplaned and were rebooked onto a replacement aircraft the same day. By 4:44 p.m., they were in the air. The delay was significant — roughly four and a half hours — but in the hierarchy of aviation disruptions, a same-day replacement aircraft with no injuries is about as good an outcome as an incident like this produces.

What we know — and what we don't

This is the part of the story where precision matters, because the gap between "heavy smoke from the landing gear" and "a fire" is real and the airline has drawn it explicitly. Southwest said there were no reports of a fire. It characterized its concern as a possible hydraulic issue. The pilots who reported it used the word fire. Both things can be true at once: from the cockpit of a trailing aircraft, heavy smoke and scattered brake material look like a fire, and controllers treat it as one until it's proven otherwise. That is exactly what the fire trucks were for.

The cause has not been established. Aviation A2Z, which first detailed the taxiway debris and fluid reports, noted the concerns raised questions about damage to the aircraft's braking or hydraulic systems — but questions are not answers, and neither the airline nor any regulator has said what failed. The FAA and NTSB had not commented as of the weekend. Landing-gear smoke during taxi can come from a number of sources — overheated brakes, a dragging brake, leaking hydraulic fluid contacting hot components — and investigators typically won't speculate until the aircraft has been inspected. We won't either.

What is confirmed: the aircraft never reached the runway, no one was hurt, the passengers were re-accommodated the same day, and the airline says it is investigating a possible hydraulic issue. Everything beyond that is pending.

A rough week for Southwest — and a stormy one for Florida flying

The gear-smoke incident landed at the end of a bumpy stretch for Southwest. On Friday, the same day as the Las Vegas incident, the airline was still working through the fallout of an October 9 software outage that knocked out baggage and boarding systems. Texas Public Radio reported the affected software was restored by 12:30 p.m. that day, with more than 1,200 delays and about 40 cancellations across the network. The airline has still not given a detailed cause for that outage.

Meanwhile, across the country, the weekend brought better news for Gulf Coast travelers. Pensacola International Airport and Destin–Fort Walton Beach Airport both reopened over the weekend after closing ahead of Hurricane Isaias — Pensacola had shut down Friday, October 9 at 10 a.m.; Destin–Fort Walton Beach closed Thursday, October 8 at 9 p.m. Pensacola officials said the airport was "back open and operational for regularly scheduled commercial service," while Destin–Fort Walton Beach said it was still restoring critical systems and warned that flight schedules had changed. Neither airport named its first flight back.

The two threads share a theme: an October week in which the margin between a routine flight and a headline was thin, and in which the aviation system's redundancies — replacement aircraft, reopened airports, rebooked passengers — did what they are built to do. For the passengers on WN759, Friday ended four hours late in Chicago. Nobody was hurt. The rest is up to the mechanics and, eventually, the investigators.