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.
News
Tesla expands Robotaxi in a way that was long anticipated
Instead, it has to do with the consumer base it offers Robotaxi to, because it has not offered it to everyone in the past.
Tesla has expanded Robotaxi in a way that was long anticipated, and it does not have to do with a new, larger geofence in a city where it already offered its partially autonomous ride-hailing suite, or a new city altogether.
Instead, it has to do with the consumer base it offers Robotaxi to, because it has not offered it to everyone in the past.
Tesla has taken a major step forward in its autonomous ride-hailing ambitions with the official launch of the Tesla Robotaxi app for Android users. Released on the Google Play Store on April 24. Titled simply “Tesla Robotaxi,” the app is now available to download directly from Tesla.
The @Tesla Robtoaxi App has just officially launched for Android users. Go get some rides y’all!
Download: https://t.co/D2jIONXc91 pic.twitter.com/rQ6TD14zkC
— Sawyer Merritt (@SawyerMerritt) April 24, 2026
This rollout fulfills a long-anticipated expansion that opens the service to hundreds of millions of Android smartphone users who were previously unable to access it on iOS alone.
The app delivers a streamlined, driverless ride experience powered by Tesla’s automated driving technology.
Users sign in with a Tesla Account, view the current service area map within the app, enter a destination, and receive an estimated fare and arrival time before confirming the ride. When a Model Y from the Robotaxi fleet arrives, riders confirm the license plate, enter the vehicle, fasten their seatbelt, and tap “Start Ride” on either the app or the vehicle’s touchscreen.
During the trip, passengers have access to all the same controls that iOS users do, and can adjust climate settings, seat positions, and music while tracking progress on an in-app map. The interface also allows drop-off changes or support requests if needed. After the ride, users exit, close the doors, and submit feedback.
This Android availability directly broadens the rider base for Robotaxi in its initial service areas. Unfortunately, Android users are used to being subject to delayed launches of new features available to Tesla owners.
By removing the iOS-only barrier, Tesla instantly expands the addressable market, enabling far more people to summon and use the autonomous vehicles already operating on public roads.
The move is a foundational requirement for scaling ride volume and gathering the real-world data needed to refine the unsupervised Full Self-Driving system that powers every trip.
For the Robotaxi program itself, the launch signals steady operational progress. It prepares the service for higher utilization rates as the fleet grows and supports the transition from limited early deployments to a more robust network.
Tesla expands Unsupervised Robotaxi service to two new cities
Tesla has indicated that users outside current service areas can sign up at the company’s website for future notifications, pointing to a deliberate, phased geographic rollout.
Looking ahead, the company plans to incorporate Cybercab vehicles to increase fleet capacity and efficiency while continuing to expand service territories. With the Android app now live, Tesla has removed a key adoption hurdle and positioned Robotaxi for the next phase of growth in autonomous urban transportation.
The infrastructure is now in place to support significantly larger rider demand as production and deployment accelerate.
News
UPDATE: SpaceX’s Falcon Heavy that launched a Tesla into space is back on a mission
SpaceX Falcon Heavy returns after 18 months away to deliver a satellite that only it could carry.
UPDATE: 10:29 a.m. et: SpaceX is standing down from today’s Falcon Heavy launch of the ViaSat-3 F3 mission due to unfavorable weather. A new target date will be shared once confirmed.
After an 18-month absence, SpaceX’s Falcon Heavy is returning to mission on Monday morning when it’s scheduled to lift off from Launch Complex 39A at Kennedy Space Center at 10:21 a.m. EDT.
The mission is called ViaSat-3 F3, and the heavy satellite payload needs to reach geostationary orbit, sitting 22,236 miles above Earth where its speed matches the planet’s rotation. Getting a satellite that heavy to that altitude demands more thrust than a single-core Falcon 9 can deliver.
This marks the Falcon Heavy’s 12th flight overall since its debut in February 2018, and its first since NASA’s Europa Clipper mission in October 2024.
Arguably, the most exciting element for spectators will be watching the booster recoveries in action when the two side boosters, B1072 and B1075, will attempt simultaneous landings at Landing Zone 2 and the newer Landing Zone 40 at Cape Canaveral Space Force Station, while the center core will be expended over the ocean.
SpaceX wins its first MARS contract but it comes with a catch
Following satellite deployment, expected roughly five hours after launch, ViaSat-3 F3 will spend several months traveling to its final orbital slot before undergoing in-orbit testing, with service entry expected by late summer 2026
As Teslarati reported, NASA awarded SpaceX a $175.7 million contract on April 16, 2026, to launch the ESA Rosalind Franklin Mars rover aboard a Falcon Heavy no earlier than late 2028, which would mark the first time SpaceX has ever sent a payload to Mars. That contract came on top of an already deep pipeline that includes the Roman Space Telescope, the Dragonfly Saturn mission, and multiple national security payloads.
SpaceX executed 165 missions in 2025 and now accounts for approximately 85% of all global orbital launches. With Starlink surpassing 10 million subscribers and an IPO targeting a $1.75 trillion valuation still ahead, Monday’s launch is one more data point in a company that has quietly become the backbone of both commercial and government space access worldwide.
Tesla is launching its solution to end Supercharger fights once and for all, eliminating any confusion on who is to charge next at a congested location.
Last year, a notable incident at a Tesla Supercharger led to a fight, and it all stemmed from a disagreement over who arrived at the location first.
Congestion at Tesla Superchargers is a pretty infrequent occurrence for most of us, but there are more congested and popular areas where wait times can be extensive. An unfortunate growing pain of EV ownership is the plain fact that chargers are not as available as gas pumps, and there are, at times, lines to charge.
This can cause tensions to flare and people to get entitled when visiting Superchargers. Nobody wants to spend hours at a Supercharger, but now, there will be no more confusion when there is a queue, and that’s thanks to Tesla’s new Virtual Queue for Superchargers.
Tesla is finally starting to build out the Virtual Supercharger Queue, according to Not a Tesla App, but it still relies on drivers to make it work.
When a driver is near a Supercharger that is full, a message will pop up on the Tesla App, using the driver’s location to determine their eligibility to join the virtual queue.
The app states:
“While the app is closed, Tesla uses your location to notify you of accurate wait times at Superchargers when you arrive.”
Another message within the app states:
“There is a waitlist to charge. Are you sure you want to start a charging session now?”
This sounds as if it will require drivers to act appropriately and only plug in when the app prompts them to do so, by letting them know it is their turn.
The app will notify the driver of their position in the queue, as well as how many vehicles are ahead of them.
Tesla launches first ‘true’ East Coast V4 Supercharger: here’s what that means
The company announced a while back that it would be working on a solution for this issue. Personally, I’ve only had to wait at a Supercharger for a charge on one occasion, and there was a line of between 3 and 10 cars during this singular occurrence.
I’m out at the Lancaster, PA Supercharger and showed up with a queue of three vehicles.
It’s now up to five and there have been several issues with order of arrival and confusion about who is first.
Any update on Supercharger queue? @elonmusk @aelluswamy @r_jegaa
— TESLARATI (@Teslarati) January 31, 2026
There were no conflicts or arguments about who had arrived first, but there was some discussion between several drivers during my time there about who was to charge first. Throw a non-Tesla EV into the mix, one that can only charge at a pull-in spot, and that causes even more of a complication.
Tesla expands Robotaxi in a way that was long anticipated
UPDATE: SpaceX’s Falcon Heavy that launched a Tesla into space is back on a mission
