News
SpaceX nears big US govt. missions as ULA handwaves about risks of competition
Speaking at the 2018 Von Braun Symposium in Huntsville, Alabama, ULA COO John Elbon expressed worries that the US National Security Space (NSS) apparatus could be put at significant risk if it comes to rely too heavily on the commercial launch industry to assure access to space.
Given that the US military’s launch capabilities rest solely on SpaceX and ULA and will remain that way for at least three more years, Elbon’s comment was effectively an odd barb tossed in the direction of SpaceX and – to a lesser extent – Blue Origin, two disruptive and commercially-oriented launch providers.
- The history of ULA and its Delta IV rocket is far wilder than most would expect. (Tom Cross)
- The first stage of Parker Solar Probe’s Delta IV Heavy rocket prepares to be lifted vertical. (ULA)
Reading between the lines
For the most part, Elbon’s brief presentation centered around a reasonable discussion of ULA’s track record and future vehicle development, emphasizing the respectable reliability of its current Atlas V and Delta IV rockets and the ‘heritage’ they share with ULA’s next-generation Vulcan vehicle. However, the COO twice brought up an intriguing concern that the US military launch apparatus could suffer if it ends up relying too heavily on ‘commercially-sustained’ launch vehicles like Falcon 9/Heavy or New Glenn.
To provide historical context and evidence favorable to his position, Elbon brought up a now-obscure event in the history of the launch industry, where – 20 years ago – companies Lockheed Martin and Boeing reportedly “set out to develop … Atlas V and Delta IV” primarily to support the launch of several large satellite constellations. The reality and causes of the US launch industry’s instability in the late ’90s and early ’00s is almost indistinguishable from this narrative, however.
Despite the many veils of aerospace and military secrecy surrounding the events that occurred afterward, the facts show that – in 1999 – Boeing (per acquisition of McDonnell Douglas) and Lockheed Martin (LM) both received awards of $500M to develop the Delta IV and Atlas V rockets, and the military further committed to buying a full 28 launches for $2B between 2002 and 2006. Combined, the US military effectively placed $3B ($4.5B in 2018 dollars) on the table for its Evolved Expendable Launch Vehicle (EELV) program with the goal of ensuring uninterrupted access to space for national security purposes.
- Crew Dragon arrives at ISS. (SpaceX)
- Boeing’s Starliner spacecraft. (Boeing)
- A mockup of Boeing’s Starliner capsule is explored by one of NASA’s Commercial Crew astronauts, clad in a Boeing spacesuit. (Boeing)
- SpaceX’s Commercial Crew pressure suit seen on NASA astronauts during testing. (SpaceX)
Rocketing into corporate espionage
“The robust commercial market forecast led the Air Force to reconsider its acquisition strategy. The EELV acquisition strategy changed from a planned down-select to a single contractor and a standard Air Force development program [where the USAF funds vehicle development in its entirety] to a dual commercialized approach that leveraged commercial market share and contractor investment.” – USAF EELV Fact Sheet, March 2017
The above quote demonstrates that there is at least an inkling of truth in Elbon’s spin. However, perhaps the single biggest reason that the EELV program and its two awardees stumbled was gross, inexcusable conduct on the part of Boeing. In essence, the company’s space executives conspired to use corporate espionage to gain an upper-hand over Lockheed Martin, knowledge which ultimately allowed Boeing to severely low-ball the prices of its Delta IV rocket, securing 19 of 28 available USAF launch contracts.
Ultimately, Lockheed Martin caught wind of Boeing’s suspect behavior and filed a lawsuit that began several years of USAF investigations and highly unpleasant revelations, while Boeing also had at least 10 future launch contracts withdrawn to the tune of ~$1B (1999). USAF investigations discovered that Boeing had lied extensively to the Air Force for more than four years – the actual volume of information stolen would balloon wildly from Boeing’s initial reports of “seven pages of harmless data” to 10+ boxes containing more than 42,000 pages of extremely detailed technical and proprietary information about Lockheed Martin’s Atlas V rocket proposal.
“If you rewind the clock 20 years, there were folks on a panel like this having dialogue about commercial launch, and there were envisioned several constellations that were going to require significant commercial launch. Lockheed Martin and Boeing set out to develop launch vehicles that were focused on that very robust commercial market – in the case of McDonald Douglas at the time, which later became Boeing, the factory in Decatur was…sized to crank out 40 [rocket boosters] a year, a couple of ships were bought to transport those…significant infrastructure put in place to address that envisioned launch market.” – John Elbon, COO, United Launch Alliance (ULA)
- ULA’s Decatur, Alabama factory now produces both Delta IV and Atlas 5. (ULA)
- ULA’s Atlas 5 launched AEHF-4 for the USAF earlier this month. (ULA)
In reality, Boeing was so desperate to secure USAF launches – despite the fact that it knew full well that Delta IV was too expensive to be sustainably competitive – that dozens of employees were eventually roped into a systematic, years-long, highly-illegal program of corporate espionage specifically designed to beat out government launch competitor Lockheed Martin. Humorously, Delta IV was not even Boeing’s design – rather, Boeing acquired designer McDonnell Douglas in late 1996, five days before the USAF announced the decision to reject Boeing and another company’s EELV proposals, narrowing down to two finalists (McDonnell Douglas and Lockheed Martin).
Seven years after the original lawsuit snowballed, Boeing settled with Lockheed Martin for a payment of more than $600M in 2006, accepting responsibility for its employees’ actions but admitting no corporate wrongdoing. Five years after that settlement, John Elbon became Vice President of Boeing’s Space Exploration division. This is by no means to suggest that Elbon is in any way complicit, having spent much of his 30+ years at Boeing managing the company’s involvement in the International Space Station, but more serves as an example of how recent these events are and why their consequences almost certainly continue to reverberate loudly within the US space industry.
SpaceX forces change
Worsened significantly by the consequences of Boeing’s lies about the actual operational costs of its Delta IV rocket (it had planned to secretly write off a loss on each rocket in order to steal USAF market share from LockMart), the commercial market for the extremely expensive rocket was and still is functionally nonexistent. 35 out of the family’s 36 launches have been contracted by the US military (30), NOAA (3), or NASA (2); the rocket’s first launch, likely sold at a major discount to Eutelsat, remains its one and only commercial mission.

