News
SpaceX may have signed a fairing agreement with ULA supplier RUAG (Update: no agreement)
According to unverified and speculative comments reportedly made to a member of the space industry by a RUAG spokesperson, the prominent aerospace supplier may have reached an agreement with SpaceX to manufacture a handful of larger payload fairings for future Falcon 9 and Heavy launches.
In the likely event that SpaceX is one of two contractors awarded a portion of several dozen US military launch contracts next year, the company will need to be able to cater to niche requirements, including accommodating unusually tall military satellites. Those satellites can be so tall that SpaceX’s own payload fairing – generally middle-of-the-pack relative to competitors’ offerings – may be too short, meaning that SpaceX will have to find ways around that minor shortcoming.
Update: Tim Chen has retracted his earlier comments and has stated that there is actually no agreement currently in place with SpaceX for RUAG to produce taller fairings out of its new Decatur, AL factory.
Additionally, ULA CEO Tory Bruno clarified that the company’s “[new fairing] has [ULA] intellectual property in its design and manufacture … [and] is currently planned only for use on Atlas and Vulcan”, meaning that any cooperation between SpaceX and RUAG would likely require a new production facility and a somewhat different fairing design.
“ULA’s new fairing, which is built in our factory in Decatur, has our intellectual property in its design and manufacture. This fairing is currently planned only for use on Atlas and Vulcan. You would want to ask RUAG about business they might have with their other customers.”
Tory Bruno, August 14th, 2019
Regardless of the veracity of these recent claims, it appears that SpaceX has three obvious responses at its disposal: design and build an entirely new variant of its universal Falcon fairing, purchase the necessary fairings from an established supplier, or bow out of launch contract competitions that demand it. The latter option is immediately untenable given that it could very well mean bowing out of the entire US military competition, known as Phase 2 of the National Security Space Launch program’s (NSSL; formerly EELV) Launch Services Procurement (LSP).
For dubious reasons, the US Air Force (USAF) has structured the NSSL Phase 2 acquisition in such a way that – despite there being four possible competitors – only two will be awarded contracts at its conclusion. The roughly ~30 launch contracts up for grabs would be split 60:40 between the two victors, leaving two competitors completely emptyhanded. In short, bowing out of the Phase 2 competition could mean forgoing as many as one or two-dozen contracts worth at least $1-2B, depending on the side of the 60:40 split.
According to a handful of recent comments and developments, SpaceX has likely sided with the option of procuring taller fairings from an industry supplier. As it turns out, European company RUAG has effectively cornered the Western rocket fairing market, with SpaceX being the only Western launch company currently building its own fairings. RUAG builds fairings for both Arianespace’s Ariane 5 and Vega rockets and ULA’s Atlas V. Additionally, RUAG will build and supply fairings for both companies’ next-gen rockets – Arianespace’s Ariane 6 and ULA’s Vulcan – and builds fairings for a number of smallsat launch companies.
Comments made in June by a RUAG official confirmed that there was some semblance of a relationship between SpaceX and RUAG for the purpose of satisfying USAF needs for taller fairings, although the phrasing suggested that the cooperation was in its early stages and nothing had been solidified.
“In a June 12 letter to Smith, the company’s CEO Peter Guggenbach makes the case that legislation forcing access to suppliers is unnecessary in this case because RUAG does not have an exclusive arrangement with ULA and is willing to work with SpaceX or any other launch providers.
“For this competition, we are in the process of submitting or have submitted proposals to multiple prime contractors regarding launch vehicle fairings. In those agreements, we share technical data to support a prime contractor’s bid while protecting our intellectual property.”
RUAG vice president Karl Jensen told SpaceNews the company has a “significant partnership” with ULA but is looking to work with others too. “We have an offer to SpaceX,” he said. “We don’t know if they’ll accept it.”
SpaceNews, 06/13/2019
Interestingly, although ULA’s RUAG-built Atlas V fairing is slightly narrower than SpaceX’s 5.2m (17 ft) diameter fairing, Atlas V’s largest fairing is significantly taller, supporting payloads up to 16.5m (54 ft) tall compared to 11m (36 ft) for Falcon 9 and Heavy. Given that just a tiny portion of military spacecraft actually need fairings that tall, SpaceX is apparently not interested in simply modifying its own fairing design and production equipment to support a 20-30% stretch.
This likely relates in part to the fact that one of SpaceX’s three NSSL Phase 2 competitors – Northrop Grumman (Omega), Blue Origin (New Glenn), and ULA (Vulcan) – are guaranteed to receive hundreds of millions of dollars of development funding after winning one of the two available slots (60% or 40% of contracts). SpaceX, on the other hand, will receive no such funding while still having to meet the same stringent USAF requirements compete in LSP Phase 2. Of note, Congressman Adam Smith managed to insert a clause into FY2020’s defense authorization bill that could disburse up to $500M to SpaceX in the event that the company is one of Phase 2’s two winners.
Despite this potential influx of infrastructure-focused funds, SpaceX may still be pursuing taller Falcon fairings from RUAG as a backup in the event that the company is not one of the two Phase 2 winners or is unable to use some of the $500M secured by Rep. Smith to develop its own stretched fairing.
On August 12th, SpaceX – along with Blue Origin, ULA, and NGIS – submitted bids for NSSL Phase 2 launch services, confirming that all four companies will indeed be in the running for contracts. The USAF is not expected to announce the results of this competition until Q2 2020.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
