News
SpaceX and NASA reaffirm Crew Dragon’s January 2019 launch debut target
After what can only be described as an attempt to sandbag the official launch schedule, NASA administrator James Bridenstine remains alone in his public implication that the date for SpaceX’s first Crew Dragon test flight (DM-1) is so uncertain that “the first half of 2019” was the closest he would get to an estimate.
Such an uncertain estimate would normally be par for the course of NASA’s Commercial Crew Program (CCP), but the fact remains that SpaceX and NASA have recently filed for and received specific launch date allotments for Crew Dragon’s DM-1 launch, dates little more than 4-6 weeks away from today.
At the NAC HEO meeting, Bill Gerstenmaier says the SpaceX Demo-1 mission is planned “towards the end of January.”
— Jeff Foust (@jeff_foust) December 6, 2018
As such, the fact that NASA associate administrator Bill Gerstenmaier – a critical hands-on leader of NASA’s commercial and exploration programs – specifically stated that NASA and SpaceX are targeting DM-1’s launch in January is an unusually stark indication that the two senior NASA officials are not reading from the same script, so to speak. The reasons for the dramatic differences in official statements separated by just one week are hard to parse and would inevitably tread into waters of pure speculation and political machinations.
What is far more important is that Gerstenmaier – backed up by Phil McCalister, NASA Director of Commercial Spaceflight – reaffirmed that NASA is planning for the first orbital, uncrewed launch of SpaceX’s Crew Dragon as early as January 2019, albeit with a slight 10-day slip since the last specific launch date (January 7) was announced.
Speaking before and after Falcon 9’s recent launch of Cargo Dragon (CRS-16) on December 5th, SpaceX VP of Launch and Build Reliability Hans Koenigsmann added yet another voice to the chorus, stating that he and SpaceX were extremely confident that all the physical hardware and software aspects of Crew Dragon would be ready to launch no later than January 7th.
NASA’s Phil McAlister updates the status of SpaceX’s Demo-1 Crew Dragon spacecraft, and says the company aims to have all hardware ready by Dec. 20, then will stand down for the holidays before resuming launch preps in January. pic.twitter.com/XDubh95PEV
— Stephen Clark (@StephenClark1) December 6, 2018
Why so uncertain?
It’s impossible to fully delve into the complex political and bureaucratic intricacies of modern NASA, but the uncertainty within NASA and the deltas between NASA and SpaceX’s official statements can generally be explained by the simple fact that a number of critical final reviews have yet to be completed, reviews that will offer the final determination of when or if Falcon 9 and Crew Dragon are ready to launch.
Depending on the results of those readiness reviews, DM-1 could be given the go-ahead to launch in January or it could be delayed six months because NASA wants SpaceX to change a number of critical spacecraft systems, two extreme sides of what can be best described as a spectrum of possibilities.
In other words, SpaceX’s Koenigsmann and NASA’s Gerstenmaier and McCalister have since implied that they are confident that those final reviews will look favorably upon launch dates that approximate “ASAP”. Bridenstine, while technically the head of NASA, can thus be treated as a dissenting or outlier opinion in this case, presumably offering a worst-case-scenario of when SpaceX might be able to launch DM-1 if final reviews go very badly.
-
- SpaceX technicians move the integrated DM-1 Crew Dragon during a vacuum chamber test campaign. (SpaceX)
-
- A SpaceX employee works on the Crew Dragon assigned to DM-2, the first launch with astronauts aboard. (SpaceX)
-
- SpaceX installed its Crew Access Arm (CAA) in September 2018. (Tom Cross)
Bridenstine and Koenigsmann’s comments are worth looking at in a bit more depth, subtly but unequivocally pointing to the differences in opinion between NASA and SpaceX that clearly still float just beneath the public surface. Asked about Bridenstine’s suggestion that DM-1 could slip quite a bit, Koenigsmann offered a skeptical but levelheaded response:
“What I could see is a [slip of a] couple of days because of [Space Station] traffic. For example, CRS-16 (Cargo Dragon) is on station at the same time, lots of traffic, lots of crew time requirements, but our target is – at this point in time – mid-January, and we’re pushing as hard and [as diligently] as we can for this particular launch.”
In fact, it appears that NASA and SpaceX concluded, around the same point in time, that a new target of January 17th was preferable to account for the logistical scheduling concerns highlighted by Hans in the above quote, allowing 10 extra days for the International Space Station (ISS) crew to complete other spacecraft operations before Crew Dragon’s planned arrival.
Even more intriguingly, local reporter Ken Kremer followed up with a question specifical triggered by Bridenstine’s suggestion (according to USA Today) that “challenges” with Crew Dragon’s landing parachutes were a leading factor in the unlikelihood of a January launch. Hans responded in his usual deadpan style:
“No; we’re working through issues, obviously, I mean every launch has things that we work through to make sure they work fine. [Dragon 2’s parachutes] actually have more redundancy than those on Dragon 1 and they are also [structurally] reinforced on Demo-1, so pretty sure [they’re] gonna be successful.”
Now we wait.
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
