News
Tesla’s software fixes, the NHTSA’s status quo, and an impending need for updated recall terminologies
It is no secret that Tesla is a popular topic, so much so that the coverage around the company is immense. Couple this with CEO Elon Musk’s rockstar persona and you get a company whose vehicles are looked at under a microscope constantly. It might feel unfair for some, but it’s just the way it is. Tesla — by simply being Tesla — is newsworthy.
Tesla’s newsworthiness is a double-edged sword. A look at the coverage for the company’s vehicle recalls from the NHTSA would prove this point. So notable is Tesla’s news coverage that a mainstream newsreader would likely get the impression that Teslas get recalls frequently. The opposite is true. As evidenced by Reuters in the graphic below, data from January 1, 2020, through February 17, 2022, shows that Tesla actually recalls its vehicles less frequently than some of the market’s leading automakers. Tesla is also the only carmaker performing a large share of its vehicle recalls through over-the-air software updates.

Tesla currently handles the majority of the industry’s remote software recalls, but it would soon not be the only one. New electric vehicle makers have used the idea of software updates as a means to promote their EVs’ capabilities. Rivian has performed OTA updates to its R1 vehicles, and those cars are only starting customer deliveries. Lucid is the same with its Air sedan, with the company rolling out features like Automatic Emergency Braking, Cross-Traffic Protection, Lane Departure Protection, Traffic Drive-Off Alert, and other features earlier this month through a software update. Ford has been rolling out updates called “Power-Ups” to the Mustang Mach-E as well.
Considering that software-based fixes are only bound to get more widespread over the coming years, one must then ask the question: Should software-based over-the-air fixes be dubbed and classified with the same terminologies as physical recalls, which typically involve the replacement of vehicle hardware?
A Vastly Different “Recall” Experience
Any car owner has likely experienced a recall for their vehicle at some point in their driving life. And more likely than not, one’s experience is probably not that pleasant. I certainly count myself among drivers who look at vehicle recalls with trepidation. My current vehicle, a Japanese-made van, was part of a minor fuel pump recall a couple of years ago, and even addressing that took a whole day out of my weekend. The dealer was overwhelmed with the number of cars it was fixing that day, and tempers among owners were flaring by the hour — all for a simple fuel pump replacement. I’ve been told that my experiences with vehicle recalls are not that unique.
In comparison, a software-based fix, such as the disabling of FSD Beta’s “rolling stops” feature, only required affected vehicles to be connected to the internet. There was no dealer visit, no forms to fill out, and no staff to argue with. The car was connected to the internet, a software fix was implemented, and the issue was resolved. One can argue that Tesla’s software fix to disable FSD Beta’s “rolling stops” feature was safety-related, and that’s true. But one could also argue that at least from a driver’s point of view, the experience related to software and hardware-based recalls is vastly different.
The Status Quo
Despite the different experiences involved when software and hardware-based vehicle recalls are addressed, it appears that the National Highway Traffic Safety Administration (NHTSA) will, at least for now, keep the status quo. Teslarati reached out to the NHTSA to inquire if it was considering the adoption of updated terminologies for cars whose fixes are completed through OTA software updates, but the agency suggested that this would likely not be the case, at least for now. According to the NHTSA, vehicle manufacturers must initiate a recall for any repair that remedies a safety risk, regardless of whether the issue is fixed by software update or by hardware replacement.
“The National Highway Traffic Safety Administration is committed to ensuring the highest safety standards on the nation’s roadways. NHTSA is empowered with robust tools and authorities to protect the public, to investigate potential safety issues, and to compel recalls when it finds evidence of noncompliance or an unreasonable risk to safety. Manufacturers are required to initiate a recall for any repair, including a software update, that remedies an unreasonable risk to safety. NHTSA recalls can include any required repair, which includes a software update, to remedy a potential safety risk. Manufacturers are also required to submit any communications to owners, dealers, and others about any software updates that address a defect, whether it is safety-related or not,” the NHTSA stated.
Product recall specialist and associate professor at the Indiana University Kelley School of Business Professor George Ball told Teslarati that while the NHTSA’s use of similar terminologies for software and hardware-based recalls is “definitely an example of regulators and industry moving at a different pace on technology,” the agency’s hesitation in adopting new terminologies for OTA fixes is understandable. Professor Ball further explained that using terms such as “soft recall” to refer to software-based vehicle fixes might imply a reduced level of risk, and this is something that the NHTSA would likely be unwilling to do.
“I believe NHTSA would resist ‘soft recall’ terminology because it implies a reduced level of customer hazard and allows the firm to be under less scrutiny by the press and public for quality corrections. While some updates are minor, some of the Tesla software upgrades are actually quite serious, and if not done, can allow a harmful defect to persist,” the recall specialist said.
But while the NHTSA’s stance on recall terminologies is completely understandable, one cannot deny the fact that the issues covered by vehicle recalls have a very wide range of risks. Take Tesla’s recall for 817,143 vehicles, which was announced earlier this month, for example. The recall was initiated since a software error may prevent a warning chime from activating even if drivers do not have their seat belts on. From a layman’s perspective, this recall seems grave as it affects over 800,000 Teslas on the road today. However, the issue was simply addressed through firmware release 2021.43.101.1 and later, which included a remedy for the seat belt chime error.
Compare this with General Motors’ recall last year of 400,000 pickup trucks in the US. Granted, it only affected about half as many vehicles as Tesla’s seat belt chime recall, but its hardware-based nature suggested that the risk presented by the issue was great. The recall covered certain 2015 and 2016 Chevrolet and GMC Sierra 1500, 2500, and 3500 trucks, and it involved a faulty airbag inflator that may rupture without warning. To fix the issue, owners of the affected trucks were required to head to a dealer so that they could get their airbag modules replaced. Since parts were in short supply last year, however, owners were notified with a letter to inform them when their trucks’ replacement parts were available.
What Can Be Done
While the NHTSA will likely continue to maintain the status quo with its recall terminologies for the foreseeable future, Professor Ball told Teslarati that the agency can actually implement some adjustments now that can make distinguishing safety fixes and issues clearer. This would likely be extremely important in the near future as more connected cars are rolled out and software updates become the norm.
“If I were to provide advice to the NHTSA, I would recommend that they get out ahead of this issue before every car maker starts updating cars like Tesla. One way to do it is to require the automaker to send all auto updates to NHTSA when pushed out, and to classify updates as ‘minor’ or ‘major.’ Any major update that impacts customer safety would be classified as a recall. Automakers won’t like this, but it will help keep the safety fixes transparent for all, especially consumers. By sending all updates to NHSTA, the agency could assign qualified people to audit the classifications assigned by the manufacturer, to ensure they are making good decisions there.
“I think any language that de-emphasizes the importance of a safety recall is not likely to be supported by NHTSA, and it doesn’t likely help customer safety. A clear distinction needs to be made between minor updates and major updates that influence safety. Those major updates should be classified as a recall, and NHTSA needs to get their arms around these updates and keep on top of them soon, or they will fall way behind the industry,” the recall specialist said.
Recalls can affect the perception of a company to the public. Software fixes should be one of the factors that are considered an edge for automakers like Tesla, not the other way around. Gary Black, Managing Partner of The Future Fund LLC, explained this from the point of view of a Tesla investor. “Since every NHTSA recall so far has been quickly solvable via Tesla OTA updates, ‘recalls’ are noise to most investors. Tesla’s huge software edge highlights one of the key advantages of owning Tesla over every other EV manufacturer,” the Wall Street veteran told Teslarati.
OTA updates, including those related to vehicle safety, are coming. With automakers like Ford joining the group of carmakers embracing OTA updates, software-based fixes are inevitable. Ultimately, I am inclined to agree with the recall specialist. By refusing to adapt to the advent of software-based vehicle fixes, the NHTSA may risk being left behind by the automotive industry. And that’s a scenario that I believe no automaker — or government agency for that matter — would prefer.
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
Elon Musk
SpaceX’s Starship FL launch site will witness scenes once reserved for sci-fi films
A Starship that launches from the Florida site could touch down on the same site years later.
The Department of the Air Force (DAF) has released its Final Environmental Impact Statement for SpaceX’s efforts to launch and land Starship and its Super Heavy booster at Cape Canaveral Space Force Station’s SLC-37.
According to the Impact Statement, Starship could launch up to 76 times per year on the site, with Super Heavy boosters returning within minutes of liftoff and Starship upper stages landing back on the same pad in a timeframe that was once only possible in sci-fi movies.
Booster in Minutes, Ship in (possibly) years
The EIS explicitly referenced a never-before-seen operational concept: Super Heavy boosters will launch, reach orbit, and be caught by the tower chopsticks roughly seven minutes after liftoff. Meanwhile, the Starship upper stage will complete its mission, whether a short orbital test, lunar landing, or a multi-year Mars cargo run, and return to the exact same SLC-37 pad upon mission completion.
“The Super Heavy booster landings would occur within a few minutes of launch, while the Starship landings would occur upon completion of the Starship missions, which could last hours or years,” the EIS read.
This means a Starship that departs the Florida site in, say, 2027, could touch down on the same site in 2030 or later, right beside a brand-new stack preparing for its own journey, as noted in a Talk Of Titusville report. The 214-page document treats these multi-year round trips as standard procedure, effectively turning the location into one of the world’s first true interplanetary spaceports.
Noise and emissions flagged but deemed manageable
While the project received a clean bill of health overall, the EIS identified two areas requiring ongoing mitigation. Sonic booms from Super Heavy booster and Starship returns will cause significant community annoyance” particularly during nighttime operations, though structural damage is not expected. Nitrogen oxide emissions during launches will also exceed federal de minimis thresholds, prompting an adaptive management plan with real-time monitoring.
Other impacts, such as traffic, wildlife (including southeastern beach mouse and Florida scrub-jay), wetlands, and historic sites, were deemed manageable under existing permits and mitigation strategies. The Air Force is expected to issue its Record of Decision within weeks, followed by FAA concurrence, setting the stage for rapid redevelopment of the former site into a dual-tower Starship complex.
SpaceX Starship Environmental Impact Statement by Simon Alvarez
News
Tesla Full Self-Driving (FSD) testing gains major ground in Spain
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Tesla’s Full Self-Driving (Supervised) program is accelerating across Europe, with Spain emerging as a key testing hub under the country’s new ES-AV framework program.
Based on information posted by the Dirección General de Tráfico (DGT), it appears that Tesla is already busy testing FSD in the country.
Spain’s ES-AV framework
Spain’s DGT launched the ES-AV Program in July 2025 to standardize testing for automated vehicles from prototypes to pre-homologation stages. The DGT described the purpose of the program on its official website.
“The program is designed to complement and enhance oversight, regulation, research, and transparency efforts, as well as to support innovation and advancements in automotive technology and industry. This framework also aims to capitalize on the opportunity to position Spain as a pioneer and leader in automated vehicle technology, seeking to provide solutions that help overcome or alleviate certain shortcomings or negative externalities of the current transportation system,” the DGT wrote.
The program identifies three testing phases based on technological maturity and the scope of a company’s operations. Each phase has a set of minimum eligibility requirements, and applicants must indicate which phase they wish to participate in, at least based on their specific technological development.

