News
Boeing Starliner spacecraft successfully returns to flight 29 months after ill-fated debut
More than three years after SpaceX’s Crew Dragon spacecraft first safely reached orbit and almost three and a half years after Boeing’s Starliner crew capsule’s ill-fated launch debut, Boeing has finally returned to flight and made it farther than ever before towards a successful test flight.
Almost ten months after Boeing’s first attempt at Starliner’s second uncrewed Orbital Flight Test (OFT-2 #1), the stars aligned. As expected, the United Launch Alliance’s Atlas V rocket lifted off on time at 6:54 pm EDT (22:54 UTC) on Thursday, May 19th, ascending from Cape Canaveral Space Force Station (CCSFS) Launch Complex 41 (LC-41) without issue. After a four and a half minute burn, the Atlas V booster – powered by a Russian-built RD-180 engine – separated and the Centaur upper stage – powered by two Aerojet Rocketdyne RL-10 engines – took over.
Another six minutes later, Centaur shut down and Starliner ultimately separated from the rocket a bit less than 12 minutes after liftoff. Unlike SpaceX’s Crew Dragon, though, Starliner separated from its launch vehicle before reaching orbit – a task Boeing engineers chose to reserve for the spacecraft itself to limit stress on the spacecraft and crew in the event of a high-altitude abort. However, that design decision also adds significant risk in other ways and – after the spacecraft’s extremely poor performance during its first launch attempt – turns a Starliner launch into a sort of 30-minute cliffhanger.
While just a hair shy of true orbit, Starliner’s suborbital launch trajectory means that whether or not it wants to, the spacecraft will reenter Earth’s atmosphere about an hour after liftoff if it can’t complete a minute-long orbital insertion burn. In the case of OFT-2, that burn came about 31 minutes after liftoff and was thankfully successful, inserting Starliner into a stable, circular orbit and undoubtedly triggering a massive wave of relief for all employees involved. From that stable orbit, Starliner can finally begin to prepare to rendezvous with the International Space Station (ISS) for the first time ever.
The story of Starliner’s tortured orbital flight test (OFT) campaign began in earnest on December 20th, 2019, when an uncrewed prototype of the Boeing spacecraft first attempted to launch to the International Space Station (ISS) atop a United Launch Alliance (ULA) Atlas V rocket. Infamously, a major software bug that could have been easily detected with even the most basic integrated hardware-in-the-loop prelaunch testing caused Starliner to lose control the moment it separated from Atlas V. Only through a heroic last-second effort was Boeing able to insert Starliner into orbit and prevent the spacecraft from reentering prematurely, which would have likely destroyed it. After hundreds of seconds of unplanned burns of its many attitude control thrusters, Starliner no longer had enough propellant to safely reach the ISS.
Boeing would later correct another completely unrelated software bug mere hours before Starliner’s planned reentry and recovery. If undetected, it could have caused the spacecraft’s capsule and service sections to crash into each other shortly after separation, potentially damaging the capsule’s heat shield and dooming it to destruction during reentry. Had astronauts been aboard, either of the two software bugs could have potentially resulted in crew fatalities and total mission failure. Instead, through a combination of sheer luck and a quick emergency response from Boeing and NASA teams, the spacecraft was saved and recovered in New Mexico.
On a positive note, aside from raising deep and foreboding questions about Boeing’s software development and integrating testing capabilities and NASA’s inept and inconsistent oversight, OFT-1 did still demonstrate that Starliner was able to reach orbit, operate in space, deorbit, survive atmospheric reentry, and land softly under parachutes.
However, the problems were about to continue and spread beyond software. On July 30th, 2021, shortly before a different uncrewed Starliner was scheduled to reattempt the first Orbital Flight Test, the launch was aborted. Eventually, Boeing and NASA reported that 13 of Starliner’s 24 main oxidizer valves had failed to open during a prelaunch test just a few hours before liftoff. The resulting investigation ultimately concluded that the Aerojet Rocketdyne-supplied valves had a faulty design and that Boeing had failed to properly insulate those valves from humidity and water intrusion. It also delayed the next OFT-2 launch attempt by almost ten months.
But finally, after almost 30 months of work to rectify those software and hardware failures, Starliner has intentionally reached a stable orbit without running into a major problem – certainly cause for some amount of optimism. Still, safely rendezvousing and docking with the ISS may be the biggest and riskiest challenge Starliner has faced yet and Boeing will be attempting the feat for the first time in its modern history. Starliner is expected to begin proximity operations around 3 pm EDT on May 20th. If the first attempt is perfect, docking could occur as early as 7:10 pm EDT.
Ultimately, even if Boeing is now more than three years behind SpaceX, whose Crew Dragon spacecraft first reached orbit and the ISS in March 2019 and launched its first astronauts in May 2020, it’s essential that NASA has two redundant crew vehicles available to carry its astronauts to and from the station. SpaceX’s extraordinary success and heroic efforts have allowed the company to singlehandedly ensure NASA access to the ISS since November 2020, but no complex system is perfect and even a failure outside of SpaceX’s control could trigger a long delay that could threaten NASA’s uninterrupted presence on the International Space Station.
NASA has contracts with SpaceX to maintain that uninterrupted presence at the ISS through Crew Dragon’s Crew-7 mission, which could launch as early as September 2023 and would then return to Earth around March 2024. If OFT-2 is completed without significant issue, Boeing’s next priority is Starliner’s Crew Flight Test (CFT), a crewed launch debut that could happen before the end of 2022.
After that, Starliner’s first operational crew launch could potentially occur in Q1 2024, just before Crew Dragon’s Crew-7 recovery. Following Crew Dragon’s near-flawless uncrewed test flight, it took another 14 months for NASA and SpaceX to proceed to Demo-2, Dragon’s Crew Flight Test equivalent. Dragon’s first operational astronaut launch occurred in November 2020, 20 months after its uncrewed demo flight. If NASA follows a similar path for Starliner, that meshes well with an operational debut in early 2024.
News
Tesla Full Self-Driving insurance program with heavy discount expands
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.
Cybertruck
Tesla quietly made the Cybertruck even stronger
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.
News
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
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

