News
SpaceX Starship prototype ignites six engines, starts major brush fire
SpaceX has successfully ignited all six engines on its latest Starship prototype, taking a significant step towards ensuring that the upper stage will be ready for the rocket’s first orbital launch attempt.
Unfortunately, the same successful static fire of a Starship upper stage – potentially producing almost twice as much thrust as the booster of SpaceX’s Falcon 9 rocket – scattered superheated debris hundreds of meters away, igniting a major brush fire. It’s not the first major fire caused by Starship activities in South Texas, and it likely won’t be the last.
Starship S24 completed its first successful static fire on August 9th, igniting two Raptor engines. Several unsuccessful attempts to test more engines followed throughout the rest of the month, and SpaceX ultimately decided to replace one of Starship S24’s three Raptor Vacuum engines in early September before trying again. After workers installed the new engine and buttoned up Ship 24, the stars eventually aligned on September 8th.
Kicking off the test, SpaceX pumped several hundred tons of liquid oxygen (LOx) and a much smaller quantity of liquid methane (LCH4) fuel into Ship 24 in about 90 minutes, producing a crisp layer of frost wherever the cryogenic liquids touched the skin of the rocket’s uninsulated steel tanks. No frost formed on Starship’s upper methane tank, implying that SpaceX only loaded methane fuel into internal ‘header’ tanks meant to store propellant for landings. The hundreds of tons of liquid oxygen, then, were likely meant as ballast, reducing the maximum stress Starship could exert on the test stand holding it to the ground.
That potential stress is substantial. Outfitted with upgraded Raptor 2 engines, Starship S24 could have produced up to 1380 tons (~3M lbf) thrust when it ignited all six for the first time at 4:30 pm CDT. On top of smashing the record for most thrust produced during a Starbase rocket test, Ship 24’s engines burned for almost 8 seconds, making it one of the longest static fires ever performed on a Starship test stand.
Several brush fires were visible almost immediately after clouds of dust and steam cleared. More likely than not, the combination of the extreme force, heat, and burn duration likely obliterated the almost entirely unprotected concrete surface below Ship 24. Despite continuous evidence that all Starship static fire operations would be easier and safer with the systems, SpaceX still refuses to install serious water deluge or flame deflector systems at Starbase’s test stands and launch pads.
Instead, under its steel Starship test stands, SpaceX relies on a single middling deluge spray nozzle and high-temperature concrete (likely martyte) that probably wouldn’t pass muster for a rocket ten times less powerful than Starship. In multiple instances, Starships have shattered that feeble martyte layer, creating high-velocity ceramic shards that damage their undersides or Raptor engines, requiring repairs and creating risky situations. With essentially no attempt at all to tame the high-speed several-thousand-degree Raptor exhaust, static fire tests at Starbase thus almost always start small grass fires and cause minor damage, but those fires rarely spread.
Ship 24’s first six-engine test was not so lucky, although the Starship made it through seemingly unscathed. Most likely, eight long seconds of blast-furnace conditions melted the top layer of surrounding concrete and shot a hailstorm of tiny superheated globules in almost every direction. Indeed, in almost every direction there was something readily able to burn, a fire started. In several locations to the south and west, brush caught fire and began to burn unusually aggressively, quickly growing into walls of flames that sped across the terrain. To the east, debris even made it into a SpaceX dumpster, the contents of which easily caught fire and burned for hours.
Eventually, around 9pm CDT, firefighters were able to approach the safed launch pad and rocket, but the main fire had already spread south, out of reach. Instead, they started controlled burns near SpaceX’s roadblock, hoping to clear brush and prevent the fire (however unlikely) from proceeding towards SpaceX’s Starbase factory and Boca Chica Village homes and residents.
The nature of the estuary-like terrain and wetlands means that it’s very easy to stop fires at choke points, so the fire likely never posed any real threat to Boca Chica residents, SpaceX employees, or onlookers. It was also unlikely to damage SpaceX’s launch facilities or return to damage Starship S24 from the start, as both of are surrounded by a combination of concrete aprons, empty dirt fields, and a highway.
Still, the “brush” burned by the fire is a protected habitat located in a State Park and Wildlife Refuge. While fire is a natural and often necessary element of many habitats, including some of those in Boca Chica, this is the second major brush fire caused by Starship testing since 2019, which may be less than desirable. At a minimum, fighting fires around Starbase generally requires firefighters to walk or even drive on protected wetlands and salt flats, the impact of which could ultimately be as bad for wildlife and habitats as the fire itself.
SpaceX’s Federal Aviation Administration (FAA) Programmatic Environmental Assessment (PEA), which fully greenlit the company’s existing Starbase Texas facilities and launch plans earlier this year, only discusses fire [PDF] a handful of times. Repairing and preventing future damage to wetlands, however, comes up dozens of times and is the subject of numerous conditions SpaceX must meet before the FAA will grant Starship an orbital launch license.
Ultimately, given that the FAA approved that PEA in full awareness of a 2019 brush fire caused by Starhopper (an early Starship prototype) that may have been as bad or worse than 2022’s, there’s a chance that it will play a small role in the ongoing launch licensing process, but the odds of it being a showstopper are close to zero. Still, it would likely benefit SpaceX at least as much as the surrounding Boca Chica wilderness if it can implement changes that prevent major brush fires from becoming a regular ‘accidental’ occurrence.
Tesla Full Self-Driving is now the centerpiece of the company’s newly revised Referral Program, which launched on October 29.
Instead of referring people to purchase vehicles and the referrer receiving $250 in Tesla Credit, the new program now incentivizes Full Self-Driving subscriptions.
If a Tesla owner is on an FSD trial and uses a referral code to subscribe to Full Self-Driving, the person whose Referral Link was used will receive one month of FSD (Supervised). Their code can be utilized 12 times per year, with January 1 marking the reset date.
Realistically, this means that if your Referral Code is used by 12 Tesla owners on an FSD trial, you will receive a full year of FSD for free.
🚨 Here is Tesla’s new Referral Program for Full Self-Driving (Supervised):
When someone subscribes to FSD using your link, you’ll get a month free. Up to a year of FSD is available to you for free!
If you’d like to use my link: https://t.co/g00IX9OCE3 https://t.co/GFBzEO2jjS
— TESLARATI (@Teslarati) October 30, 2026
The previous program made it pretty difficult to get referrals; buying a vehicle is obviously a much larger financial strain than subscribing to Full Self-Driving for a month.
Of course, the previous Referral Program also offered a tangible benefit: $250 in credits you could use on Service, Supercharging, or anything in the Tesla Shop. It truly could pay for someone’s travel for a year. It recently bought me a new backpack and a T-shirt.
However, this new program is much more attainable for those who do not have a massive online presence of a slew of friends in the Tesla community who will use the code and max out subscriptions for vehicle purchases.
Woke up to maxed out Referrals! Thank you guys, that’s awesome!
Share your referral link below so others can use it! https://t.co/kesbwTcoTV
— TESLARATI (@Teslarati) October 30, 2026
The Full Self-Driving suite will now be the keystone of the Referral Program, which makes it more inclusive and more fun for everyone with an awesome benefit.
It also gives the impression that Tesla is truly focused on FSD subscriptions, something that saw a tremendous increase in volume in Q3, as 75 percent of deliveries for the quarter came with an FSD subscription attached.
Full Self-Driving data is so instrumental to the suite’s improvement that this kind of program benefits Tesla as much as it does the consumer.
Elon Musk
Tesla made napping in a Robotaxi easier with its latest update
Tesla’s quiet mode reaches Model Y Robotaxis, blacking out the screen for riders wanting rest.
Tesla’s quiet mode, the setting that blacks out the screen for riders who want to rest, has moved beyond the Cybercab. A video posted Thursday by Spencer (@scotsrule08) shows the feature running in a Model Y Robotaxi on a night ride that appears to be in Dallas.
New quiet mode now on @Robotaxi https://t.co/2cM2eM9NeN — Spencer (@scotsrule08) October 29, 2026
The rider taps a small crescent moon icon in the bottom right corner of the map screen. The map, media player, app shortcuts and Grok prompt disappear, leaving a dark display with “Arriving soon,” the destination and a line reading “Tap display to exit quiet mode.” Controls a passenger may still need, including Pull Over, cabin temperature, volume and Support, stay visible. One tap anywhere brings the full map back.
Quiet mode first showed up in the Cybercab last week, which Teslarati reported alongside a new rear camera view. Tesla has been trimming cabin noise in other ways too. On October 25, Spencer reported that Robotaxi turn signals now chime for the first four blinks and then go silent. Tesla has not published release notes for either change.
Elon Musk has been pitching this use for more than a decade. In October 2014, he said that “maybe five or six years from now I think we’ll be able to achieve true autonomous driving where you could literally get in the car, go to sleep and wake up at your destination,”
By 2017 he was setting a higher bar. Speaking at TED, Musk said the hard part was not making self-driving work 99.9 percent of the time, “because, like, if a car crashes one in a thousand times, then you’re probably still not going to be comfortable falling asleep. You shouldn’t be, certainly.”
Owners asked for something similar in their own cars. In December 2019, a Tesla owner requested a Nap Mode that would keep the climate running and wake the occupant with an alarm, and Musk answered “Ok,” as Teslarati covered at the time.
The line returned when the Cybercab was unveiled at the We, Robot event in October 2024. “We’ll move from supervised Full Self-Driving to unsupervised Full Self-Driving, where you can fall asleep and wake up at your destination,” Musk said. On Tesla’s first quarter earnings call in April 2025, he called it the deciding measure: “The acid test is, can you go to sleep in your car and wake up in your destination and I’m confident that will be available in many cities in the US by the end of this year,”
Tesla has run driverless Model Y rides in Dallas and Houston since April, so a passenger dozing off on the way home is now a realistic use of the button. Tesla is also offering new riders a free first trip in both cities, according to an in-app screen shared by tracker Ethan McKanna, and said on its third quarter call that Cybercab rides would launch in Dallas next month.
News
FCC green lights SpaceX’s move to a showdown with Verizon and AT&T
The FCC advanced plans opening 482 MHz to satellite phone service, boosting SpaceX’s Starlink Mobile.
The Federal Communications Commission voted Thursday to move forward with a proposal that would open an additional 482 MHz of spectrum to satellite service beamed directly to ordinary phones, a step that could widen the road for SpaceX’s Starlink Mobile to compete with the country’s largest wireless carriers.
The commission adopted the notice of proposed rulemaking at its October open meeting in Washington, Reuters reported. The proposal would raise the number of bands eligible for Supplemental Coverage from Space from five to 13, according to the FCC fact sheet. Commissioners also advanced a companion item proposing an auction of 25 MHz in the 1675 to 1695 MHz and 2020 to 2025 MHz bands, which could be used for terrestrial service, direct to device service or both.
Thursday’s vote does not hand any spectrum to SpaceX. It opens a public comment period, and final rules will come later. Under the draft, comments would be due 60 days after the notice is published in the Federal Register. The FCC had not released the adopted text at the time of writing, so it is not yet clear whether any bands were changed before the vote.
That question is where the fight now moves. AT&T, Verizon and T-Mobile, through industry group CTIA, asked the FCC to drop the 2.5 GHz and 3.45 GHz bands, which make up 290 MHz of the 482 MHz on the table, as Teslarati reported ahead of the vote. T-Mobile argued satellite interference could wipe out up to 96% of a cell site’s uplink coverage area. SpaceX asked the commission to go the other way and add the 902 to 928 MHz band.
The rule change that matters most to SpaceX may be a structural one. Today, a satellite operator must lease spectrum from every carrier holding co-channel licenses across an entire region such as the contiguous United States. The proposal would replace that with a certification that the operator has coexistence agreements covering only the areas it plans to serve, or that it holds the terrestrial licenses itself.
SpaceX has spent this year building that second path. It bought EchoStar’s AWS-4 and H-block licenses in a deal worth roughly $17 billion, and earlier this month agreed to acquire Grain Management’s nationwide 800 MHz portfolio, which the company said would pave the way for Starlink to become a major US mobile carrier. The FCC approved SpaceX’s purchase of three unused AWS-3 licenses from Tristar on October 21, and cleared its plan for 15,000 next generation direct to cell satellites on October 6.
The regulator has not always sided with SpaceX. In April, the FCC dismissed a SpaceX petition seeking access to Mobile Satellite Service spectrum held by incumbents, and it rejected 2.5 GHz for satellite coverage when it first adopted the framework in 2024.
The carriers are also building their own defenses. In May, the three companies agreed in principle to form a joint venture pooling spectrum for satellite service, and T-Mobile remains SpaceX’s US launch partner for Starlink Mobile even as it leads the push to keep satellites out of 2.5 GHz. SpaceX President Gwynne Shotwell has said service on SpaceX’s own airwaves is targeted for early 2028.
Tesla Full Self-Driving becomes main pillar of new Referral Program
Tesla made napping in a Robotaxi easier with its latest update
