Connect with us

News

SpaceX to launch secret “Zuma” payload same day as Tesla Semi event

SpaceX Falcon 9 at Cape Canaveral, FL [Tom Cross/Teslarati]

Published

on

SpaceX has completed preparations and is ready to launch the highly secretive “Zuma” satellite(s) at 5pm/8pm PST/EST on Thursday, November 16th, the same day Tesla will be holding its semi-truck unveiling event.

Updated: SpaceX has rescheduled the Zuma mission.

The Zuma launch campaign has been veiled in an extraordinary level of secrecy for SpaceX and the US launch industry in general, and this has piqued the interest of many.

Advertisement
-->

In the last decade or two, the United States military apparatus has launched many dozens of satellites, and secrecy on the order of Zuma is unusual to say the least. Missions for the National Reconnaissance Office (NRO) typically feature some level of media presence and have developed a community of fans in the age of social media, taking advantage of cartoonish mission logos that can often be entertaining, if not vaguely disturbing.

 

Some of the more ‘unique’ NROL logos in recent years. (NRO)

However, no federal agency has yet to announce involvement in Zuma. The full extent of public information available can be found in a handful of tweets, with drastically less official info available from a leaky source on Reddit. Thus far, Northrop Grumman is known to have at least procured Zuma’s launch from SpaceX, and the same statement indirectly suggested that Zuma was in fact a government-related mission. NRO is the obvious option, with the Air Force or another branch of the US military or intelligence apparatus also a distinct possibility. It is entirely possible that the nature and parent of the mission will remain secret for the indefinite future, even after its launch.

Nevertheless, a handful of details allow us to speculate in greater detail. In May 2017, SpaceX launched NROL-76, a Department of Defense satellite that was intriguingly observed to have made very close passes to the International Space Station, far too close to have been a coincidence. Based on Notices to Airmen (NOTAMs) filed with the FAA and discussed earlier this week, it appears Zuma may be placed in an orbit very similar to that of NROL-76, suggesting that Zuma could be an iteration on NROL-76’s supposed orbit-to-orbit data gathering capabilities. This time, however, agency involvement has been completely shadowed. A blank fairing, sans any NROL-reminiscent logo, will be the tell-tale sign come tomorrow, when Teslarati’s launch photographer Tom Cross arrives at Kennedy Space Center for camera setup.

Advertisement
-->

Meanwhile, as has become shockingly routine, SpaceX’s Falcon 9 first stage, core 1043, will conduct a Return to Launch Site (RTLS), landing at LZ-1 just a few miles from its launch pad. Like NROL-76, we can expect live coverage of the second stage and payload to end immediately after stage separation; bittersweet but esoteric fans, but likely to result in a unique focus on the stage returning to Earth.

On the horizon

Possibly more exciting than the launch itself, Zuma is expected to be the last launch from SpaceX’s Kennedy Space Center LC-39A facilities until Falcon Heavy, currently aiming for an inaugural flight around December 29th. After a solid year of repairs and refurbishment, SpaceX’s LC-40 launch pad is anticipating a return to flight operations with the CRS-13 Cargo Dragon mission on December 4th. Located within the Cape Canaveral Air Force Station just a few miles south of LC-39A, LC-40 suffered widespread damage after a Falcon 9 catastrophically failed while preparing for a static fire test on the pad.

Despite the tragic loss of vehicle and the Amos-6 payload, SpaceX has maintained a strong relationship with the owner, Spacecom, and was recently chosen for both a contractual reflight in 2019 and an additional launch in 2020.

Advertisement
-->

SpaceX has also made great strides since returning to flight after Amos-6 in January 2017, and has enjoyed a truly groundbreaking year of incredible progress towards the goal of rapid reusability. Quite fittingly, LC-40 is expected to return to action while hosting yet another commercial reuse of a Falcon 9 first stage, this time with the hugely significant approval of NASA. The space agency has yet to make this decision resoundingly public, but respected industry insider NASASpaceflight.com has stated that it is all but in stone at this point in time. In a sense, the disaster that severely damaged LC-40 acted as a since-heeded wake-up call for SpaceX, and the venerable pad will rise from those ashes into a new era of reusable rocketry, led wholeheartedly by SpaceX.

Be sure to follow our Instagram stories and see live action directly from the launch site at the Kennedy Space Center!

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Tesla CEO Elon Musk teases insane capabilities of next major FSD update

Published

on

Credit: Tesla China/Weibo

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.”

Advertisement
-->

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.

Advertisement
-->

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.

Continue Reading

News

Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad

Published

on

Credit: Teslarati

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.

Advertisement
-->

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.

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.

Advertisement
-->

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.

However, this was truly my only complaint about v14.2.

You can check out our full 62-minute ride-along below:

Advertisement
-->
Continue Reading

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. 

Published

on

Credit: SpaceX/X

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.

Advertisement
-->
Continue Reading