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.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
