News
SpaceX completes Falcon 9 test fire, space station supply mission up next
After almost exactly 15 months of dormancy, SpaceX’s Launch Complex 40 (LC-40) came to life with the roar of nine Merlin 1D rocket engines as Falcon 9 1035 conducted its second pre-launch static fire in preparation for the company’s 13th Commercial Resupply Services mission, CRS-13. Previously tasked with the launch of the CRS-11 Cargo Dragon, the booster completed its mission and returned safely to Landing Zone-1 (LZ-1) on June 3 2017. The path towards LC-40’s reactivation has delayed the launch approximately one week, but December 6th’s successful static fire bodes well for the current launch date, 11:46 AM on December 12.
Static fire test of Falcon 9 complete—targeting launch of CRS-13 on December 12 from Pad 40, followed by launch of Zuma from Pad 40 in early January.
— SpaceX (@SpaceX) December 6, 2017
On September 6 2016, LC-40 was effectively destroyed over the course of the Amos-6 failure. In months that followed, SpaceX reactivated LC-39A in order to continue chipping away at the company’s launch manifest, but also began the slow process of damage assessment and reconstruction of LC-40. It is safe to assume that almost every single component of the ground support equipment (GSE) was completely replaced, and interviews with Cape Canaveral’s 45th Space Wing commander suggest that SpaceX went further still, transforming the painful situation into an opportunity.
In an exclusive and frank conversation between Brig. Gen. Wayne Monteith and Florida Today’s Emre Kelly, the commander suggested that extensive design changes and additional hardening measures implemented during reconstruction are expected to make LC-40 exceptionally resilient to the rigors of rocket launches. Most tellingly, if perhaps overly optimistic, Monteith estimated that a second vehicle failure on the order of Amos-6 might only take two months to recover from, compared to the 15 months that followed Amos-6. He attributed this claim to GSE that is now largely buried underground, theoretically protecting the vast apparatus of hand-welded piping necessary to fuel the Falcon 9 launch vehicle. The replacement Transporter/Erector/Launcher (TEL) tasked with supporting Falcon 9 during integration and launch also appears to have been modernized, and will likely end up looking quite similar to the monolithic white TEL that resides at LC-39A.
Rocket and spacecraft for CRS-13 are flight-proven. Falcon 9’s first stage previously launched SpaceX’s eleventh resupply mission for @NASA, and Dragon flew to the @Space_Station in support of our sixth cargo resupply mission. pic.twitter.com/RY4F2TrWO2
— SpaceX (@SpaceX) December 6, 2017
With CRS-13’s static fire now complete, the mission is set to become the fifth operational reuse of a flight-proven Falcon 9 booster in 2017, thanks to NASA’s unusually rapid acceptance of the new practice. Further still, if Iridium-4’s December 22 launch date holds, and it does look to be stable for the moment, SpaceX will rather incredibly have conducted five commercial reuses of a Falcon 9 in its first year of operations, meaning that one third of SpaceX’s 2017 missions will have launched aboard flight-proven boosters. Also impressive is SpaceX’s full-stop move towards the reuse of Cargo Dragon capsules, and the company stated over the summer that it was hoping to almost completely redirect Cargo Dragon’s manufacturing facilities towards Dragon 2, also known as Crew Dragon. This was most recently reiterated several months ago and is presumed to still be the company’s goal moving forward, and CRS-12 is believed to have been the last “new” Cargo Dragon that will fly. CRS-13’s Dragon previously flew the CRS-6 mission in April 2015.

Photos shared privately with the author show CRS-13’s Falcon 9 to be covered in a graceful layer of soot from its previous recovery, similar in appearance to Falcon 9 1021 seen above. (Instagram/bambi_mydear)
In a December 6 tweet, SpaceX further confirmed that the deeply secretive Zuma mission, previously delayed from an early-November launch as a result of concerns about fairing defects, has now been moved from LC-39A to LC-40 and is understood to be targeting January 4 2018. This will give SpaceX approximately three weeks after the launch of CRS-13 to verify that everything is functioning nominally in what is essentially a new pad.
Meanwhile, with Zuma now officially moved to 40, LC-39A is completely free from routine operations, meaning that SpaceX’s ground crew can now work at will to ready the pad for the inaugural launch of Falcon Heavy, now aiming for early 2018. Aside from Falcon Heavy, recent FCC filings point to two additional SpaceX launches aiming for January, although slips are probable in light of CRS-13’s minor delays. Regardless, December and January are likely to be thrilling months for followers of the intrepid space exploration outfit.
News
Tesla Full Self-Driving lands in a new country, its 7th
Tesla Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
Elon Musk
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
News
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below: