Midland Driverless Truck Accidents: Who Pays When an Autonomous Oilfield Rig Collides
You are reading this because a truck with no driver hit someone you love on a Permian Basin road — or because you can see it coming. Either way, you are standing at the edge of a kind of case no courtroom has resolved yet. The 18-wheeler that caused the harm had no human behind the wheel. The company that owns the truck says the technology company is responsible. The technology company says the trucking company is responsible. And the person in the hospital bed — or the family at the kitchen table with a death certificate — is caught between two corporations pointing at each other across a server rack. That is the moment you are in. We know this moment. We know what to do with it.
Here is the first thing to understand, and it may be the only thing that lets you breathe: the absence of a human driver does not eliminate accountability. It shifts it. In many ways, it makes the case stronger — because the defense that trucking companies have used for decades, “our driver made a mistake, not the company,” is gone. When the autonomous system was in control, the system’s designers and the company that deployed it stand in the place of the driver. The law has tools for this. Products liability, motor carrier negligence, federal regulatory violations — these are well-established paths, and they all lead to the companies that profited from putting 80,000 pounds of steel on a public road with nobody steering it.
We are Attorney911 — The Manginello Law Firm, PLLC. We handle commercial trucking cases across Texas, including the Permian Basin corridor that runs through Midland and Odessa. Ralph Manginello has spent 27-plus years in courtrooms, including federal court, and was a journalist before he was a lawyer — he reads corporate statements the way he reads evidence, looking for what is left out. Lupe Peña spent years inside a national insurance-defense firm, in the rooms where adjusters and their software decided how to deny, delay, and devalue people exactly like you. He now sits on your side of the table. He conducts full consultations in Spanish without an interpreter. We do not get paid unless we win your case. The consultation is free. The call is 1-888-ATTY-911.
What Is Happening on Permian Basin Roads Right Now
As of December 2024, Atlas Energy Solutions — a publicly traded company (NYSE: AESR) and one of the largest frac-sand suppliers in the Permian Basin — became the first customer in the country to take ownership and independent operational control of driverless commercial semi-trucks. These are Class 8 trucks equipped with the Kodiak Driver, Kodiak Robotics’ sixth-generation autonomous driving platform. The trucks are called “RoboTrucks.” They operate without a safety driver. They deliver proppant — the gritty, resin-coated sand used in hydraulic fracturing — across a 75,000-square-mile operating area spanning West Texas and Eastern New Mexico.
The initial route was a 21-mile off-road path in the Permian Basin. Atlas has since expanded to daily driverless deliveries. The operation is integrated with Atlas’s Dune Express, a 42-mile autonomous conveyor system that feeds sand to the RoboTrucks, creating a fully automated supply chain from mine to well pad. Kodiak established an 18,000-square-foot support facility in Odessa, Texas, staffed by approximately 12 employees with projected growth. Kodiak has also announced its intention to extend operations to highway corridors, including a hub-to-hub partnership with J.B. Hunt Transport Services for autonomous freight.
The companies have framed this as a safety advancement. John Turner, CEO of Atlas, said the deployment enhances the company’s ability to “maintain a fundamentally safe and reliable service at the best price for our customers.” Don Burnette, founder and CEO of Kodiak, called it “an incredible moment” and said “the commercialization of autonomous trucks has been a goal for the industry for many years, and it has now come to fruition.”
“Incorporating these driverless RoboTrucks into our operations is a significant advancement in the automation of our business, enhancing our ability to maintain a fundamentally safe and reliable service at the best price for our customers.”
That is a corporate press statement. It is not a legal defense. When a driverless truck collides with a passenger vehicle, an oilfield worker, or a family on a Basin road, the question is not whether the automation was good for Atlas’s pricing model. The question is whether the companies that built, deployed, and profited from the technology met their duty of care to the people sharing the road with it. If you or someone you love has been hurt by a commercial truck in the Permian Basin — autonomous or not — our 18-wheeler accident practice handles these cases, and we understand the specific hazards of oilfield corridors.
Who Is Liable When a Driverless Truck Causes Injury or Death
The first answer most people need is simple: yes, you can sue. The absence of a human driver does not create a legal vacuum. It creates a multi-defendant liability structure that is, in some respects, more favorable to the injured party than a conventional trucking case — because the comparative-fault defense that a human driver’s testimony traditionally provides is gone. No one can put your loved one’s driving decisions up against a truck driver’s word when there was no truck driver.
The liable parties fall into a stack, and each is a separate investigation:
Atlas Energy Solutions — the motor carrier and truck owner. Atlas owns the RoboTrucks and operates them as commercial deliveries. Under the Federal Motor Carrier Safety Regulations (49 CFR Parts 390–399), Atlas remains a motor carrier subject to financial responsibility requirements, vehicle maintenance standards, and inspection obligations. The autonomous system does not extinguish the carrier’s non-delegable duty to operate safely. If a Kodiak-equipped truck causes a collision, Atlas bears primary motor-carrier liability — the same liability any trucking company bears when its vehicle injures someone, regardless of whether a human was behind the wheel.
Kodiak Robotics — the autonomous system designer and manufacturer. Kodiak designed the Kodiak Driver platform, including the sixth-generation sensor suite, proprietary SensorPods, and the decision-making algorithms that control the truck. Products liability law applies. If a perception failure, a decision-making error, or a sensor degradation in dust or heat caused the collision, Kodiak faces design-defect, manufacturing-defect, and failure-to-warn theories. This is the track that conventional trucking cases do not have — a strict-liability claim against the technology manufacturer, separate from the negligence claim against the carrier.
The OEM chassis manufacturer. The base vehicle — the truck beneath the Kodiak platform — was built by a traditional truck manufacturer whose identity would be confirmed in discovery. If the collision involved a braking failure, a steering defect, or a structural failure in the base vehicle independent of the Kodiak system, that manufacturer is a separate defendant with its own products-liability exposure.
Remote operations or teleoperations personnel. If Kodiak’s operational model includes any human remote oversight — remote operators who can supervise, intervene, or take control — those operators and the companies that employ them carry their own negligence exposure. Delayed intervention, inadequate staffing, or negligent supervision by a remote operator is direct negligence, not vicarious liability.
The corporate structure is the first fight. Atlas is a publicly traded company with substantial revenue. Kodiak is a venture-backed technology firm with institutional investment. Both have the financial resources to fully compensate catastrophic injuries. But each will try to shift responsibility to the other. Atlas will say the autonomous system failed. Kodiak will say Atlas failed to maintain the sensors or operate within the designated operating domain. Naming every defendant at the outset — and mapping the insurance and corporate structure behind each — is the foundational work that determines whether a case settles for a fraction of its value or is built to compel full compensation. For the specific hazards of oilfield trucking in this region, our Texas oilfield commercial truck accident resource covers the carriers, corridors, and dynamics that make Basin trucking cases different from ordinary highway crashes.
Texas Law on Autonomous Truck Liability
Texas law governs collisions occurring on the Texas side of the Permian Basin — the Midland-Odessa corridor, Ector and Midland Counties, and the surrounding production counties. For incidents on the New Mexico side, New Mexico law would govern, and venue selection between the two states’ forums becomes a critical strategic decision.
Comparative fault. Texas follows a modified comparative negligence rule with a 51% bar. If you were 50% or less at fault, you can recover — though your recovery is reduced by your percentage of responsibility. If you are found 51% or more at fault, you are barred entirely. In a driverless truck case, this rule works in the plaintiff’s favor: the autonomous system was in control, which eliminates much of the comparative-fault defense that a human truck driver’s testimony traditionally provides. The adjuster cannot put the truck driver on the stand to say “the car cut me off” — because there was no truck driver. The system’s own logs will show what it perceived and what it did, and those logs are either favorable to your case or they are missing.
Products liability. Texas recognizes strict liability for design defects under the risk-utility test, manufacturing defects, and failure-to-warn claims. The autonomous driving system’s status as a “product” versus a “service” will be a contested legal question of first impression — one of the first times a Texas court will decide whether an autonomous driving platform is a product subject to strict liability. We believe the answer is yes: the Kodiak Driver is a tangible system — sensors, software, control hardware — sold and installed on a commercial truck. It is a product. And the design-defect question is whether the system was unreasonably dangerous because a safer alternative design was feasible and would have prevented the harm.
Punitive damages. Texas imposes limitations on exemplary damages, but those limitations do not apply if the defendant’s conduct is proven by clear and convincing evidence to constitute gross negligence under the statutory definition. Here is where the safety-case documentation becomes explosive: Kodiak has publicly confirmed it “completed its safety case” before driverless deployment. That safety case is a written evaluation that presumably documents what Kodiak knew about operational risks, sensor limitations, edge cases, and hazard scenarios in the Permian Basin operating domain. If that document acknowledges sensor limitations in dust or heat — and operations proceeded regardless — the conscious disregard of a known risk supports gross negligence and opens the door to punitive damages beyond the statutory cap.
The Stowers doctrine. Texas creates a duty on liability insurers to accept reasonable settlement demands within policy limits when a reasonably prudent insurer would do so. In a catastrophic autonomous-truck case with multiple well-capitalized defendants, a well-supported settlement demand — backed by the safety-case documentation and internal testing records obtained in discovery — can create bad-faith exposure for excess carriers who refuse to accept it. This is leverage that Lupe Peña understands from the inside, because he used to be the person on the other side of that calculation.
The statute of limitations. In Texas, you have two years from the date of the crash to file a personal-injury lawsuit, and two years from the date of death to file a wrongful-death claim, under the Texas statute of limitations. Two years sounds like a long time when you are in the hospital. It is not. The evidence in an autonomous-truck case — the system logs, the sensor data, the safety-case documents — can be overwritten or lost in a fraction of that time. The deadline is the floor. The urgency is the evidence.
FMCSA Regulations Still Apply to Driverless Trucks
A motor carrier does not escape the Federal Motor Carrier Safety Regulations by removing the driver. The carrier’s obligations shift — some provisions become inapplicable (hours-of-service logs, driver qualification files, post-crash drug testing), but the core duties remain:
Financial responsibility. A for-hire interstate carrier of non-hazardous property with vehicles rated at 10,001 pounds or more must carry at least $750,000 in liability coverage under federal regulation. For certain hazardous materials, the floor rises to $1,000,000 or even $5,000,000. Atlas, as a publicly traded company operating a fleet in the oilfield, likely carries far more — but the federal minimum is the negotiating floor, not the ceiling. The coverage tower (primary auto liability, excess/umbrella layers, and potentially MCS-90 endorsement if interstate commerce is involved) is mapped in discovery, not assumed from the regulatory minimum.
Vehicle maintenance and inspection. The duty to inspect, maintain, and repair commercial vehicles survives the removal of the driver. For autonomous trucks, this duty extends to the SensorPods, the redundant braking and steering systems, and the base-vehicle components. Atlas must keep maintenance records. If sensor degradation in dusty Permian Basin conditions contributed to a collision, the maintenance and sensor-cleaning logs are the proof of whether Atlas kept the autonomous system in safe operating condition.
Daily vehicle inspection reports. Federal regulations require driver vehicle inspection reports covering brakes, steering, lighting, tires, and other safety-critical systems. These reports must be retained for three months — the shortest retention clock in the FMCSA regime. For autonomous trucks, the question becomes: who performs the daily inspection when there is no driver? If Atlas has a maintenance technician or remote system performing this function, those records exist and must be preserved. If no one is performing daily inspections because there is no driver, that absence is itself a regulatory violation and evidence of negligence.
NHTSA’s Standing General Order on Crash Reporting. Manufacturers of vehicles equipped with Level 3–5 automated driving systems must report certain crash data to NHTSA. This creates a regulatory record of prior incidents involving Kodiak-equipped vehicles — a record that is discoverable in litigation and may reveal a pattern of autonomous-system failures or near-misses before the collision that injured you. These are public regulatory filings obtainable through NHTSA records requests.
Products Liability Against the Autonomous System Manufacturer
The products-liability track against Kodiak is what makes an autonomous-truck case fundamentally different from a conventional trucking case — and potentially more valuable. In a conventional truck crash, you sue the carrier for negligence. In an autonomous-truck crash, you sue the carrier for negligence AND you sue the technology manufacturer under strict liability. Strict liability means you do not have to prove Kodiak was careless — you have to prove the product was unreasonably dangerous.
Design defect. The Kodiak Driver autonomous platform is a product whose design may be unreasonably dangerous if its sensor suite and decision algorithms cannot reliably handle foreseeable Permian Basin conditions. The Permian Basin is not a controlled test track. It is a 75,000-square-mile oilfield with dust storms (haboobs) that reduce visibility to near-zero in seconds, extreme summer heat exceeding 110°F, unpaved lease roads with irregular grades, and mixed traffic including unconventional oilfield equipment, livestock operations, and passenger vehicles. A design-defect claim would target whether a safer alternative design was feasible — enhanced lidar redundancy, thermal imaging for dust conditions, human-in-the-loop fallback, or more conservative operating-domain limitations — and whether that alternative would have prevented the harm.
Failure to warn. Kodiak and Atlas may have failed to adequately warn other roadway users, proximate landowners, or well-site personnel that driverless trucks are operating in the area and may behave unpredictably compared to human-operated vehicles. When a human truck driver encounters a dust cloud ahead, the driver interprets it as an imminent visibility hazard and slows or stops. Whether the Kodiak Driver’s perception stack makes that same interpretation — in real time, in blowing sand, on an unpaved road — is the central engineering question in any future collision case.
Manufacturing defect. If a specific SensorPod, a redundant braking component, or a steering actuator in the subject truck was defective — departed from its intended design — Kodiak or the component manufacturer faces strict liability regardless of how careful the manufacturing process was.
The safety-case documentation. Kodiak has publicly confirmed it “completed its safety case” before driverless deployment — described as a comprehensive evaluation demonstrating the safety and readiness of its self-driving system within Atlas’s operating domain. This is an admission that a written safety evaluation exists. It is discoverable. It is the single most important document in any future autonomous-truck case, because it establishes what Kodiak knew about operational risks, sensor limitations, edge cases, and hazard scenarios before the truck ever rolled without a driver. If the safety case acknowledges that the system has limitations in dust or heat — and operations proceeded anyway — that document becomes the spine of a gross-negligence claim and the engine of punitive damages.
The Evidence Clock: Autonomous System Data Is the New Black Box
In a conventional trucking case, the driver’s hours-of-service logs are the evidence that proves fatigue. Federal law requires carriers to retain those logs for six months — after which, the company can legally destroy them. That six-month clock is why we send preservation letters within days of a crash.
In an autonomous-truck case, the evidence landscape is entirely different — and in some ways more fragile, because the retention rules for autonomous-system data are not standardized.
Kodiak Driver autonomous system logs. These are sensor data, perception outputs, decision-making records, and control commands for the subject vehicle at the time of the incident. This data is the equivalent of the driver’s testimony — it proves what the system perceived, what decisions it made, and whether its response was appropriate. This is the single most critical evidence in any autonomous-truck case. Data retention policies for autonomous-system logs are not standardized by federal regulation. They may be overwritten on short cycles determined by Kodiak’s internal data policies. A preservation letter to Kodiak Robotics must be issued within days of any incident.
Kodiak safety-case documentation. The comprehensive safety evaluation referenced as completed before driverless deployment. This is an existing document. It should be demanded immediately upon any incident. The risk is revision or supersedence as the safety case is updated for highway operations — the current version may be the most honest version the company ever produces.
Atlas RoboTruck maintenance and sensor-cleaning logs. Records of SensorPod inspection, calibration, cleaning, and any degradation incidents. In the dusty Permian Basin, sensor contamination is a foreseeable operational reality. These logs prove whether Atlas maintained the autonomous sensor systems in the condition required for safe operation. Field maintenance logs on oilfield operations are notoriously informal and may be reconstructed or lost. A preservation letter to Atlas is required within days.
Vehicle EDR / black-box data. The subject truck’s base chassis captures vehicle speed, braking application, steering input, and other dynamic data independent of the Kodiak system. This may reveal whether the base vehicle responded appropriately to Kodiak’s control commands. EDR data can be overwritten after a limited number of ignition cycles. It must be imaged within days.
NHTSA ADS crash reports. Filed under the Standing General Order for any prior incidents involving Kodiak-equipped vehicles. These are public regulatory filings obtainable immediately through NHTSA records requests. They establish a regulatory record of prior autonomous-system failures or near-misses — critical for notice, pattern-and-practice, and punitive-damages theories.
Near-miss incident reports, internal testing data, and simulation results. Kodiak and Atlas’s internal records regarding Permian Basin operating conditions. These may reveal known edge cases, sensor failures in dust or heat, and scenarios where the autonomous system failed to respond appropriately. These are the discoverable records of what the companies knew before any incident. Internal corporate documents subject to retention policies. The preservation letter must reference all electronic communications, testing data, and simulation logs.
Scene evidence. Road conditions, dust visibility, weather data, tire marks, debris field, and vehicle positions. Physical reconstruction of the collision is essential to proving what the autonomous system should have perceived and how it should have responded. Environmental conditions — dust, heat, road surface — may explain sensor degradation. Scene evidence degrades within hours to days. Oilfield roads are subject to rapid change from traffic and weather.
Remote operations / teleoperations communications logs. If human remote operators have any supervisory or intervention role, their communications and response times are directly relevant to negligence and causation. Remote communications logs may be retained on short cycles by telecommunications providers. Preservation letters to Kodiak and any third-party telecom vendor are required immediately.
The fastest-dying evidence in an autonomous-truck case is the Kodiak Driver’s own system logs — the electronic record of what the truck “saw” and “decided.” If those logs are not preserved within days of the collision, the family’s ability to prove what happened may be permanently compromised. This is why the day you call is the day the clock starts working for you instead of against you. To understand how we approach commercial-truck cases more broadly, our definitive guide to commercial truck accidents walks through the full investigative process.
Permian Basin Hazards That Challenge Autonomous Sensors
The Permian Basin is not a proving ground. It is the most prolific oil and gas production region in the United States, generating extraordinary heavy-truck traffic on infrastructure that was never designed for the current load. FM roads, county roads, and lease access roads are narrow, often unpaved, and subject to severe dust storms that can reduce visibility to near-zero in seconds. US-285 running north from Pecos through Reeves and Loving Counties is widely known among safety advocates as a high-fatality corridor due to oilfield truck density. TX-302, TX-349, and Loop 338 around Odessa carry dense commercial-vehicle throughput with documented accident histories.
Extreme summer heat exceeding 110°F, blowing sand, and irregular road surfaces create conditions that directly challenge autonomous driving system perception modules. Lidar, radar, and camera systems — the sensors packed into Kodiak’s proprietary SensorPods — can degrade in heavy dust. Camera lenses can be obscured by fine particulate matter. Lidar returns can be scattered by suspended dust particles. Radar performance can be affected by temperature extremes that alter the dielectric properties of the environment.
When driverless trucks share these corridors with conventional oilfield service vehicles, passenger cars, and livestock operations, the collision risk is compounded by the absence of human hazard recognition. A human truck operator driving through the Permian Basin interprets a dust cloud ahead as an imminent visibility hazard. The operator identifies a stock-tank crossing as an animal-vehicle collision risk. The operator recognizes that a crew truck stopped on a lease road may have workers on foot behind it. These are interpretive judgments based on local knowledge and experience. Whether the Kodiak Driver’s perception stack and decision algorithms make those same interpretations — reliably, in real time, in blowing sand, on an unpaved road at 2 p.m. in August — is the engineering question that will decide the first autonomous-truck personal-injury case in the Permian Basin.
The Insurance and Coverage Reality
In a conventional trucking case, the coverage tower is relatively predictable: primary auto liability, excess/umbrella layers, and potentially MCS-90 endorsement if interstate commerce is involved. In an autonomous-truck case, the coverage structure is more complex because the liability is split between two distinct corporate defendants with potentially different insurance arrangements.
Atlas Energy Solutions. As a publicly traded motor carrier operating a fleet in the oilfield, Atlas carries commercial auto liability coverage at or above the federal minimum ($750,000 for non-hazardous property), likely layered with excess and umbrella policies. Atlas may also self-insure a retention layer. The coverage tower is mapped in discovery — the regulatory minimum is the floor, not the disclosure.
Kodiak Robotics. As a technology company, Kodiak’s insurance structure may include products-liability coverage, technology errors-and-omissions coverage, and general commercial liability — a different insurance architecture than a motor carrier. Whether Kodiak’s policies cover autonomous-driving-system failures in commercial operation is a coverage question that may itself become a litigation track.
The gap. The most dangerous scenario is one where Atlas’s carrier denies coverage by arguing the collision was caused by a product defect in the Kodiak system (not a covered motor-carrier occurrence), and Kodiak’s carrier denies coverage by arguing the collision was caused by Atlas’s negligent maintenance or operation (not a covered product defect). This coverage gap is where injured parties can be left undercompensated — and it is why naming every defendant and mapping every policy at the outset is the most important early strategic work.
Workers’ compensation vs. third-party tort. If the injured person was an oilfield worker on the job — for instance, a worker on foot at a well pad struck by a RoboTruck during a delivery — two lanes exist. The workers’-compensation lane provides no-fault benefits but is capped and bars suit against the direct employer. The third-party tort lane allows a full-damages suit against the negligent non-employer — Atlas, Kodiak, or both. The third-party lane is where the real recovery lives, because it includes the human losses — pain, suffering, lost quality of life — that workers’ compensation never pays. Drawing this fork early reorders a family’s entire understanding of the case.
The Medicine: What an 80,000-Pound Driverless Truck Does to a Human Body
A fully loaded Class 8 commercial truck weighs up to 80,000 pounds. A passenger vehicle weighs roughly 4,000 pounds. That is a 20-to-1 mass disparity. When those two objects collide, the laws of physics do not care whether a human or a computer was steering the truck. The energy transfer is the same. The injuries are the same. The difference is only in who answers for them.
The predictable injury classes in a Permian Basin truck collision — autonomous or conventional — include traumatic brain injury, spinal cord injury, crush injury, amputation, and wrongful death. These are catastrophic injuries that change the trajectory of a family’s life across decades.
Traumatic brain injury. A “mild” traumatic brain injury — the medical term for a concussion-class injury on the Glasgow Coma Scale — can come with a perfectly normal CT scan. That is the standard presentation, not the exception. Roughly one in seven people with a “mild” TBI still has symptoms three months later: the headaches, the lost words, the short fuse. You may see it across the dinner table before any scan sees it. These injuries are proven with neuropsychological testing, advanced imaging, and the testimony of people who knew the person before. For a deeper look at brain injury litigation, our brain injury practice page covers the medicine and the proof.
Spinal cord injury. The National Spinal Cord Injury Statistical Center tracks every spinal-cord injury in the country. The first year of a high-cervical (neck-level) paralysis costs approximately $1.4 million in medical care. The lifetime cost for a young adult with high tetraplegia exceeds $6 million — and that figure deliberately excludes lost wages. Vehicle crashes are the number-one cause of paralysis in America.
The mass disparity. In a two-vehicle collision, the lighter vehicle undergoes the larger change in velocity — the delta-V — and delta-V is the single best predictor of occupant injury severity. When an 80,000-pound autonomous truck collides with a 4,000-pound car, the people in the car absorb most of the violent change in motion. The question of who was steering the truck matters to liability. It does not matter to the physics.
For families facing these injuries, the victims’ guide to 18-wheeler accident injuries walks through what to expect medically and legally.
The Insurance Adjuster’s Playbook
The adjuster’s job is to close your file for the smallest number possible. That is not cynicism — it is the job description. Here are the plays you will see, and here is what to do about each one.
Play 1: The “just tell us what happened” recorded statement. Within days of the collision, someone friendly will call to check on you and ask you to “just tell us what happened” — on a recording engineered to be quoted against you. In an autonomous-truck case, this play is even more dangerous because the technology is novel and the adjuster will try to get you to speculate about what the truck “was doing” or “should have done” — speculation that will later be used to undermine your credibility. Counter: Do not give a recorded statement without counsel. The truck’s own system logs are the objective record of what happened. Your statement is not needed to investigate the crash — it is needed to build a defense against you.
Play 2: The fast settlement check. A check may arrive fast, with a release printed on the back or attached, before the full medical picture is clear. In the Permian Basin, where trauma centers may be hours away and injuries can declare themselves over days, a quick check is designed to close the file before the real cost is known. Counter: Do not sign a release before the medical picture is complete. A traumatic brain injury may not be diagnosed until neuropsychological testing weeks later. A spinal injury may not declare itself until swelling resolves. The release the adjuster offers in week one covers injuries you may not know you have in week four.
Play 3: The “no driver, no liability” argument. The adjuster may suggest that because there was no human driver, the collision was a “technology failure” for which the trucking company is not responsible — or conversely, that it was an “operational failure” for which the technology company is not responsible. This is the shell game. Counter: Both companies are liable. The motor carrier’s duty to operate safely does not depend on having a human driver. The technology manufacturer’s duty to design a safe product does not depend on the carrier’s maintenance practices. We name every defendant and let the evidence assign responsibility — not the adjuster’s first narrative.
Play 4: The social-media surveillance. The adjuster’s team will monitor social media accounts, looking for photos or posts that can be taken out of context to minimize the injury. A photo of you at a family barbecue becomes “the plaintiff is clearly active and unhurt.” Counter: Set everything to private. Do not post about the collision, your injuries, your medical appointments, or your activities. Assume everything you post will be exhibited in a courtroom.
Play 5: The independent medical examination with their doctor. The insurer will send you to a doctor they pick for an “independent” examination. That doctor is not independent — they are selected because their reports consistently minimize injury. Counter: We have seen the IME playbook from the inside. We know which doctors the insurers pick and why. We prepare you for the examination and we challenge the report when it contradicts the treating physicians.
Lupe Peña knows these plays because he used to run them. He sat in the rooms where adjusters and their software — programs like Colossus — decided how to value claims. He knows how reserves are set in the first 48 hours, before the real injuries are diagnosed. He knows how IME doctors are selected. He knows the delay tactics aimed at running the statute of limitations. He now uses that knowledge for injured clients, and that knowledge is the reason the adjuster’s first offer is never the last word.
The First 72 Hours After a Driverless Truck Crash
Hour 1 through Hour 24: Medical first. If you were in the collision, you go to the hospital — even if you feel “okay.” Traumatic brain injuries, spinal injuries, and internal injuries can present with delayed symptoms. The ER record from the day of the crash is the medical baseline that defeats the defense’s “she wasn’t really hurt” argument. If your loved one was killed, the medical examiner’s report and the death certificate are the foundational documents.
Hour 24 through Hour 48: Evidence lockdown. This is when the preservation letters go out — to Atlas, to Kodiak, to any third-party data vendor or telecommunications provider involved in remote operations. The letters must specifically name the Kodiak Driver autonomous system logs, the safety-case documentation, the maintenance and sensor-cleaning logs, the vehicle EDR data, and all internal communications relating to the incident. Every day that passes without a preservation letter is a day the company can legally allow evidence to be overwritten, deleted, or “lost.”
Hour 48 through Hour 72: Scene and vehicle preservation. The wrecked truck must not be released to the carrier for repair or scrapping. The truck is evidence — the SensorPods, the sensor surfaces, the base-vehicle components, and any physical damage patterns are the physical record of what happened. A preservation order or an agreed evidence-hold must be in place before the carrier takes possession. The scene itself — tire marks, debris field, road conditions, dust visibility at the time — degrades within hours to days. Oilfield roads change rapidly from traffic and weather. Photograph everything. Document the weather conditions. Identify witnesses.
What not to sign, say, or post. Do not sign anything from the insurance company. Do not give a recorded statement. Do not post about the collision on social media. Do not discuss the collision with anyone except your lawyer and your doctor. Do not assume the “friendly” investigator from the company is on your side — they are building a defense file from the moment they arrive at the scene.
When to call. The day you call is the day the preservation letters go out. In an autonomous-truck case, the system logs that prove what the truck perceived and decided may be on a deletion cycle measured in days, not months. Every day you wait is a day the evidence dies. The call is 1-888-ATTY-911. The consultation is free. We do not get paid unless we win your case.
What Your Case Is Worth
No honest attorney can tell you what your case is worth without seeing the medical records, the collision reconstruction, the defendant’s corporate structure, and the insurance tower. What we can tell you is the framework — how a real number is built, and why the adjuster’s first offer is a fraction of it.
For a fatal or catastrophic-injury collision involving a driverless Class 8 truck operated by a publicly traded carrier and a venture-backed technology company, the prospective case value range — based on comparable catastrophic commercial-trucking and emerging-technology product-liability verdicts — runs from approximately $1,500,000 on the low end to $25,000,000 or more on the high end. Cases involving gross-negligence findings — known sensor limitations, ignored near-miss data — could exceed these ranges if punitive damages are awarded.
The reason these cases can be more valuable than conventional trucking cases is structural: the autonomous system was in control, which eliminates much of the comparative-fault defense. The products-liability component against Kodiak adds a strict-liability track that is not available in conventional trucking cases. And both defendants — Atlas and Kodiak — are well-capitalized entities with the resources to fully compensate catastrophic injuries.
The number is built from the economic stream — past and future medical expenses, including potentially lifelong life-care planning for catastrophic injuries; lost wages and lost earning capacity; property damage — and the human losses: pain and suffering, mental anguish, loss of consortium, disfigurement, and the life the injured person no longer gets to live. A life-care planner builds the cost stream. A forensic economist reduces it to present value. The adjuster’s first offer is a fraction of that number because the adjuster’s software cannot see the human losses. Our job is to make the jury see them.
Past results depend on the facts of each case and do not guarantee future outcomes.
The Proof Story
Here is how an autonomous-truck case is actually built, from the day you call to the day the number is real.
Week one. The preservation demand goes out to Atlas and Kodiak, freezing the system logs, the safety-case documents, the maintenance records, the sensor-cleaning logs, the internal communications, the testing data, and the simulation results. The truck is secured and not released. The EDR is imaged. NHTSA ADS crash reports are requested through the Standing General Order database. The scene is documented — weather conditions, road conditions, dust visibility, tire marks, debris field.
Weeks two through eight. The records come out in discovery. The Kodiak Driver system logs are downloaded and analyzed by an autonomous-vehicle perception engineer — an expert who can read sensor data, perception outputs, and decision-making records the way a trucking expert reads hours-of-service logs. The safety-case documentation is produced — the written evaluation that Kodiak completed before driverless deployment, showing what the company knew about sensor limitations in dust and heat. The maintenance logs are produced — showing whether Atlas kept the SensorPods clean and calibrated in the dusty Permian Basin environment. A forensic meteorologist reconstructs the dust and visibility conditions at the time of the collision. A commercial-vehicle accident reconstructionist maps the physical evidence to the system data.
Months three through twelve. The depositions. The Kodiak safety director explains the safety case under oath. The Atlas maintenance supervisor explains the sensor-cleaning protocols. The remote-operations personnel explain their supervisory role, if any. The corporate representatives explain the decision to deploy driverless trucks in a known-hazardous operating environment. The internal communications — emails, Slack messages, testing reports, near-miss incident reports — are examined for evidence of known risks that were ignored.
The number. The number at the end is built from all of it — the system logs that show what the truck saw, the safety-case documents that show what the company knew, the maintenance records that show whether the sensors were kept clean, the medical records that show the harm, the life-care plan that shows the future cost, and the forensic economist who converts it all to a present-value dollar figure that a jury can hold in its hands. That number is the case. And that number is built from evidence that starts dying the moment the collision happens — which is why the day you call is the day the case begins.
For families dealing with a fatality, the wrongful death practice page covers the specific machinery of a Texas wrongful-death claim, including who may file and what damages are recoverable.
Frequently Asked Questions
Can I sue if a driverless truck hit me?
Yes. The absence of a human driver does not eliminate legal accountability — it shifts it to the companies that designed, deployed, and profited from the technology. The motor carrier (Atlas) remains liable as the truck owner and operator. The technology manufacturer (Kodiak) faces products-liability claims for any perception, decision-making, or control failure. The absence of a driver can actually strengthen your case by removing the comparative-fault defense that a human driver’s testimony traditionally provides.
Who is at fault when an autonomous truck crashes?
Fault is determined by the evidence — specifically, the autonomous system’s own logs, which show what the truck perceived and what decisions it made. If the system failed to perceive a hazard, the technology manufacturer may be at fault. If the carrier failed to maintain the sensors in dusty conditions, the carrier may be at fault. If both contributed, both are liable. The system logs are the objective record — they do not change their story the way a human driver’s memory might. The question can I sue for being hit by a semi truck is answered in more detail in our video resource.
How long do I have to file a lawsuit?
In Texas, you have two years from the date of the crash to file a personal-injury lawsuit, and two years from the date of death to file a wrongful-death claim. But the evidence in an autonomous-truck case — system logs, sensor data, safety-case documents — can be lost in a fraction of that time. The two-year deadline is the legal floor. The evidence clock is the real urgency. If the collision occurred on the New Mexico side of the Permian Basin, New Mexico’s statute of limitations would govern instead.
What evidence is unique to an autonomous truck case?
The Kodiak Driver autonomous system logs — sensor data, perception outputs, decision-making records, and control commands — are the single most critical evidence. These are the “driver’s testimony” in a driverless case. Additionally, the safety-case documentation that Kodiak completed before deployment, the maintenance and sensor-cleaning logs, NHTSA ADS crash reports, and any remote-operations communications logs are all evidence that does not exist in a conventional trucking case. None of this evidence has a standardized federal retention requirement, which means it can be overwritten or destroyed on the company’s own schedule unless a preservation letter freezes it.
Are the FMCSA regulations different for driverless trucks?
The FMCSA regulatory framework under 49 CFR Parts 390–399 still applies to Atlas’s driverless operations. Some provisions become inapplicable (hours-of-service logs, driver qualification files, post-crash drug testing), but the core duties — financial responsibility, vehicle maintenance, inspection — remain. The absence of a driver does not eliminate the carrier’s non-delegable duty to operate safely. NHTSA’s Standing General Order on Crash Reporting separately requires manufacturers of ADS-equipped vehicles to report crash data, creating a regulatory record that is discoverable in litigation.
What if the injured person was an oilfield worker on the job?
Two legal lanes exist. The workers’-compensation lane provides faster, no-fault benefits but is capped and bars suit against the direct employer. The third-party tort lane allows a full-damages suit against the negligent non-employer — Atlas, Kodiak, or both — and includes the human losses (pain, suffering, lost quality of life) that workers’ compensation never pays. The third-party lane is where the real recovery lives. Drawing this fork early is critical because the comp carrier may assert a lien on any third-party recovery, and the timing of both claims matters.
Can I get punitive damages in a driverless truck case?
Texas allows punitive damages upon a showing of gross negligence by clear and convincing evidence. If discovery reveals that Kodiak or Atlas had knowledge of specific autonomous-system failures, sensor-degradation issues, or near-miss incidents and continued driverless operations without remediation, the conscious disregard of a known risk supports gross negligence and punitive damages. The safety-case documentation is central to this analysis — if it acknowledges sensor limitations in Permian Basin conditions and operations proceeded regardless, the punitive-damages engine is activated.
How much is my autonomous truck case worth?
No honest attorney can answer that without seeing the medical records, the collision reconstruction, and the defendant’s insurance structure. For a fatal or catastrophic-injury collision involving a driverless Class 8 truck operated by a publicly traded carrier and a venture-backed technology company, the prospective range — based on comparable catastrophic commercial-trucking and emerging-technology product-liability verdicts — runs from approximately $1,500,000 to $25,000,000 or more, with cases involving gross-negligence findings potentially exceeding that range. The specific number is built from the medical evidence, the life-care plan, the lost-earning-capacity analysis, and the human losses that no spreadsheet can measure. Past results depend on the facts of each case and do not guarantee future outcomes.
Do I need a lawyer who understands autonomous vehicle technology?
Yes. An autonomous-truck case is not a conventional trucking case with a different fact pattern. It is a fundamentally different case that requires understanding of autonomous-vehicle perception systems, sensor-degradation science, products-liability law applied to software and AI, the NHTSA regulatory framework for automated driving systems, and the specific hazards of the Permian Basin operating environment. A lawyer who handles ordinary truck crashes but does not understand how a lidar system degrades in blowing sand, or how to demand and interpret autonomous-system logs, will leave the strongest parts of your case on the table.
Why This Firm
Ralph Manginello has spent 27-plus years in Texas courtrooms, including federal court. He was a journalist before he was a lawyer — he reads corporate press releases the way he reads evidence, looking for what is omitted. When Kodiak’s CEO calls the deployment “an incredible moment” and Atlas’s CEO calls it “a significant advancement in automation,” Ralph hears the careful framing — the language of a company managing risk perception, not the language of a company that has eliminated risk. The gap between the press release and the safety-case documentation is where the case lives.
Lupe Peña spent years inside a national insurance-defense firm. He sat in the rooms where adjusters and their valuation software — programs like Colossus — decided how to price claims. He knows how reserves are set in the first 48 hours, before the real injuries are diagnosed. He knows how IME doctors are selected. He knows the recorded-statement script. He knows the delay tactics. He now uses every one of those insights for the people the insurance machine was designed to process. Lupe is fluent in Spanish and conducts full client consultations in Spanish without an interpreter.
We handle commercial-trucking and catastrophic-injury cases across Texas, including the Permian Basin corridor through Midland, Odessa, and the surrounding production counties. We work with local counsel and pro hac vice admission where required. We do not claim an office in Midland. We do not claim to be on any specific case unless we are. What we claim is the knowledge, the experience, and the willingness to fight the companies that put 80,000 pounds of autonomous steel on a public road and then try to say nobody was responsible when it hurt someone.
If we are not the right fit for your case, we will tell you. The consultation is free. We do not get paid unless we win. The call is 1-888-ATTY-911.
If a Driverless Truck Hit Your Family
The Permian Basin is about to become the testing ground for a question no Texas jury has answered yet: when a truck with no driver kills or maims someone, who pays? The answer is the companies that built it, deployed it, and profited from it — but only if someone forces them to answer. The companies will not volunteer. The adjuster will not offer the full value. The system logs that prove what happened will not preserve themselves.
The day you call is the day the preservation letters go out. The day you call is the day the evidence stops dying and starts working for you. The day you call is the day the companies stop writing the narrative and the facts start writing it instead.
Hablamos Español. Lupe Peña conducts full consultations in Spanish without an interpreter.
The consultation is free. We do not get paid unless we win your case. The call is 1-888-ATTY-911. Ralph Manginello and Lupe Peña are ready to talk to you now.