The NHTSA robotaxi directive issued this week is blunt by federal standards, but the agency has been careful not to spell out what happens if developers ignore it. That tension, between stern language and uncertain enforcement, is precisely the story right now in autonomous vehicles.
NHTSA’s Robotaxi Directive: Strong Words, Open Consequences
National Highway Traffic Safety Administration (NHTSA) administrator Jonathan Morrison sent a letter to every autonomous vehicle developer listed in the Department of Transportation’s Standing General Order, demanding they address a ‘clear pattern’ of driverless vehicles interfering with law enforcement and emergency services. The specific failures cited include vehicles driving into active emergency scenes, blocking ambulances and firefighters, and failing to recognise flashing lights, flares, smoke, fire, and traffic cones.
Morrison’s letter made the core argument plainly: ‘Let me be clear: the inability to detect and appropriately respond to such situations represents a functional insufficiency. Emergency scenes are not rare or extreme edge cases. As such, NHTSA is today issuing a call to action for AV developers and operators to immediately focus their resources on fixing this issue.’
Companies have until the end of the month to present solutions. According to CBT News, NHTSA plans to meet with developers in person by the end of July rather than simply collect written submissions. What happens to companies that show up with inadequate answers remains unstated: the letter specifies no consequences for non-compliance.
The directive names no single company. But Waymo, which operates the largest robotaxi fleet in the United States across Los Angeles, Phoenix, and San Francisco, has had documented run-ins with first responders. The July 4 fireworks gridlock in San Francisco added fresh material. Local reports had already noted that numerous Waymo robotaxis were towed after running out of power during the lengthy traffic jam. The Next Web reported that some vehicles also stalled and caught fire during the same event.
San Francisco supervisor Bilal Mahmood separately announced plans to submit a letter of inquiry examining how autonomous vehicles affected public transit and emergency responders during and after the fireworks show.
Regulatory Agenda Opens a Door for Driverless Vehicle Design
The same week the directive landed, the DOT published its updated 2026 Regulatory Plan and Unified Agenda. It lists eight separate rulemakings aimed at modernising a total of ten different Federal Motor Vehicle Safety Standards (FMVSS) to account for autonomous vehicles, according to a Sidley analysis of the DOT agenda. These adjust existing standards rather than create new ones from scratch.
One rulemaking under FMVSS No. 126 would address requirements for vehicles with Automated Driving Systems that lack manually operated driving controls, given that the current standard assumes a human driver behind a steering wheel. That matters for companies like Tesla and Zoox, which are developing vehicles without steering wheels or pedals entirely.
Morrison went further on 9 July 2026, telling CNBC the agency would ‘absolutely’ consider ending the requirement for driverless vehicles to include steering wheels and manual controls. His reasoning: ‘If you’re developing a vehicle that is designed never to be driven by a human operator, it doesn’t make any sense to require manual controls.’ The agency had already updated federal safety standards in June 2026 to remove the requirement for manual brake pedals in vehicles built exclusively for autonomous operation, according to Basenor.
So the same regulator issuing stern warnings about robotaxi safety failures is simultaneously loosening the design rules that govern them. Make of that what you will.
Rivian’s Share Sale: $1.34 Billion Gross, DOE Financing in the Mix
Away from the regulatory drama, Rivian closed a sizeable equity raise. The company sold 86.25 million Class A common shares at $15.50 each, including 11.25 million shares that underwriters opted to purchase on top of the initial 75 million announced the previous day. Goldman Sachs acted as representative of the underwriters, and the underwriting agreement was signed on 7 July 2026, according to a report on the final deal size.
Gross proceeds came to approximately $1.34 billion. After underwriting discounts, commissions, and expenses, net proceeds are approximately $1.32 billion, implying underwriting costs of around 1.3% of the deal. The raise was completed under Rivian’s existing shelf registration statement filed on 30 April 2026.
As to what the money is for: Yahoo Finance, citing the company, reports Rivian intends to use proceeds for general corporate purposes, including equity contributions required under its financing agreement with the US Department of Energy (DOE). The DOE has agreed to facilitate a multi-draw term loan through the Federal Financing Bank for one of Rivian’s subsidiaries.
Rivian reported an estimated cash, cash equivalents, and short-term investments balance of $5.3 billion as of 30 June 2026, alongside preliminary total consolidated revenue estimates for Q2 2026 of $1.55 billion to $1.65 billion, per its prospectus supplement. The company also revised its 2026 delivery forecast upward to between 65,000 and 70,000 vehicles, crediting strong quarter-over-quarter growth in its EDV and R1 lines plus early R2 deliveries.
Rivian is not yet profitable, and scaling R2 production is capital-intensive. The DOE loan backstop at least signals the federal government remains a willing partner, even as it issues stern letters to Rivian’s robotaxi-adjacent industry neighbours next door. The end-of-July NHTSA meeting with AV developers is the next date worth watching.
