What happens when a driverless Class 8 breaks down at 2 AM?

What happens when a driverless Class 8 breaks down at 2 AM?

Aurora Innovation is running driverless Class 8 trucks commercially between Dallas and Houston. Kodiak Robotics operates driverless trucks in the Permian Basin. Both companies have logged commercial miles, reported safety data, and announced plans to scale to hundreds of trucks by the end of 2026. The hardware is operational. The question fleet managers and shop supervisors should be asking: what is the service protocol when one of these units fails on the highway in the middle of the night?

No public roadside-failure protocol exists

A conventional Class 8 breakdown triggers a known sequence: driver calls dispatch, dispatch calls roadside service, a mobile tech or tow truck arrives, the unit is cleared or towed. The driver can set triangles, communicate with first responders, and move the truck to the shoulder if it retains partial power. An autonomous truck has no driver in the cab. If the propulsion system faults, the ADAS suite loses power, or a tire blows at highway speed, the unit must execute a minimal-risk condition stop — often in the right lane or on the shoulder, depending on what the system can execute before it shuts down.

Neither Aurora nor Kodiak has published a detailed roadside-failure SOP accessible to state troopers, tow operators, or the carriers that will eventually lease or operate these trucks. The companies have reported safety data and scaling timelines, but the operational question — who responds, how fast, what the responder is authorized to do with an unmanned cab, and whether the unit can be safely towed or must wait for a company technician — remains unanswered in public documentation.

What a shop supervisor needs to know before the first unit arrives

If a carrier adds an autonomous truck to its fleet, the maintenance manager must know:

• Service-call response time. A conventional roadside service contract guarantees arrival within 60 to 90 minutes in most metro corridors. Autonomous OEMs have not disclosed whether their remote operations centers dispatch third-party service, company technicians, or rely on the carrier's own roadside vendor. If the unit is disabled in a rural stretch between Dallas and Houston, the response time could exceed three hours.

• Towing compatibility. Standard wrecker procedure hooks the front axle and lifts. Autonomous trucks carry sensor arrays, lidar units, and compute hardware in the nose and roof fairings. A tow operator unfamiliar with the hardware could damage $50,000 worth of sensors during a routine hook. The OEM must provide a tow-safe diagram and train the carrier's roadside vendors, or the carrier will eat the repair cost when the unit arrives at the shop with a cracked lidar housing.

• Remote diagnostics and override authority. If the truck stops in the right lane and will not restart, can the remote operations center override the minimal-risk condition and move the truck 200 feet to a safer position? Or does the unit stay put until a technician arrives with a laptop? The answer determines whether the disabled truck blocks traffic for 20 minutes or two hours.

• First-responder interaction. A state trooper arriving at a disabled truck with no driver in the cab has no protocol for securing the scene. The trooper cannot ask the driver to move the unit, cannot verify the load, and cannot determine whether the truck is safe to approach. If the unit is carrying hazmat, the placard is visible, but the trooper has no one to interview about the cargo. Autonomous OEMs must coordinate with state DOTs and highway patrol to establish a contact protocol — a phone number on the cab door, a remote operations center that answers immediately, and a procedure for granting access to the cab if the trooper needs to inspect the load or disable the vehicle.

Scaling to thousands of units without a public service network

Aurora and Kodiak plan to scale to hundreds of trucks by the end of 2026. If each company operates 500 units and the industry-average breakdown rate is one roadside event per 15,000 miles, the combined fleet will generate roughly 65 roadside events per month at 1 million miles per month. By 2028, if the fleets scale to thousands of units, the monthly roadside event count will exceed 200.

The companies have not disclosed whether they are building a proprietary roadside service network, contracting with national providers like Love's or Pilot, or expecting carriers to handle service through existing vendors. A carrier that leases an autonomous truck and relies on its current roadside contract may find that the vendor refuses the call because the technician is not trained on the hardware, or the tow operator will not hook the unit without an OEM-provided diagram.

What changes for a small fleet considering autonomous lease terms

A small fleet evaluating an autonomous truck lease or purchase must negotiate the service terms up front. The lease agreement should specify:

• Who pays for roadside service. If the OEM retains ownership of the autonomy hardware and the carrier leases the truck, the OEM should cover service calls related to autonomy-system failures. If the carrier owns the truck outright, the carrier needs a service contract that covers both the base truck and the autonomy stack, or the carrier will face a $5,000 service call every time the lidar faults.

• Service response-time guarantee. The lease should include a maximum response time for roadside failures, with penalties if the OEM or its service provider exceeds the window. A truck sitting disabled for four hours costs the carrier the load, the customer relationship, and the tow fee.

• Towing and transport procedures. The OEM must provide a tow-safe diagram, train the carrier's roadside vendors, and indemnify the carrier if a third-party tow operator damages the autonomy hardware following OEM-provided instructions.

• Remote diagnostics access. The carrier's shop supervisor should have read access to the autonomy system's fault codes and diagnostic logs. If the truck arrives at the carrier's shop after a roadside failure, the supervisor needs to know whether the failure was autonomy-related or a base-truck issue before calling the OEM or the Freightliner dealer.

The hardware is real. The commercial miles are real. The scaling plans are real. The service infrastructure that keeps these trucks running when they break down is not yet visible to the carriers, shops, and first responders who will have to manage the failures.