News
NASA says SpaceX's Crew Dragon abort test is go for launch on doomed Falcon 9 rocket
NASA has formally given SpaceX permission for Crew Dragon’s second launch – a crucial test flight that should be the last before SpaceX launches NASA astronauts to the International Space Station (ISS) for the first time ever.
Known as its In-Flight Abort (IFA) test, Crew Dragon will attempt to escape a Falcon 9 rocket while airborne, a feat that CEO Elon Musk says will almost certainly destroy the rocket in the process. Technically speaking, NASA and SpaceX completed what is known as a Launch Readiness Review (LRR) sometime on Thursday, allowing SpaceX to proceed with launch preparations. By all accounts, Crew Dragon’s IFA test will likely be one of the most spectacular SpaceX launches ever, given that it is all but guaranteed to result in the intentional in-flight failure of a massive Falcon 9 rocket – “destroyed in Dragon fire” according to Musk.
Thanks to a much smoother launch flow compared to Crew Dragon’s Demo-1 orbital launch debut on Falcon 9, SpaceX’s newest Crew Dragon capsule is scheduled to lift off from Kennedy Space Center Launch Complex 39A (KSC LC-39A) as early as 8 am EST (13:00 UTC), Saturday, January 18th. The In-Flight Abort test will likely be one of Crew Dragon’s most challenging hurdles yet but success would be a major boon for the spacecraft’s demonstrated safety. While both Boeing and SpaceX will ultimately ferry NASA astronauts to and from the ISS, only SpaceX chose to prove Crew Dragon’s in-flight abort capabilities in the real world.
Effectively condemned to destruction to support a greater cause after a productive life, Falcon 9 Block 5 booster B1046 rolled out to Pad 39A – Crew Dragon mounted atop it – on January 16th after successfully performing its last routine static fire on the 11th. As previously discussed on Teslarati, B1046 is the first Falcon 9 Block 5 booster completed by SpaceX and is thus also the oldest flightworthy rocket in the company’s substantial fleet.
“After becoming the first SpaceX booster to launch three times in December 2018, B1046 spent several months at SpaceX’s Hawthorne, CA factory undergoing inspections and refurbishment. At some point, SpaceX assigned the thrice-flown booster to support Crew Dragon’s In-Flight Abort (IFA) test – effectively a death sentence – and shipped the booster to Florida, where it publicly appeared for the first time in months on October 3rd, 2019. Given that four more Falcon 9 boosters have now successfully performed three (or even four) orbital-class launches each, B1046’s now-imminent demise is certainly disappointing but remains extremely pragmatic.”
Teslarati.com — January 15th, 2020
As such, there is arguably no better booster for SpaceX to expend even if its loss is still less satisfying than a successful post-launch landing. In fact, aside from NASA’s prematurely-retired Space Shuttle, the entire history of orbital-class rocketry has effectively operated on the assumption that it’s both normal and necessary for rockets to be almost entirely expendable.
Only by sheer force of will has SpaceX turned that assumption on its head, making the act of expending Falcon 9 or Falcon Heavy boosters feel suddenly morose. Even then, the practice of propulsively landing orbital-class boosters is scarcely four years old, while reusing those boosters has been ongoing for less than three years. As such, B1046’s demise should be enjoyed for what it ultimately is: the spectacular retirement of a rocket that has already helped launch three separate payloads to orbit.
-
Perhaps even more importantly, B1046’s sacrifice should – if things go as planned – also pave the way for Crew Dragon to launch its first NASA astronauts into orbit just a few months from now. For the test to be successful, however, Crew Dragon will have to perform an extremely precise string of maneuvers – the failure of any one of which could potentially lead to the spacecraft’s destruction.
“Traveling as fast as Mach 2.5 (860 m/s) at an altitude of 28 kilometers (17 mi), Crew Dragon will ignite its abort thrusters and attempt to escape, the very act of which will likely hammer the spacecraft’s windward surfaces with an extra dozen or so metric tons (~25,000 lb) of aerodynamic pressure. Crew Dragon C205 could thus find itself traveling almost Mach 3 (more than a kilometer per second) moments after separating from Falcon 9, eventually reaching an apogee of almost 75 km (45 mi), after which it will reenter the bulk of Earth’s atmosphere and have to deploy an array of parachutes to ensure a gentle Atlantic Ocean splashdown.”
Teslarati.com — January 13th, 2020
Unfortunately, Crew Dragon escaping a supersonic Falcon 9 also means that that same Falcon 9 – basically a thin, flexible tube designed to be as light as possible – will meet a supersonic blast of air the moment Dragon’s SuperDraco abort thrusters ignite. A bit like if a hurricane on all kinds of meteorological steroids just sort of punched a soda can for fun, that airstream will almost certainly obliterate Falcon 9’s sacrificial upper stage into a sort of aluminum snow, quickly revealing – and likely then destroying – B1046’s carbon fiber interstage.
The rest of the thrice-flown Falcon 9 booster is also liable to break up after that supersonic punch. In fact, SpaceX engineers are so confident in B1046’s imminent demise that the booster will have neither landing legs or grid fins come launch. In a best-case scenario, if, against all odds, B1046 survives Dragon’s escape, the intact booster will subsequently impact the Atlantic Ocean at terminal velocity and become a nice, artificial reef off the coast of Florida. Stay tuned for updates from Teslarati and photographers Jamie Groh and Richard Angle as Falcon 9 B1046’s demise inches ever closer.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
