News
SpaceX’s Starbase environmental review delayed another month
The FAA says that it will take at least another month to complete a crucial environmental review of orbital Starship launches from SpaceX’s South Texas Starbase facilities.
The agency now expects that Starbase’s Programmatic Environmental Assessment (PEA) will be completed no earlier than March 28th, 2022, delaying the process at least another four weeks on top of an initial delay from December 31st, 2021 to February 28th, 2022. However, while the FAA gained some infamy for repeatedly delay SpaceX Starbase launch operations in late 2020 and early 2021, there is growing evidence that other US government agencies – not the FAA itself – are primarily responsible for most of the review’s delays.
Namely, information acquired through a Freedom Of Information Act (FOIA) request indicates that US Departments of Fish and Wildlife Services (FWS) and National Parks Services (NPS) are the primary sources of recent delays and the only real sources of discord this late in the process. As an example, as of the end of October 2021, the NPS had a list of at least 31 comments on SpaceX’s Starbase Draft PEA, each of which would have required a detailed response and additional back-and-forth to refine each response. The critiques and requests cover virtually every aspect of orbital Starship launches from Starbase, including FAA launch license details, recent SpaceX land acquisitions, impacts on a local Civil War battlefield landmark, pad lighting, air quality, noise, paint colors, road closures, Raptor thrust, contingency plans, and more.
Meanwhile, in a general review, the Department of the Interior (DOI) – speaking on behalf of the FWS and NPS – raised concerns about “launch site blast area hazards, closure of FWS and NPS lands, environmental justice (EJ) concerns, NHPA Section 106 and 110(f), [endangered] species, air quality emissions, and climate change impacts. It’s difficult to say how many of the concerns raised are actually serious. For example, the point repeatedly made by the DOI, FWS, and NPS is that hypothetical emissions from a natural gas power plant SpaceX proposed to build in its Draft PEA would violate EPA rules.
However, since that draft was published, there is growing evidence that SpaceX is behind a brand new power distribution line set to connect Boca Chica and Brownsville, Texas. The new lines appear to be sized to provide Starbase with enough power to entirely preclude the need for the construction of any dedicated power plants on site. Only a backup power source of some kind would be necessary. Assuming SpaceX is actually behind the development, it’s difficult to believe that the company hasn’t communicated that change of plans to the FAA and other Starbase PEA stakeholders.
As another example, the Fish and Wildlife Services’ own list of complaints includes the bizarre request that SpaceX increase its estimate for the number of failures that will occur during future Starship testing fivefold from 10% (already an extremely pessimistic figure) to 50% because “[nine] of 16 tests or hops that have occurred [at Starbase]…resulted in some type of anomaly with fire or debris.” While true that many of SpaceX’s developmental Starship tests have resulted in major failures or explosions, the FWS appears to fundamentally misunderstand the purpose of those failures and SpaceX’s approach to development, which is to learn from failures and prevent their reoccurrence. Something would have to go terribly wrong for half of all future Starship ground and flight tests to result in failure when SpaceX’s goal is to develop Starship into a reliable launch vehicle – not to futilely test prototypes forever.
Ultimately, it remains to be seen if SpaceX and the FAA will be able to secure the DOI, FWS, and NPS approvals required to finish the Starbase PEA. If the parties can’t come to some kind of agreement, SpaceX may be forced to effectively restart the environmental review process from scratch and pursue a more thorough Environmental Impact Statement (EIS). Completing an EIS could easily take years, potentially forcing SpaceX to give up on South Texas as a site for regular orbital Starship launches.
While CEO Elon Musk recently implied that SpaceX would never abandon Starbase and might use the site as a sort of dedicated research and development facility, it’s difficult to believe that the cost of operating and maintaining an entire Starship factory and orbital launch site would make sense from a programmatic or financial perspective given that SpaceX appears likely to build a Florida Starbase for East Coast Starship launches. SpaceX already has full environmental approval to launch 24 Starships per year from its Kennedy Space Center Pad 39A facilities.
News
Why SpaceX is finishing another space-internet system that isn’t Starlink
SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.
SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.
Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.
With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.
A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.
Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.
For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.
Elon Musk
Tesla gives the Roadster an official “Go for launch” demonstration date
Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.
Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.
Go for launch pic.twitter.com/Khu03eiZ04
— Tesla (@Tesla) September 12, 2026
Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.
The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.
Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video
Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.
The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.
Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.
Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.
In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.
Glad you are safe. Even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance coming as part of the next big upgrade (v15).
— Ashok Elluswamy (@aelluswamy) September 11, 2026
The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.
The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.
Tesla is rolling out a new FSD version with a massive safety addition
Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.
Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.
A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.
European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.
Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.
Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.
Why SpaceX is finishing another space-internet system that isn’t Starlink
Tesla gives the Roadster an official “Go for launch” demonstration date
