News
SpaceX’s Starbase environmental review is inches from the finish line
Update: Just two days after the FAA’s latest delay announcement, an online portal documenting SpaceX’s Starbase environmental assessment progress has been updated to show that the last step requiring “interagency consultations” was completed on June 2nd.
In theory, that means that to successfully complete its Programmatic Environmental Assessment (PEA) for orbital Starship launches, SpaceX merely needs to incorporate all recommendations, requirements, or mitigations added during the interagency review process into one final draft and presumably secure the approval of all relevant stakeholders one last time. Once those documents are complete, approved, and published, all Starbase will need to begin orbital Starship test flights is an FAA launch license.
Securing that launch license is its own can of worms with plenty of unique challenges, but it’s highly unlikely that SpaceX and the FAA won’t be able to come to some kind of agreement allowing the company to begin those test flights within a month or two of receiving a good environmental review. According to the FAA, the final results of the Starbase PEA are scheduled to be released on June 13th.
The US Federal Aviation Administration says that its environmental review of SpaceX’s plan to conduct orbital Starship launches out of South Texas has been delayed for the fifth time in five months.
However, despite the chronic delays and the FAA’s odd decision to announce a new delay every month instead of simply acknowledging that it doesn’t know when the process will be finished, there are now even more reasons to expect a positive outcome.
Even though there were attempts to spin the new information into something negative, a document acquired through the Freedom Of Information Act (FOIA) by Bloomberg revealed that the US Fish and Wildlife Service (FWS) had decided to approve its portion of the Starbase environmental review. Their only condition: that SpaceX implement a few small mitigation measures, “including contracting with a qualified biologist to conduct monitoring of vegetation and birds, operating an employee shuttle between the launch facility site and nearby town of Brownsville, reducing vehicle traffic, and adjusting lights to minimize the impact on sea turtles.” Bloomberg chose not to publish the documents it received through the FOIA process.
In the same set of documents, the FWS also revealed that SpaceX has removed a request for permission to build a small desalination plant, a natural gas production and liquefaction plant, and a natural gas power plant at or near Starbase’s launch site from Starbase’s first Programmatic Environmental Assessment (PEA). That change comes as little surprise. In fact, SpaceX’s decision to pursue a “programmatic” assessment instead of a more common standalone assessment means that the company will be able to pursue additions to a basic Starbase environmental approval without having to rebuild the foundation each time.
In this case, a “basic approval” would mean the ability to conduct at least a few orbital Starship launches per year. Once that foundation is secured, SpaceX should be able to tier new environmental assessments on top of it and pursue permission for a desalination plant, natural gas production, more annual launches, or any other additions that might benefit Starbase. The simpler the foundation, the harder it should be for environmental stakeholders and agencies to protest or prevent SpaceX from receiving a good outcome.
“The FAA now plans to release the Final PEA on June 13, 2022 to account for ongoing interagency consultations concerning Section 4(f) of the Department of Transportation Act. All other consultations and analysis have been completed at this time.”
Another cause for optimism: after four delays of one or two months, the FAA’s latest delay announcement only pushes the conclusion of the review from May 31st to June 13th. Additionally, the FAA confirmed that only one small component of the entire review remains unfinished. Every other major component has been completed successfully and will likely result in a Finding Of No Significant Impact (FONSI) or Mitigated FONSI that would greenlight the environmental side of conducting orbital Starship launches out of Boca Chica, Texas.
When the draft PEA was first published, the FAA noted several points of contention over Section 4(f) compliance, which is designed to “protect significant publicly owned public parks, recreation areas, and wildlife and waterfowl refuges, as well as significant historic sites, whether they are publicly or privately owned.” At the time, the main problem was SpaceX’s request to close the public Boca Chica Beach and the only highway to it for up to 500 hours (~42 days), as well as a contingency that would allow for another 300 hours of closures to safely respond to emergencies.
Thanks to an even more in-depth environmental impact statement (EIS) completed in 2014 for a Falcon 9 and Falcon Heavy launch pad where Starship’s launch site now stands, we know that SpaceX has already met Section 4(f) demands with a plan for up to 180 hours of road closures per year. In the absolute worst-case scenario, SpaceX should be able to drastically reduce its road closure request to satisfy the Department of Transportation. Subsisting on roughly 20-30 days of closures per year would undoubtedly maim Starbase’s utility but it would at least allow SpaceX to conduct a few basic orbital test flights and some limited ground testing while it rapidly redirects most of its effort to finishing alternative Starship production and launch facilities in Florida.
Regardless, it’s now quite likely that SpaceX’s Starbase environmental review will finally be over by the end of June, freeing up the FAA and SpaceX to focus fully on the launch license side of the equation. Meanwhile, SpaceX still has weeks or even months of work ahead of it to prepare a Starship and Super Heavy pair for their first orbital launch attempt, so (for now) there is no risk of the company being forced to sit around and wait for the gears of bureaucracy to turn.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
