News
SpaceX Texas test HQ fires up a dozen Falcon, Starship rocket engines in six hours
Though it often falls under the radar relative to SpaceX’s high-profile Boca Chica Starship hub, another even more important Texas outpost appears to be busier than ever testing the rocket engines and boosters instrumental to all SpaceX operations.
Famous for occasionally supporting half a dozen or more rocket tests on busy days, SpaceX’s McGregor, Texas facilities showed off exactly that kind of rapid-fire activity on Friday, March 19th, flexing the sheer variety and volume of rocket hardware liable to pass through its gates.
Located on the grounds of a former US military explosives factory, SpaceX’s McGregor, Texas rocket development and test facilities have been testing Falcon, Dragon, and Starship parts and supporting each program’s development for a decade and a half. After being fabricated and assembled in Hawthorne, California, virtually every single active propulsive component SpaceX has ever flown has spent some amount of time in McGregor.
For boosters, every cold gas maneuvering thruster is qualified in Texas before being sent back to Hawthorne for final installation. Each stage’s nine Merlin 1D engines are individually tested in McGregor, shipped back to Hawthorne, installed on a booster, shipped back to McGregor, and static fired as an integrated first stage before SpaceX deems a Falcon 9 or Falcon Heavy core ready for flight. The exact same process (separate engines and thruster qualification followed by integrated vehicle testing) is performed with Falcon upper stages and their Merlin Vacuum engines, as well as all Dragon spacecraft and their Draco (and SuperDraco) thrusters. The same is true for the two Raptor engine variants and cold-gas thrusters that power Starship.
On March 19th, nearly all of those different engines and vehicles – and the separate stands used to test each of them – came together for an exceptionally busy day at McGregor. According to local resident Reagan (@bluemoondance74), who lives within earshot of SpaceX’s extraordinarily busy rocket testing HQ, at least five unique tests were performed in just six hours – all but one of which was squeezed into the last ~125 minutes.
Around 2:40 pm, an unknown test – possibly a Merlin Vacuum (MVac) or Merlin 1D (M1D) engine – kicked off the salvo. Four hours later, SpaceX completed arguably the most significant test of the day, firing up the first Falcon Heavy center core to head to McGregor in almost 24 months. Assuming that static fire was a success, the booster will be inspected, have its tanks cleaned, and be shipped to Florida to complete the first stage of SpaceX’s fourth Falcon Heavy rocket for a launch as early as July.
An hour and a half after the Falcon Heavy center core’s static fire, SpaceX fired up a Raptor engine (either a sea level or vacuum variant), followed by another likely M1D or MVac test just minutes later. Finally, at 8:52 pm, SpaceX ignited a second Raptor engine at an entirely separate vertical test stand (known as the tripod stand) recently modified to support testing Starship engines in a more flight-like configuration. Altogether, assuming no repeated tests, SpaceX effectively tested a booster and 13 (9+4) rocket engines in a little over six hours.
More likely than not, one or both of those Raptors will soon find themselves on a Starship or Super Heavy prototype in Boca Chica. The M1D and/or MVac engines will assuredly find a place on a future Falcon booster or upper stage. The Falcon Heavy center core (B1065 or B1066) is scheduled to launch as early as July 2021 and will be the first of its kind to fly in an intentionally expendable configuration. Another Falcon Heavy center core – possibly B1067 – will likely also find itself in McGregor within the next few months for the rocket’s fifth launch, scheduled no earlier than (NET) October 2021.
All told, SpaceX’s McGregor rocket testing HQ is about as busy as – if not busier than – it’s ever been as the company works towards an unprecedentedly ambitious 48-launch 2021 manifest, builds and flies at least four Dragon spacecraft, and pursues an even more ambitious effort to begin orbital Starship launches this summer. Quieted away in rural Texas, McGregor may largely go unnoticed but its infrastructure remains as integral as ever for virtually every single SpaceX project – past, present, and future.
Elon Musk
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Tesla is planning to unveil the Roadster in late April after years of waiting. But the wait might be worth it, according to Travis Kalanick, the founder of Uber, who recently shed some light on his expectations for the all-electric supercar.
We all know the Roadster is supposed to have some serious capability. CEO Elon Musk has said on numerous occasions that the Roadster will be unlike anything else ever produced. It might go from 0-60 MPH in about a second, it might hover, it might have SpaceX cold gas thrusters.
However, the constant delays in the Roadster program and its unveiling event continue to send Tesla fans into confusion because they’re just not sure when, or if, they’ll ever see the finished product.
Perhaps the wait will be worth it, especially according to Uber founder Travis Kalanick, who recently teased the Roadster’s potential capabilities based on what he has heard from internal Tesla sources.
Kalanick said on X:
When I’ve run into people who are in the know, I inquire, they tell me nothing, but their eyebrows raise and their eyes widen in a way that can only mean something of sorcery and magic is coming…
— travis kalanick (@travisk) March 17, 2026
Musk has said this vehicle is not going to be geared for safety, and that, “If safety is your number one goal, do not buy the Roadster.”
There has been so much hype regarding the Roadster that it is hard to believe the company could not come through on some kind of crazy features for the vehicle.
However, the latest delay that Tesla put on the unveiling event is definitely eye-opening, especially considering it is the latest in a series of pushbacks the company has put on the vehicle for the past several years.
Tesla has made several jumps in the Roadster project over the past few months, as it has ramped up hiring for the vehicle and also applied for a patent for a new seat design.
The car has been a back-burner project for Tesla, as it has been focusing primarily on autonomy and the rollout of Robotaxi and Cybercab. Additionally, its other vehicle projects, like the Model 3 and Model Y refreshes, took precedence.
Tesla still plans to unveil the Roadster next month, so we can hope the company can stick to this timeframe.
Cybertruck
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Tesla CEO Elon Musk has clarified some details regarding the viral Tesla Cybertruck accident with company driver logs, which show various metrics at the time of an incident.
The logs have been used in the past to pull responsibility off of Tesla when the automaker’s Full Self-Driving (Supervised) or Autopilot platforms are blamed for a collision or accident. It appears this will be no different.
On Tuesday, a video of a Cybertruck crashing into an overpass barrier in August 2025 was shared by Fox Business in a story that reported a woman was suing the automaker for $1 million in a liability and negligence case.
In the suit, Justine Saint Amour said that, “Something terrifying happened, without warning, the vehicle attempted to drive straight off an overpass.” Her attorney, Bob Hilliard, said Amour “tried to take control, but crashed into the barrier and was seriously injured (mostly her shoulder, neck, and back).”
The Tesla Model Y is leading China’s electric SUV segment by a wide margin
Tesla vehicle crashes are widely popular to report by mainstream media outlets because of the sensationalism of the event. Oftentimes, these outlets will include Tesla in the headline, especially because it will pique the interest of the masses, as most who read the story are waiting to see the claim that Autopilot or Full Self-Driving was the culprit of the accident.
However, Tesla has access to the logs of every vehicle in its fleet, which will show the various metrics, like whether either FSD or Autopilot was active, if the accelerator was pressed, the speed, and other important factors.
Musk has come out to say that the driver logs have already shown that the driver “disengaged Autopilot four seconds before crashing,” in a post on X.
Logs show driver disengaged Autopilot four seconds before crashing
— Elon Musk (@elonmusk) March 18, 2026
If the logs do show this, which Tesla will likely have to prove in court, the real question would be why did the Amour disengage the suite?
Tesla’s Full Self-Driving suite is still not fully autonomous, meaning the driver cannot pull attention away from the road and must be ready to take over the vehicle at all times.
It will be interesting to see how this particular case pans out, especially considering the clip that was released by the law firm starts at about four seconds before the collision. Tesla logs have dispelled media reports in the past that have accused the company’s suite of being responsible for an accident, so there will be some major attention on what is proven in this particular case.
News
Tesla Robotaxi appears to be heading to a new U.S. city
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
Tesla Robotaxi appears to be heading to a new U.S. city, and although the company has revealed plans to launch in six new metros this year, it has yet to establish a new location outside of Austin and the Bay Area of California, where it has operated since last Summer.
A lot full of Model Y vehicles was spotted in Henderson, a town just north of Las Vegas, but there seems to be more than just this hint indicating that the Sin City will be the next location to offer potentially driverless rides in a Tesla using its Full Self-Driving suite.
These Model Ys are not your typical vehicles, as they are fitted with hardware that is only on Robotaxis: a rear camera washer is the dead giveaway:
🚨 These rear camera washers are only present on Robotaxi vehicles
Maybe Las Vegas is the next city to get the Robotaxi suite 😀 https://t.co/my3da5L4zc pic.twitter.com/jYFQuX1j2E
— TESLARATI (@Teslarati) March 17, 2026
The photos and video of the lot were taken by TheZacher on X, who spotted the Model Y fleet in the Henderson parking lot.
The rear camera washer is the main piece of evidence here that indicates Tesla could be looking to expand Robotaxi to Las Vegas, a major ride-hailing hot spot, as it is one of the biggest tourist attractions in the United States. Ride-sharing is a major industry in Vegas, especially for those who are staying off the Strip.
Tesla has also been extremely transparent that Vegas is on its radar for the Robotaxi fleet, as it revealed last year that it was one of five new U.S. cities that it planned to launch the ride-hailing service in this year.
Tesla confirms Robotaxi is heading to five new cities in the U.S.
The others were Phoenix, Dallas, Houston, and Miami.
Things are expanding for Robotaxi, but the big sign that it is really moving along greatly will be with the expansion to a new city. Tesla has not gone outside of Austin or the Bay Area as of yet, and launching in a new city will be a great indicator of progress.
It will also give Tesla a new benchmark against rival company Waymo, which has operated in Las Vegas for some time.
Tesla Roadster is ‘sorcery and magic’ and might be worth the wait, Uber founder says
Elon Musk clarifies viral Tesla Cybertruck accident with driver logs