Atlas V, typically priced around 30% less than comparable Delta IV variants, has had a far more productive career, albeit with very few commercial launches since the Dec. 2006 formation of the United Launch Alliance. Since 2007, just 5 of Atlas V’s 70 launches have been for commercial customers. Frankly, although Atlas V was appreciably more affordable than Delta IV, neither rocket was ever able to sustainably compete with Europe’s Ariane 5 workhorse – Ariane 5 cost more per launch, but superior payload performance often let Arianespace manifest two large satellites on a single launch, approximately halving the cost for each customer. Russia’s affordable (but only moderately reliable) Proton rockets also played an important role in the commercial launch industry prior to SpaceX’s arrival.
After fighting tooth and nail for years to break ULA’s US governmental launch monopoly, SpaceX’s first dedicated National Security Space launch finally occurred less than a year and a half ago, in May 2017. SpaceX has since placed a USAF spaceplane and a classified NSS-related satellite into orbit and been awarded launch contracts for critical USAF payloads, most notably winning five of five competed GPS III satellite launches, to begin as early as mid-December. Falcon 9 will cost the USAF roughly 30% less than a comparable Atlas 5 contract, $97M to ULA’s ~$135M.
- The aft connection mechanisms on Falcon Heavy Flight 1 and Flight 2 appear to be quite similar. It’s possible that SpaceX has chosen to reuse aspects of the hardware recovered on Flight 1’s two side boosters. (SpaceX)
- Falcon 9 Block 5 booster B1046 seen during both of its post-launch landings. (SpaceX/SpaceX)
A bit more than two decades after Boeing bought McDonnell Douglas and began a calculated effort to steal trade secrets from Lockheed Martin, Elbon – now COO of the Boeing/Lockheed Martin-cooperative ULA – seems to fervently believe that the most critical mistake made in the late 1990s and early 2000s was the USAF’s decision to partially support the development of two separate rockets. Elbon concluded his remarks on the topic with one impressively unambiguous summary of ULA’s position:
“We have to make sure that we don’t get too much supply and not enough demand so that the [launch] providers can’t survive in a robust business environment, and then we lose the capability as a country to do the launches we need to do … [That’s] the perspective we have at ULA and it’s based on the experience that we’ve been through in the past.”
In his sole Delta IV vs. Atlas V case-study, what ULA now seems to think might have been “too much supply” under the USAF’s EELV program appears to literally be the fundamental minimum conditions needed for competition to exist at all – two companies offering two competing products. Short of directly stating as much, it’s difficult to imagine a more concise method of revealing the apparent belief that competition – at all – is intrinsically undesirable or risky.
News
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Elon Musk
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
News
Tesla Cybercab has one important piece that AI4 cars might need for FSD
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.









