News
Boeing Starliner abort test (mostly) a success as SpaceX nears Crew Dragon static fire
On November 4th, Boeing completed a crucial pad abort test of its reusable Starliner spacecraft, successful in spite of an unintentional partial failure of its parachute recovery system. Three days later, Boeing revealed what it believed to be the cause of that anomaly in a November 7th press conference.
Meanwhile, SpaceX – having completed Crew Dragon’s pad abort test in 2015 – is preparing for an equally important In-Flight Abort (IFA) test and is perhaps just a day or two away from static firing the Crew Dragon capsule assigned to the test flight.
According to a NASA press release after the test, it “was designed to verify [that] each of Starliner’s systems will function not only separately, but in concert, to protect astronauts by carrying them safely away from the launch pad in the unlikely event of an emergency prior to liftoff.” Although the test wasn’t without flaws, the pad abort test successfully demonstrated the ability of the four launch abort engines and control thrusters to safely extricate astronauts from a failing rocket.
Those theoretical astronauts would have almost certainly survived the ordeal unharmed despite the failed deployment of one of Starliner’s three main parachutes, testing the spacecraft’s abort capabilities and redundancy quite a bit more thoroughly than Boeing intended. To put it bluntly, Boeing’s above tweet and PR claim that the failed deployment of 1/3 parachutes is “acceptable for the test parameters and crew safety” is an aggressive spin on a partial failure that NASA undoubtedly did not sign off on.
Boeing and SpaceX have both suffered failures while testing parachutes, leading NASA to require significantly more testing. However, in a November 7th press conference, Boeing revealed that Starliner’s parachute anomaly wasn’t the result of hardware failing unexpectedly under planned circumstances, but rather a consequence of a lack of quality assurance that failed to catch a major human error. Boeing says that a critical mechanical linkage (a pin) was improperly installed by a technician and then not verified prior to launch, causing one of Starliner’s three drogue chutes to simply detach from the spacecraft instead of deploying its respective main parachute.
Space is Parachutes are hard
Parachutes have been a major area of concern for the Commercial Crew Program. Both SpaceX and Boeing have now suffered failures during testing and have since been required to perform a range of additional tests to verify that upgraded and improved parachutes are ready to reliably return NASA astronauts to Earth. Although the Starliner pad abort test did indeed demonstrate the ability to land the capsule safely under two main chutes, an inadvertent test of redundancy, the series of Boeing actions that lead to the failure will almost certainly be scrutinized by NASA to avoid reoccurrences.
Boeing believes that the parachute failure won’t delay the launch of Starliner’s Orbital Flight Test (OFT), currently targeting a launch no earlier than (NET) December 17th. However, it can be said with some certainty that it will delay Starliner’s crewed launch debut (CFT), at least until Boeing can prove to NASA that it has corrected the fault(s) that allowed it to happen. SpaceX is similarly working to qualify upgraded Crew Dragon parachutes for astronaut launches, although the company has thus far only suffered anomalies related to the structural failure of parachute rigging/seams/fabric.
Abort tests galore
Boeing’s Starliner pad abort test occurred just days prior to a different major abort test milestone – this time for SpaceX. SpaceX Crew Dragon capsule C205 will perform a static fire test of its upgraded SuperDraco abort system, as well as its Draco maneuvering thrusters.
SpaceX has made alterations to the SuperDraco engines to prevent a failure mode that abruptly reared its head in April 2019, when a leaky valve and faulty design resulted in a catastrophic explosion milliseconds before a SuperDraco static fire test. Prior to its near-total destruction, Crew Dragon capsule C201 was assigned to SpaceX’s In-Flight Abort test, and its loss (and the subsequent failure investigation) delayed the test’s launch by at least six months. Crew Dragon’s design has since been fixed by replacing reusable check valves with single-use burst discs, nominally preventing propellant or oxidizer leaks.
If capsule C205’s static fire testing – scheduled no earlier than November 9th – goes as planned, SpaceX may be able to launch Crew Dragon’s in-flight abort (IFA) test before the end of 2019e. Likely to be a bit of a spectacle, Crew Dragon will launch atop a flight-proven Falcon 9 booster and a second stage with a mass simulator in place of its Merlin Vacuum engine, both of which will almost certainly be destroyed when Dragon departs the rocket during peak aerodynamic pressure.
NASA made in-flight abort tests an optional step for its Commercial Crew providers and Boeing decided to perform a pad abort only and rely on modeling and simulations to verify that Starliner’s in-flight abort safety. Assuming that NASA is happy with the results of Starliner’s pad abort and Boeing can alleviate concerns about the parachute anomaly suffered during the test, Starliner’s uncrewed orbital flight test (OFT) could launch as early as December 17th. Starliner’s crewed flight test (CFT) could occur some 3-6 months after that if all goes as planned during the OFT.
If SpaceX’s In-Flight Abort (IFA) also goes as planned and NASA is content with the results, Crew Dragon could be ready for its crewed launch debut (Demo-2) as early as February or March 2020.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla has improved Dashcam playback with an awesome new addition, as the company has launched a web-based version that is potentially easier to navigate and operate.
The tool is available at dashcam.tesla.com and will be enabled as your vehicle receives the 2026.20 Software Version. Clips that are captured by your Tesla will be available on the Online Dashcam Clip Viewer once the files on your car’s storage drive are encrypted.
Not a Tesla App first noticed the new feature, and states that once your Tesla updates to 2026.20, the car will automatically protect the clips with an encryption key that is uniquely tied to your owner account.
Tesla Launches New Web-Based Dashcam Viewer https://t.co/AlJKXYxujJ pic.twitter.com/4igicYpvkX
— Not a Tesla App (@NotATeslaApp) June 2, 2026
The web-based viewer should be easier to operate for most. All you will do is head over to dashcam.tesla.com and log in using your account credentials.
Ensure your vehicle is updated to 2026.20 in order for the web-based viewer tool to fetch your vehicle’s saved dashcam clips.
Currently, only a small percentage of owners are updated to this, so it may be a couple of weeks until a majority of owners in the fleet are able to access this feature.
Watching Dashcam clips on the Tesla smartphone app is quick and convenient, as they can also be easily downloaded and stored right on your smartphone.
However, the clips are sometimes tougher to navigate, and in order to get details like self-driving activation, speed, and turn signals, owners have to screen record the Tesla app and crop out the rest of the screen.
It could also be a massive storage saver as you’ll be able to download the Dashcam clips from the online viewer and save them to your laptop, desktop, a flash drive, or even an external hard drive. This will keep all your clips in one place.
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
Tesla responds to Robotaxi skeptics with a massive move in Austin
