News
SpaceX’s flight-proven Falcon 9 and drone ship fleet ready for duo of launches
SpaceX is gearing up for a duo of flight-proven Falcon 9 launches and drone ship landings on both coasts of the United States, set for liftoff from Cape Canaveral’s Kennedy Space Center and Vandenberg Air Force Base no earlier than (NET) November 15th and 19th, respectively.
#SpaceXArmada: Moments ago, outbound tugboat Hawk with droneship OCISLY in tow in @PortCanaveral. Destination: Booster core landing/recovery LZ of Thursday's #Eshail2 launch, approx 408 mi E of @NASAKennedy. pic.twitter.com/n5FvBdIvpt
— Cowboy Dan (@CowboyDanPaasch) November 12, 2018
East Coast activities
On the East Coast, drone ship Of Course I Still Love You departed from Port Canaveral late last night (Nov 11) as Falcon 9 B1047 rolled onto Pad 39A for a preflight static fire test, where the rocket will be filled with a full complement of fluids (TEA/TEB, helium, nitrogen, oxygen, kerosene) and all nine Merlin 1D engines are ignited in order to replicate the seconds just prior to a real launch. That static fire test was originally expected to occur on November 10 or 11 but has obviously been pushed back a day to Nov. 12, likely meaning that the rocket’s launch – carrying Qatari communications satellite Es’hail-2 – will slip 24 hours to 3:46pm EST (08:46 UTC) on the 16th,
Following the unfortunate loss of Amos-6 during a preflight static fire in September 2016, SpaceX has since made a reasonable move away from performing static fires with payloads integrated atop the rocket, unless the customer specifically requests that it be done that way to save time. As such, Falcon 9 must be brought horizontal, rolled back to the hangar, inspected, and finally have the payload and fairing attached to the rocket, a sensitive process that demands nuance and time. Combined with an analysis of data gathered during the static fire, this process – when all goes as planned – can take at least 48 hours from start to finish, and longer still if any minor off-nominal behavior is observed or the launch customer has additional requirements (typically reserved for NASA and national security-related missions).
-
- B1047 horizontal at Pad 39A, November 11. (Tom Cross)
-
- B1047 made an extraordinary ring vortex rainbow as it smashed through Max Q, the point of highest aerodynamic stress on the rocket. (Tom Cross)
-
- B1046 seen mid-static fire at Pad 39A ahead of Falcon 9 Block 5’s launch debut, May 2018. (Tom Cross)
Because rockets like Falcon 9 are extraordinarily intricate and finely-tuned machines, perfectly nominal launch-related events are few and far between. In reality, the time between static fire rollout and launch readiness is rarely less than three days (72 hours), not including the process of rolling the fully-integrated rocket back out to the pad, aligning and securing the vehicle and transporter-erector (TE) over the flame trench, and finally attaching all umbilical connections and verifying vehicle health. Speaking generally, four to five days is a good rule of thumb for the time it takes to complete Falcon 9’s static fire and return the rocket to the pad after attaching the payload.
Still, it’s always a good sign when a drone ship leaves port, much like OCISLY did on the evening of the 11th. The journey to its destination will take 2-3 days, meaning that the drone ship will be ready to catch Falcon 9 whenever the rocket is ready to launch.
Drone ships and sooty rockets, oh my!
On the West Coast, SpaceX is also getting ready for drone ship Just Read The Instructions (JRTI) to depart Port of San Pedro in anticipation of a presumed sea recovery of Falcon 9 following the NET Nov 19 launch of a multi-satellite rideshare mission known as SSO-A. While SpaceX currently holds two recovery licenses for the booster, one by sea and one at the land-based LZ-4 pad, it’s possible that the company will be forced to use JRTI despite the fact that Falcon 9 will have plenty of propellant left to return itself to the launch site (RTLS). United Launch Alliance’s (ULA) next Delta IV Heavy rocket is currently on-pad with a presumably very expensive National Reconnaissance (NRO) satellite attached roughly 1.5 miles northeast of SpaceX’s LZ-4 – the rest of the gaps are easy enough to fill in.
-
- Falcon 9 Block 5 booster B1046 seen during both of its post-launch landings. (SpaceX/SpaceX)
-
- B1047 completed its first successful launch in July 2018. (Tom Cross)
-
- B1047 seen rolling into 39A’s integration hangar for refurbishment on July 31st. (Reddit – Kent767)
JRTI was spotted by Teslarati photographer Pauline Acalin performing some rare sea trials on November 10 after spending several weeks berthed at port for routine maintenance and deck repairs. Fairing recovery vessel Mr. Steven has also been undergoing some unusual modifications, now proudly sporting what can only be described as a steel horn recently installed on the tip of his bow deck. After sitting out a catch attempt during the launch of SAOCOM 1A to prepare for controlled helicopter drop tests performed over a period of several weeks in October, Mr. Steven will most likely be ready for another stab at operational fairing recovery during SSO-A.
Both rockets – B1047 to the East and (presumed) B1046 to the West – are flight-proven, meaning that they have flown operational orbital missions prior to their upcoming launch attempts, B1047 launched communications satellite Telstar 19V in July 2018, while B1046 has actually performed two successful launches already, Bangabandhu-1 in May and Telkom 4 (Merah Putih) in August.
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
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.
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:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
