News
SpaceX Falcon Heavy testing delayed after government shutdown
As the U.S. Senate’s majority party searches for ten additional votes in order to end a federal government shutdown that began late Saturday, all “non-essential” activities at the country’s numerous government-operated space launch facilities have ground to an immediate halt and will remain in limbo until a funding bill compromise is hammered out.
While SpaceX is a wholly private space launch company, it relies almost unilaterally upon launch support and range expertise provided by NASA and the US Air Force, both in Cape Canaveral, FL and Vandenberg, CA. Sadly, the Air Force personnel SpaceX depend upon to conduct launches, static fires, and other ignition tests at its launch pads are not considered “essential” under regulations that prevent the federal government from coming to a complete halt in the event of a funding-related shutdown.
Unfortunately, a budget agreement wasn't reached, resulting in a gov't shutdown. This will unfortunately disrupt the lives and operations here at Patrick AFB. Go to https://t.co/yvmNBH1LMy for info on the current shutdown, impact on base resources, & financial resource options.
— Space Launch Delta 45 (@SLDelta45) January 20, 2018
SpaceX did appear to complete the most thorough round of Falcon Heavy testing yet late Saturday evening, the US Senate’s failure to either pass a continuing resolution or a new funding bill for the fiscal year led to a complete federal government shutdown soon after. As a result, nearly all of the US Air Force’s 45th Space Wing – a crucial backbone of East coast range and launch operations – was furloughed indefinitely, pending new funding from Congress. SpaceX had previously requested a new static fire date for Falcon Heavy on Monday, January 22 (today), a date that is now clearly going to move right for at least as long as the government lacks funding for basic launch operations.
Thankfully, activities like the extensive propellant loading tests that occurred on Saturday night do not technically require range support, so long as no engine ignition or static fire components are included. In the event of a catastrophic failure, the government-run range would be tasked with ensuring the safety of those in the vicinity and coordinating the emergency response that would immediately follow. This policy is brought somewhat into question by the failure of Amos-6 – although that Falcon 9 was being prepared for a static fire test, its highly-destructive failure is understood to have occurred at least five or more minutes before the planned point of ignition. Nevertheless, SpaceX will be able to continue some level of testing with Falcon Heavy, if needed.
Elsewhere, instability
While SpaceX’s Falcon Heavy has undoubtedly garnered magnitudes more eyeballs than the company’s Falcon 9 activities, the government shutdown could be far more consequential for SpaceX’s customers if it cannot be halted within a handful of days. A federal shutdown lasting several days is a hugely disruptive and damaging event on its own, lack of range support on the East coast could quickly begin to eat into SpaceX’s GovSat-1 preparations, the launch of which is targeting NET late January/January 30. For GovSat-1’s flight-proven booster, a static fire at the launch site is unlikely to be bypassed (SpaceX has never skipped a prelaunch static fire), and would typically occur no fewer than four or five days before launch. As a result, in the somewhat unlikely event that the shutdown stretches beyond the next several days, SpaceX customers SES and GovSat could see their launch delayed, an event that would likely bring financial consequences to the public-private satellite venture.
Looking slightly farther into the future, SpaceX’s flight-proven launch of PAZ and two of its own prototype communications satellites is just about two weeks away from its own static fire test, this time at the West Coast’s Vandenberg Air Force Base. Such an extended shutdown would be utterly unprecedented, but if 2017 and 2018 have done anything at all, they’ve tempered tendencies towards knee-jerk claims of “that’ll never happen!”
- A panorama of LC-39A in November 2017. (Tom Cross/Teslarati)
- SpaceX’s Vandenberg launch complex, SLC-4E, depends upon an Air Force range to operate. (SpaceX)
- LC-40, located in Cape Canaveral Air Force Station, is SpaceX’s second pad. (Tom Cross)
Here’s to hoping that Congress can get their act together and return to those they represent the bare minimum of federal stability, for both federal employees and those that depend upon them.
Update: After a solid two days of shutdown, the Senate has apparently reached an agreement to pass a continuing resolution that will maintain funding for another three weeks, after which a new FY2018 budget must be passed to avoid another shutdown. While this thankfully means that the impact to the Space Coast and the Air Force’s 45th Space Wing should be relatively small, I have left my above thoughts on the potential impacts of a longer shutdown untouched for posterity.
Senate has voted on an amended bill to fund U.S. government for 3 weeks. Bill now heads back to the House for debate & vote. If it passes the House without changes, the President then needs to sign it into law. Once all those things happen, the government reopens. Then… 1/2
— Chris G (@ChrisG_SpX) January 22, 2018
Follow along live as launch photographer Tom Cross and I cover these exciting proceedings as close to live as possible.
Teslarati – Instagram – Twitter
Tom Cross – Instagram
Eric Ralph – Twitter
News
Tesla Robotaxi ride-hailing without a Safety Monitor proves to be difficult
Tesla Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.
Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.
BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor
Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.
However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.
He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:
Wow just wow!
It’s 8:30PM, 29° out ice storm hailing & Tesla Robotaxi service has turned back on!
Waymo is offline & vast majority of humans are home in the storm
Ride 38 was still supervised but by far most impressive yet pic.twitter.com/1aUnJkcYm8
— David Moss (@DavidMoss) January 25, 2026
Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”
This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.
However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.
News
Tesla gives its biggest hint that Full Self-Driving in Europe is imminent
Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.
Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”
FSD now shows a new message when approaching an international border crossing.
Stayed engaged the whole way as we crossed the border and worked great in Mexico! pic.twitter.com/bDzyLnyq0g
— Zack (@BLKMDL3) January 26, 2026
Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.
This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.
Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.
This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.
Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.
Tesla Europe builds momentum with expanding FSD demos and regional launches
Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.
Elon Musk
SpaceX Starship V3 gets launch date update from Elon Musk
The first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
Elon Musk has announced that SpaceX’s next Starship launch, Flight 12, is expected in about six weeks. This suggests that the first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
In a post on X, Elon Musk stated that the next Starship launch is in six weeks. He accompanied his announcement with a photo that seemed to have been taken when Starship’s upper stage was just about to separate from the Super Heavy Booster. Musk did not state whether SpaceX will attempt to catch the Super Heavy Booster during the upcoming flight.
The upcoming flight will mark the debut of Starship V3. The upgraded design includes the new Raptor V3 engine, which is expected to have nearly twice the thrust of the original Raptor 1, at a fraction of the cost and with significantly reduced weight. The Starship V3 platform is also expected to be optimized for manufacturability.
The Starship V3 Flight 12 launch timeline comes as SpaceX pursues an aggressive development cadence for the fully reusable launch system. Previous iterations of Starship have racked up a mixed but notable string of test flights, including multiple integrated flight tests in 2025.
Interestingly enough, SpaceX has teased an aggressive timeframe for Starship V3’s first flight. Way back in late November, SpaceX noted on X that it will be aiming to launch Starship V3’s maiden flight in the first quarter of 2026. This was despite setbacks like a structural anomaly on the first V3 booster during ground testing.
“Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X.


