News
SpaceX Falcon 9 booster spied on highway as triple-satellite launch moves right
A SpaceX Falcon 9 booster was spotted heading north from the company’s Hawthorne, California factory on January 22nd, signifying a likely shipment of the flight-proven rocket that will help launch Canada’s trio of Radarsat Constellation Mission satellites.
Delayed from mid-February to early March 2019 after an unplanned landing anomaly damaged the Falcon 9 originally assigned to the mission, the shipment of a different booster to Vandenberg Air Force Base (VAFB) helps to narrow down the rocket now likeliest to launch the Canadian Space Agency’s (CSA) radar satellite constellation.
https://twitter.com/GoForStaging/status/1088174203298230272
Do the Booster Shuffle!
Thanks to a hydraulic pump failure that led Falcon 9 B1050 to land (albeit softly and in one piece) in the Atlantic Ocean last December, the imminent launch of two booster-dense Falcon Heavy missions, and the thus far schedule-shy orbital launch debut of Crew Dragon, SpaceX’s fleet of available boosters – all flight-proven – can be succinctly summarized as “B1046 thru B1049”.
B1050’s future is uncertain after suffering a smashed interstage and soaking in salt water for several days, while B1051 is definitively assigned to Crew Dragon’s orbital launch debut, known as Demo-1 (DM-1). Falcon 9 B1052 and B1053 are unknown quantities and B1054 was expended after a high-value US Air Force launch, also SpaceX’s final mission of 2018. It’s probably safe to bet that B1052, B1053, and B1055 will be the next three boosters to support a Falcon Heavy launch (or two), currently NET March and April 2019. All three of those Falcon Heavy (FH) boosters have completed static fire tests in Texas and both side boosters arrived at SpaceX’s Florida facilities within the last ~6 weeks.
-
- A Falcon Heavy side booster was spotted eastbound in Arizona on November 10th. (Reddit – beast-sam)
-
- The second (and third) flight of Falcon Heavy is even closer to reality as the first new side booster heads to Florida after finishing static fire tests in Texas. (Reddit /u/e32revelry)
-
- Reddit user wedatsaints captured this photo of the second Falcon Heavy side booster traveling through Mississippi on Jan 16. (Reddit /u/wedatsaints)
-
- SpaceX Facebook group member Joshua Murrah captured the second Falcon Heavy side booster to arrive in Florida in the last month. (Joshua Murrah, 01/17/19)
-
- A booster – likely the next Falcon Heavy center core – was vertical at McGregor’s S1 static fire stand. (Instagram /u/tcryguy)
Assuming that Falcon Heavy Flight 2 and 3 use the same exact boosters, SpaceX production technicians and engineers may already be nearing the completion of another Falcon 9 booster (B1056, presumably) at the Hawthorne factory, although they are likely 1-2 weeks away from that milestone. If, Falcon Heavy Flight 3 (presumed to be the USAF’s STP-2 mission) does not reuse all three first stage boosters from Flight 2 (commercial payload Arabsat 6A), then Hawthorne will have to build, ship, and test anywhere from 1-3 additional boosters between now and April 2019. In the latter scenario, all unflown – mid-build or completed – Falcon boosters would be ‘claimed’ between now and March or April.
Put in another way, short of opting for a delay that could stretch 1-4 months or longer, the Canadian Space Agency (CSA) and Radarsat prime contractor MDA will have to accept one of SpaceX’s flight-proven Falcon 9s.
Falcons on wheels
Thanks to SpaceX’s trusty and well-worn method of using good old trucks and roads to transport Falcon 9 and Heavy boosters, upper stages, fairings, landing legs, and much more cross-country, spaceflight fans have long taken advantage of opportunities – rare and fleeting as they might be – to spot and track SpaceX hardware on public roads. Put simply, a lot of people are excited about SpaceX or are at least familiar and curious enough to know someone to share a photo or observation with. As a result, the community averages dozens of ‘core spottings’ per year. With a little intuition, the process of elimination, a few sources, and some wild guesses, this allows unofficial fans to (very roughly) paint a picture of SpaceX’s fleet of rockets.
-
- Reddit user intamin1 spotted a Falcon 9 booster northbound between Hawthorne and Vandenberg on Jan 22. (Reddit /u/intamin1)
-
- A booster – likely the next Falcon Heavy center core – was vertical at McGregor’s S1 static fire stand. (Instagram /u/tcryguy)
For example, the Falcon 9 spotted in Valencia, CA on January 22nd by Reddit user intamin1 could theoretically be any SpaceX booster currently in existence. By knowing the rough state of SpaceX’s fleet (as described above) and observing that the booster was northbound between Hawthorne, CA (the factory) and Vandenberg Air Force Base (VAFB) on Jan 22, a great deal can be intuited. Bound for SpaceX’s West Coast launch complex (SLC-4), it ought to be flightworthy. Knowing that a Falcon Heavy center booster was on SpaceX’s McGregor, Texas static fire stand on January 10th means that the spotted booster can’t (or at least shouldn’t) be coming from Texas, as Falcon Heavy has no known launches planned from VAFB. The process of testing, inspecting, and preparing Falcon boosters for cross-country shipment is also not easily rushed.
On the East Coast, SpaceX needs to launch communications satellite PSN-6 and Spaceflight rideshare GTO-1 in mid to late February. With no new boosters expected to be easily available for months and PSN-6/GTO-1 already entering into the phases of payload fueling, integration, and fairing encapsulation, it can be all but guaranteed that a flight-proven booster was assigned to the mission months ago and is now nearly ready for its third flight somewhere in Cape Canaveral, FL.
Given that B1046 and B1049 are on the West Coast after conducting launches from VAFB and that B1050 is out of circulation for the time being, only B1047 and B1048 remain (in theory) on the East Coast, both having flown two missions. B1048 was recently spotted and confirmed in photos of SpaceX’s Pad 39A integration hangar, although Falcon 9 B1051 and the first orbit-ready Crew Dragon were the center of attention.
B1047 completed its second launch in mid-November 2018 and returned to one of SpaceX’s Florida hangars for refurbishment around Nov 21. Unless any number of locals and bystanders somehow missed it, neither booster has left the Cape since arriving. Meanwhile, B1048 is currently the best-known candidate at hand for SpaceX’s Crew Dragon In-Flight Abort (IFA) test, expected to occur no earlier than spring 2019 and entirely dependent upon the successful launch, reentry, recovery, and refurbishment of the DM-1 capsule to proceed. As a result, the only booster that is realistically available for PSN-6/GTO-1 is Falcon 9 B1047 for what would be its third launch.
Few of my favorites from today's Pence visit to #SpaceX pad 39A. In first photo, from left to right: Previously flown B1048, booster for DM-1, Crew Dragon for DM-1. Look at the size of that Merlin engine bell.
More photos: https://t.co/6dMbampx2c pic.twitter.com/3KmjVj4Rvf
— Emre Kelly (@EmreKelly) December 18, 2018
Assuming B1048 did not manage to make it from Cape Canaveral to Central California without a single spotting, the only rockets available for the RCM mission are B1046 and B1049. B1049 completed its second launch – Iridium-8 – just weeks ago and returned by drone ship to Port of LA on January 13th, whereas Falcon 9 B1046 – after completing its historic third launch – completed recovery and was snug in a Hawthorne, CA refurbishment bay by December 17th, 2018. Going off of Occam’s Razor, B1046 is the clear victor for the launch of RCM, although a ~60-90-day turnaround for the already thrice-flown booster could be a stretch. B1049, however, would have barely a single month for refurbishment and inspections.
In the last week or two, RCM stakeholders were provided an updated launch target, delaying the mission by approximately two weeks to a window that begins February 28th with the implication being that the launch is now expected NET early March. If that date is recent and from SpaceX, B1046 is the most practical option, with B1049 thus filling its refurbishment bay in Hawthorne, CA around the same day. If a risk of a 30-day or greater delay is tolerable for CSA and MDA, then B1049.3 would likely be a more optimal fit for their risk tolerance profile. Time will tell!
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
