News
NASA head calls out SpaceX CEO Elon Musk over Starship event in bizarre statement
Roughly 24 hours before SpaceX CEO Elon Musk was scheduled to present an update on the company’s Starship launch vehicle development, NASA administrator Jim Bridenstine tweeted a bizarre and wholly unprovoked statement on the subject.
Seemingly equating SpaceX’s recent Crew Dragon delays with the distribution of Elon Musk’s public attention, the NASA administrator’s comment was almost universally criticized by the spaceflight community at large – and rightfully so.
First, some context. Created in 2010 and first supported with serious funding some 12-24 months later, NASA’s Commercial Crew Program (CCP) exists to replace the astronaut transport capabilities once offered by Space Shuttle and now achieved with contracts for seats on Russian Soyuz launches. Primarily the result of inept bureaucracy in NASA and Congress, the Space Shuttle was “retired” in 2011 in full knowledge that the US would have to rely on Russia to get NASA astronauts to the ISS until 2015 (at the absolute earliest).
Congress shut down multiple 2010 proposals to continue Shuttle flights until the late 2010s, choosing instead to kill the Shuttle and divert its associated funding to the expendable Ares V rocket (now the Space Launch System, SLS) and Orion crew capsule. More on that later...
Retweeted by Bridenstine’s official Twitter account, above is the absolute best-case interpretation of the NASA administrator’s comment. Although Eric Berger means well, the interpretation gives NASA far too much credit. Specifically, Bridenstine (or whoever fed him the statement) went out of his way to make it entirely one-sided in its focus on SpaceX. By all appearances, it would have never been posted if not for Elon Musk’s plans to present on Starship. Bridenstine additionally notes that “Commercial Crew is years behind schedule” and indicates that “NASA expects to see the same level of enthusiasm focused on [its] investments”.
Altogether, it’s simply impossible to interpret it as anything less than Bridenstine scolding SpaceX – and SpaceX alone – for not falling to the floor, kissing NASA’s feet, and pretending that Crew Dragon and Falcon 9 are the only things in existence. Absent from Bridenstine’s criticism was NASA’s other (and even more delay-complicit) Commercial Crew Partner, Boeing, who has yet to complete a pad abort or orbital flight test of its Starliner spacecraft. SpaceX completed Crew Dragon’s pad abort in 2015 and completed a flawless orbital flight test in March 2019.
In essence, Bridenstine is publicly implying that SpaceX needs to stop being (or appearing to be) distracted by Starship and focus 100% on Crew Dragon. Boeing was not mentioned, despite being a minimum of six months behind SpaceX and dramatically more ‘distracted’ in the Bridenstine-style interpretation of the word. For reference, Boeing is a publicly-traded company with 150,000 employees, annual revenue of more than $100B, and a market cap of $206B. Boeing has 14 subsidiaries, a handful of which are involved in spaceflight, and has no less than one or two dozen products that are each more fiscally important to shareholders and board members than Starliner.
Compared to Boeing’s annual ~$100B revenue, the entirety of the Starliner development program – from the drawing board in 2010 to crewed, orbital spaceflight sometime in 2020 – is ~$4.8B. On the scale of corporate focus, Starliner has likely been a blip at most in 2019, with the company probably far more focused on the systematic organizational failures that lead to the deaths of hundreds of people in two near-identical 737 MAX crashes. Alas, NASA administrator Jim Bridenstine did not release a statement publicly implying that Boeing needs to devote the “same level of enthusiasm” to Starliner after the second fatal 737 MAX crash in March 2019. Nor did Bridenstine release a statement charging Boeing with a lack of focus after continuous reports of issues with the company’s KC-46 Pegasus tanker program, nor Boeing’s recent $9.2B US Air Force trainer jet contract, or myriad other corporate focuses.
On the other hand, as Musk noted in his relatively subtle September 28th responses to Bridenstine’s implicitly derisive comment, something like 50-80% of the entirety of SpaceX’s workforce and resources are focused on Crew Dragon, the Falcon 9 rockets that will launch it, or a combination of both. At present, Starship is – at most – a side project, even if its strategic importance to SpaceX is hard to exaggerate. The same is largely true for Starlink, SpaceX’s ambitious internet satellite constellation program. It may be true that Starship will eventually make Crew and Cargo Dragon (as well as Falcon 9 and Falcon Heavy) wholly redundant, but that is likely years away and SpaceX will support NASA – as it is contractually required to – for as long as the space agency has vested interest in using Crew Dragon.
At the same time, NASA has explicitly and publicly chosen to prioritize safety over schedule with the Commercial Crew Program, accepting the possibility of delays and cost overruns to ensure that SpaceX and Boeing can build the safest spacecraft possible.
In a September 28th interview with CNN, Musk bluntly noted that the hardware was – at this point in time – more or less ready for flight and will be on-site at SpaceX’s Pad 39A Florida launch site within the next two months. According to Musk, from then on, any additional launch delays can almost entirely be attributed to the paperwork and reviews NASA must complete before giving SpaceX the go-ahead. If Bridenstine wants SpaceX to launch astronauts sooner, one – and possibly the only – solution is to tackle the roadblocks created by NASA’s own self-enforced red tape. The question, then, is whether Bridenstine wants to cut away red tape that may (or may not) be there for good reason.
When the pot calls the kettle black
Detached from whining about a contractor’s CEO presenting about a non-NASA program, complaining about Commercial Crew delays is at least slightly more reasonable. Originally intended to launch as early as 2015, Congress systematically underfunded the Commercial Crew Program by more than 50% for over half a decade, dispersing $2.4B of the $5.8B NASA requested from 2011 to 2016. Unsurprisingly, this completely upended Boeing and SpaceX development schedules. By September 2014, SpaceX aimed to have Crew Dragon certified by NASA for astronaut transport before the end of 2017, but even then, NASA already saw that schedule as overly optimistic.
It would be another two years before Congress began to seriously fund Commercial Crew at its requested levels, beginning in FY2016. In response to Bridenstine, former NASA deputy administrator Lori Garver noted that over the ~5 years Congress consistently withheld hundreds of millions of dollars of critical funds from Commercial Crew, NASA’s SLS rocket and Orion spacecraft were just as consistently overfunded above and beyond their budget requests. From 2011 to 2016 alone, SLS and Orion programs requested $11B and received an incredible $16.3B (148%) from Congress, while Commercial Crew requested $5.8B and received $2.4B (41%).
Ironically, despite literally receiving almost seven times as much funding as Crew Dragon and Starliner, SLS and Orion are arguably just as – if not more – delayed than their commercial brethren. Originally intended to launch an uncrewed test flight in 2017, there is now little to no chance that that mission (known then as EM-1 and now as Artemis-1) will launch before 2022, a delay of roughly half a decade. The cost of the SLS/Orion program recently crested $30B, a figure likely to grow to ~$40B before it has conducted a single launch. Of that funding, approximately a third has gone to Boeing, the primary contractor responsible for NASA’s comically-delayed SLS Core Stage – the orange booster pictured above.
The Commercial Crew development program will likely cost NASA $8B total over 9-10 years and produce two clean-sheet, high-performance, (relatively) low-cost crewed spacecraft. After their demonstration launches are completed, NASA will transition to fixed-price service contracts with SpaceX and Boeing to routinely send astronauts to the ISS several times per year.
Put simply, if Bridenstine actually cared about defending “the investments of the American taxpayer” more than wielding their sanctity as a political weapon, he wouldn’t have folded like a house of cards at the slightest resistance to his attempts to cull SLS/Orion delays and cost overruns, and he certainly wouldn’t be wasting breath complaining about what SpaceX’s CEO is or isn’t talking about.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
-
-
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.
If you’re driving a Tesla in Tennessee, FSD miles now cost 50% less to insure with Lemonade. Autonomous Car is now live in TN.https://t.co/4CDTuhyORi pic.twitter.com/QZk4LBIs6f
— Lemonade (@Lemonade_Inc) August 3, 2026
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.
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:
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.
good eye – it’s a new material. Testing showed it to be more durable than the aluminum while being lower weight and cost. Also slight efficiency improvement since we can better form the areas around the bolts to keep the underbody airflow cleaner than what stamped aluminum allows
— Wes (@wmorrill3) July 30, 2026
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.
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.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
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:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
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:
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
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:
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
Tesla Full Self-Driving insurance program with heavy discount expands
Tesla quietly made the Cybertruck even stronger
