Connect with us

News

SpaceX’s Starbase environmental review is inches from the finish line

Ship 24 rolls down the highway to Starbase's launch facilities. (SpaceX)

Published

on

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.

https://twitter.com/danahull/status/1527041649477464065

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.

Advertisement
-
-

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.

Advertisement
-
-

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla Full Self-Driving insurance program with heavy discount expands

Published

on

Lemonade has expanded its innovative Autonomous Car insurance program to Tennessee, giving Tesla owners in the state a substantial discount on Full Self-Driving (FSD) miles. Announced on August 3, the product offers 50 percent off every mile driven with FSD activated, positioning the digital insurer as a leader in pricing insurance around autonomous technology.

The program, marketed as Lemonade Autonomous Car insurance, uses a direct connection via Tesla’s Fleet API (with customer permission) to automatically distinguish FSD-engaged miles from manual driving. Policyholders pay a low base rate when the vehicle is stationary and a few cents per mile when moving, with the 50 percent reduction applied specifically to FSD miles.

Coverage includes standard protections such as liability, collision, comprehensive, roadside assistance, and Tesla-specific benefits like access to certified repair shops and emergency crash services. Eligible vehicles require Hardware 4, as well as recent firmware.

Lemonade first unveiled the product on January 21 of this year, describing it as a first-of-its-kind offering designed for self-driving cars, starting with Tesla FSD. It began rolling out in Arizona on January 26, followed by Oregon about a month later. Subsequent expansions brought it to Indiana in early June 2026 and Colorado later that month.

Tennessee marks the fifth state.

Tesla Full Self-Driving gets outrageous insurance offer with insanely cheap rates

The discount rests on Lemonade’s strong belief in the safety of Tesla’s FSD system. The company cites Tesla’s data showing that FSD-driven miles are twice as safe as those driven manually, or associated with roughly a 50 percent crash reduction.

Lemonade Co-founder and President Shai Wininger has emphasized this distinction: “Traditional insurers treat a Tesla like any other car, and AI like any other driver. But a car that sees 360 degrees, never gets drowsy, and reacts in milliseconds can’t be compared to a human.”

He added that “Teslas driven with FSD are involved in far fewer accidents” and committed that as FSD software improves and becomes safer, Lemonade’s prices will drop further.

Tesla Full Self-Driving gets an offer to be insured for ‘almost free’

This approach leverages Lemonade’s existing pay-per-mile technology and AI-driven risk models, which analyze nuanced vehicle data including software version and sensor performance. The company expects the model to reward higher FSD usage with greater savings while supporting mixed households that include both Tesla and non-Tesla vehicles under one policy. Bundling with home, renters, or pet insurance can yield additional discounts.

As autonomous driving technology advances, Lemonade’s state-by-state expansion of usage-based pricing that directly reflects real-world safety data represents a notable shift in how insurers evaluate risk.

Tesla owners in the five available states – Arizona, Oregon, Indiana, Colorado, and now Tennessee – can obtain quotes quickly through the Lemonade app or website, potentially lowering the overall cost of ownership for vehicles equipped with advanced driver-assistance systems. Further states are expected as regulatory approvals progress.

Continue Reading

Cybertruck

Tesla quietly made the Cybertruck even stronger

Published

on

Credit: Tesla

Tesla has continued to flex the strength, rigidity, and robustness of its all-electric pickup, the Cybertruck. In fact, since 2019, Cybertruck’s ability to avoid dents, dings, and even gunfire has been one of the main selling points Tesla has used to attract buyers who are looking for a vehicle that can handle the most intense challenges.

But that does not mean Tesla is not still actively trying to make it even better.

In a new hardware update, Tesla has decided to change the material of the Cybertruck’s underbody panels from aluminum to carbon fiber, a move that aims to not only increase pricing efficiency but also improve strength.

RELATED:

Tesla Cybertruck is officially the safest pickup, IIHS says

Cybertruck Lead Engineer Wes Morrill confirmed the change was made to the Cybertruck recently after it was spotted by Coleton Guerin of Out of Spec. This particular trim level was a Cyberbeast, but it is being applied to all trims to keep supply chain efficiency high and have less variance across trim levels.

Morrill said that Tesla tested different materials for the underbody panel protection, and carbon fiber performed better than aluminum, which is what the company was using since its first deliveries in 2023.

Additionally, there are some efficiency improvements because Tesla can better form the areas around the bolts to keep underbody airflow cleaner than previously.

Carbon fiber is traditionally lighter and more durable than aluminum, which is why it is such a popular material among luxury automakers, and EV makers will utilize some of the materials around battery packs to save weight.

This is the first instance of Tesla utilizing carbon fiber on the Cybertruck’s exterior to help with overall performance and strength. As previously mentioned, Tesla used aluminum to protect the underside of the body, but it is pretty typical for the company to continue making engineering changes that will improve the car in the future.

Continue Reading

News

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

on

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Continue Reading