Tesla FSD tests
As noted by Tesla watcher Kees Roelandschap on X, the DGT’s new framework effectively gives the green flight for nationwide FSD testing. So far, Tesla Spain has a total of 19 vehicles authorized to test FSD on the country’s roads, though it would not be surprising if this fleet grows in the coming months.
The start date for the program is listed at November 27, 2025 to November 26, 2027. The DGT also noted that unlimited FSD tests could be done across Spain on any national route. And since Tesla is already in Phase 3 of the ES-AV Program, onboard safety operators are optional. Remote monitoring would also be allowed.
Tesla’s FSD tests in Spain could help the company gain a lot of real-world data on the country’s roads. Considering the scope of tests that are allowed for the electric vehicle maker, it seems like Spain would be one of the European countries that would be friendly to FSD’s operations. So far, Tesla’s FSD push in Europe is notable, with the company holding FSD demonstrations in Germany, France, and Italy. Tesla is also pushing for national approval in the Netherlands in early 2026.
News
Tesla FSD V14.2.1 is earning rave reviews from users in diverse conditions
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise.
Tesla’s Full Self-Driving (Supervised) software continues its rapid evolution, with the latest V14.2.1 update drawing widespread praise for its smoother performance and smarter decision-making.
Videos and firsthand accounts from Tesla owners highlight V14.2.1 as an update that improves navigation responsiveness, sign recognition, and overall fluidity, among other things. Some drivers have even described it as “more alive than ever,” hinting at the system eventually feeling “sentient,” as Elon Musk has predicted.
FSD V14.2.1 first impressions
Early adopters are buzzing about how V14.2.1 feels less intrusive while staying vigilant. In a post shared on X, Tesla owner @LactoseLunatic described the update as a “huge leap forward,” adding that the system remains “incredibly assertive but still safe.”
Another Tesla driver, Devin Olsenn, who logged ~600 km on V14.2.1, reported no safety disengagements, with the car feeling “more alive than ever.” The Tesla owner noted that his wife now defaults to using FSD V14, as the system is already very smooth and refined.
Adverse weather and regulatory zones are testing grounds where V14.2.1 shines, at least according to testers in snow areas. Tesla watcher Sawyer Merritt shared a video of his first snowy drive on unplowed rural roads in New Hampshire, where FSD did great and erred on the side of caution. As per Merritt, FSD V14.2.1 was “extra cautious” but it performed well overall.
Sign recognition and freeway prowess
Sign recognition also seemed to show improvements with FSD V14.2.1. Longtime FSD tester Chuck Cook highlighted a clip from his upcoming first-impressions video, showcasing improved school zone behavior. “I think it read the signs better,” he observed, though in standard mode, it didn’t fully drop to 15 mph within the short timeframe. This nuance points to V14.2.1’s growing awareness of temporal rules, a step toward fewer false positives in dynamic environments.
FSD V14.2.1 also seems to excel in high-stress highway scenarios. Fellow FSD tester @BLKMDL3 posted a video of FSD V14.2.1 managing a multi-lane freeway closure due to a police chase-related accident. “Perfectly handles all lanes of the freeway merging into one,” the Tesla owner noted in his post on X.
FSD V14.2.1 was released on Thanksgiving, much to the pleasant surprise of Tesla owners. The update’s release notes are almost identical to the system’s previous iteration, save for one line item read, “Camera visibility can lead to increased attention monitoring sensitivity.”
