Midland Autonomous Truck Accidents: When a Driverless Semi Crashes in the Permian Basin, Who Pays?
You drive the Permian Basin roads, or someone you love does. You know what US 285 looks like at 2 a.m. — the sand haulers, the water tankers, the frac equipment moving in convoys on narrow two-lane roads with no shoulder and no light. You have been passing 80,000-pound trucks your whole life, and you know the geometry of that road well enough to know that a passenger car does not survive a collision with one. Now you have just learned that those trucks are starting to run with no human behind the wheel at all. A California technology company has put its first fully driverless Class 8 semi on the same dirt roads and ranch-to-market routes that the Texas Department of Transportation already calls the deadliest stretch of highway in the state. No crash has been reported yet. That word “yet” is what brought you here. We are Attorney911 — The Manginello Law Firm — and this page is the complete legal and evidence framework for what happens when the first autonomous truck crash occurs in the Permian Basin. We wrote it because the day that truck hits someone, the clock on the evidence starts in hours, not weeks, and the company that built the AI will control the data that proves what went wrong. You need to know what that clock looks like before it starts ticking.
What Just Happened in West Texas — and Why It Changes Everything
A California-based autonomous-vehicle technology company called Kodiak Robotics announced it had completed its first fully driverless commercial truck delivery — transporting frac sand for Atlas Energy Solutions through the Permian Basin in West Texas. The route ran through dirt roads in a region characterized by extreme heat, dust storms that can reduce visibility to near-zero, and a traffic-mix that puts 80,000-pound commercial haulers on the same unimproved roads as passenger vehicles with no separation. The company plans to deploy two additional purpose-built trucks with its latest hardware into Atlas’s commercial fleet operations by early 2025.
This is not a test run. This is the transition from testing to commercial operations. The trucks that ran with safety drivers behind the wheel for years are now running with no human in the cab at all, on public roads, for paying customers, in a region that the Texas Department of Transportation identifies as disproportionately lethal.
The Texas Department of Transportation states that the Permian Basin accounted for 7% of all traffic fatalities in Texas in 2021, despite housing less than 2% of the state’s entire population.
That statistic is not background color. It is the foreseeable-harm foundation of every future crash case involving these trucks. A company that chooses to deploy fully autonomous 80,000-pound vehicles on roads that are already this dangerous has made a decision about acceptable risk — and when that risk materializes, the question is whether the company understood the danger and deployed anyway.
The Permian Basin: The Deadliest Roads in Texas
The Permian Basin spans much of West Texas — Reeves, Loving, Ward, Winkler, Ector, Midland, and Pecos counties. It is one of the most heavily trucked oilfield corridors in North America. US Highway 285, which bisects the Delaware Basin portion, has been characterized by safety advocates as one of the most dangerous roads in America. The convergence is lethal: 80,000-pound sand haulers, water tankers, and frac equipment transports on narrow, often unimproved roads with minimal shoulders and no lighting. Dust storms routinely reduce visibility to near-zero. The 24-hour nature of fracking operations produces chronic driver fatigue in human-operated trucks. The dirt lease roads and ranch-to-market routes that connect well pads to sand mines are unimproved, lack traffic control devices, and are shared by passenger vehicles with no separation.
TxDOT has invested in corridor safety improvements on key Permian routes, but the fundamental geometry and traffic-mix hazards remain. Now add to that mix a fully autonomous 80,000-pound truck whose perception system was trained primarily on the Dallas-Houston corridor — an interstate highway environment that looks nothing like a West Texas dirt road at midnight during a dust event.
This is the core design-defect theory that any future crash case will turn on: was the autonomous driving system adequate for the environment it was deployed in? The Permian Basin is not Interstate 45 between Dallas and Houston. It is unimproved roads, mixed traffic, dust, glare, and geometry that the system’s training data may not adequately cover. When a technology company tests on one road and deploys on another, the gap between those environments is the liability.
If you or someone in your family has been hurt by any commercial truck in the Permian Basin — autonomous or not — the same road conditions, the same corporate structures, and the same evidence clocks apply. We handle 18-wheeler accident cases across Texas, and our Permian Basin oilfield truck accident practice is built specifically for the roads and the industry that run through Midland, Odessa, Pecos, and the surrounding counties.
The Defendant Stack: Four Companies Between You and the Money
When a conventional truck crashes, the defendant structure is already complex — the carrier, the leasing company, the broker, the insurance company. When a driverless truck crashes, the structure multiplies. Here are the entities that could be on the hook when a Kodiak-equipped autonomous truck hurts someone in the Permian Basin:
Kodiak Robotics — the autonomous system designer and integrator. Kodiak is a technology company, not a traditional motor carrier. It was founded in 2018 and is headquartered in Mountain View, California. Its Kodiak Driver system is an autonomous driving stack purpose-built for Class 8 long-haul trucks, currently on its sixth-generation hardware platform with integrated sensor-pod architecture. The company holds partnerships with both commercial entities and the US Army for defense applications. In any future crash, Kodiak would face product-liability and technology-negligence theories as the designer, integrator, and updater of the autonomous driving system that controls the vehicle’s perception, decision-making, and actuation. Its deep-pocket status as a venture-backed technology firm with defense contracts makes it a primary target.
Atlas Energy Solutions — the fleet operator and cargo owner. Atlas is a publicly traded frac sand supplier (NYSE: AESI) serving oil and gas operators across the Permian Basin. The company mines, processes, and transports proppant sand to well sites via its own logistics network. As the entity deploying the trucks into its commercial fleet and directing their routes and cargo operations, Atlas would face negligent operation, negligent fleet management, and vicarious liability theories. As a publicly traded company, its pocket depth and insurance stack are significant.
The unidentified motor carrier of record. This is the critical question that drives the entire insurance analysis: which entity holds the FMCSA operating authority for these driverless trucks? Is it Kodiak as the technology provider? Is it Atlas as the fleet operator and cargo owner? Or is it a third-party carrier operating under a service agreement? This determination drives MCS-90 applicability, minimum financial responsibility requirements, and the identity of the named insured on the primary commercial auto policy. The corporate separation between the AI system designer (Kodiak) and the fleet operator (Atlas) creates a layered defendant profile that would need to be unrolled through discovery.
The truck OEM and chassis manufacturer. The underlying Class 8 truck platform manufacturer could face product-liability claims if a crash involves a mechanical or braking-system failure rather than a perception or decision failure by the autonomous stack. This is the “was it the software or the hardware” question, and the answer determines which defendant theory leads.
The generalist lawyer files a complaint against the trucking company and stops. The lawyer who understands autonomous-vehicle litigation files against the technology company, the fleet operator, the carrier of record, and the chassis manufacturer — because each one controls a different piece of the evidence and carries a different layer of insurance. Missing one can leave money on the table that the family will never recover.
Texas Autonomous-Vehicle Law: The AI Is the “Operator”
Texas enacted autonomous-vehicle legislation that designates the automated driving system as the “operator” of the vehicle when it is engaged. This is not a technicality. It fundamentally changes the liability framework for any crash involving a driverless truck in Texas.
In a conventional truck crash, the liability framework is built around the human driver’s negligence — was the driver speeding, fatigued, distracted, following too close? The employer is vicariously liable under respondeat superior. When the driver is a machine, that entire framework shifts. The “operator” is the automated driving system, which means the negligence inquiry moves from the human to the company that designed, built, tested, updated, and deployed that system.
This shift pushes the case toward product liability — design defect, manufacturing defect, failure to warn — and technology-negligence theories. The argument becomes: was the autonomous driving system unreasonably dangerous in its design, particularly its ability to perceive and respond to hazards on unimproved oilfield roads where dust, irregular geometry, and mixed traffic create edge cases the system’s training data may not adequately cover?
Texas follows a modified comparative negligence rule with a 51% bar, meaning a plaintiff who is 51% or more at fault cannot recover damages. In an autonomous-truck case, the comparative-fault analysis gets interesting — the defense will try to pin fault on the other driver, the road conditions, even the weather. But when there is no human driver in the truck to attribute fault to, the comparative-fault calculus shifts. The technology company and the fleet operator become the primary targets for fault allocation.
Texas imposes no caps on non-economic or punitive damages in standard personal-injury and wrongful-death cases arising from commercial vehicle crashes. This distinguishes Texas from states with tort-reform caps that would limit what a jury can award for pain, suffering, mental anguish, loss of companionship, or punishment. In an autonomous-truck case, the absence of those caps matters enormously — a jury that finds the technology company deployed a system it knew was inadequately tested for Permian Basin conditions can award the full measure of human loss without a statutory ceiling cutting it down.
Federal Regulations and the Driverless Gap
FMCSA regulations under 49 CFR Parts 390 through 399 govern commercial motor vehicle operations and apply to interstate freight movements regardless of whether a human driver is present. These rules cover vehicle maintenance, cargo securement, minimum financial responsibility, and recordkeeping. The MCS-90 endorsement requires interstate motor carriers to maintain minimum financial responsibility of $750,000 for general freight, $1,000,000 for oilfield hazardous-materials transport, and $5,000,000 for certain hazmat.
But here is the gap: the federal regulatory framework was written for human drivers. FMCSA’s Hours-of-Service regulations, driver-qualification requirements, and drug-testing rules all presuppose a person behind the wheel. When no human driver exists, which rules still apply? The question is unsettled. The FMCSA has not issued comprehensive regulations for autonomous commercial vehicles. This regulatory uncertainty is itself a liability argument — a company deploying driverless trucks on public roads without clear regulatory guidance is operating in a gray zone, and the decision to deploy anyway is a corporate choice a jury can evaluate.
NHTSA’s Standing General Order requires manufacturers of automated driving systems to report crashes involving Level 2+ systems, creating a potential public-record data source for prior incidents. This means if a Kodiak-equipped truck has been in any prior crash or near-miss anywhere in the country, that report may exist in a federal database — evidence of notice, pattern, and potentially punitive damages.
Texas’s autonomous-vehicle statute permits driverless operation on public roads under defined conditions, but the federal-state regulatory overlap for autonomous commercial vehicles remains unsettled. The practical reality is that a company can deploy driverless trucks in Texas today, and the first comprehensive regulatory framework will likely be written in response to the first catastrophic crash — not before it.
For a deeper dive into the federal trucking regulations that still apply even when the driver is a machine, our commercial truck accident guide walks through the FMCSA framework in plain language.
The Evidence That Disappears in Days — Not Months
This is the section that matters more than any other. When a conventional truck crashes, the evidence-preservation clock runs in months — driver logs can be legally destroyed after six months under 49 CFR 395.8(k), and the truck’s engine computer data can overwrite itself when the truck is put back on the road. When an autonomous truck crashes, the evidence-preservation clock runs in days, and sometimes hours, because the data that proves what the AI perceived and decided is stored on systems the technology company controls — systems designed to cycle and overwrite.
Here is the evidence that exists after an autonomous truck crash, who holds it, and how fast it can legally die:
Autonomous driving system data logs — perception outputs, decision traces, disengagement events, sensor-fusion records. This is the central causation evidence in any autonomous-vehicle crash. These logs prove what the AI system perceived, what decisions it made, and whether it identified the hazard in time. Telematics and autonomous-system logs may be overwritten within days or weeks depending on the technology company’s data-retention configuration. No federal mandate currently requires long-term retention of Level 4 autonomous driving data. The company that designed the system controls the servers, and the company decides how long the data lives.
Kodiak Driver software version history and over-the-air update logs. These records establish which software version was running at the time of the incident, whether known bugs or perception limitations had been identified internally, and whether patches were available but not deployed. Update logs may be maintained on the technology company’s cloud infrastructure indefinitely, but correlating a specific truck’s running version to a specific moment in time requires an immediate preservation demand — before the company can argue the version was updated and the historical record is no longer retrievable.
Vehicle telematics, GPS breadcrumb data, and speed, braking, and steering records. These reconstruct the vehicle’s speed, path, braking input, and steering commands in the seconds before impact — the autonomous system’s actuation outputs. Telematics platforms typically retain high-resolution data for 30 to 90 days before degrading to summary records. After 90 days, the second-by-second truth is replaced by a spreadsheet average, and the reconstruction engineer’s ability to prove what the truck actually did in the final seconds is gone.
Dashcam and sensor-pod video and image captures. The visual record of what the truck’s cameras and sensors captured in real time is critical for both causation and jury presentation. Onboard storage may overwrite within hours to days depending on the loop configuration. Cloud-uploaded clips may persist longer but depend on the technology company’s upload triggers — if the system did not flag the event as significant, the clip may never have been uploaded at all.
Atlas dispatch records, route assignments, and cargo loading documentation. These establish who directed the truck onto the specific route, what cargo was being hauled, whether weight limits were observed, and whether any route-risk assessment was conducted before the truck was sent onto unimproved Permian Basin roads. Dispatch records are typically retained per company policy but may be subject to routine destruction schedules.
Remote monitoring and teleoperations center records and staffing logs. If the technology company or the fleet operator maintains a remote-monitoring center where humans can intervene in the autonomous system’s operation, the staffing levels, response times, and intervention protocols are critical to liability. If a human operator was supposed to be monitoring the truck and was understaffed, distracted, or slow to respond, that is a direct negligence theory against the monitoring company. Real-time intervention logs could be overwritten quickly — potentially on the same short cycles as the autonomous driving data.
NHTSA Standing General Order crash reports. These are a public-record source of prior crashes or near-misses involving the same autonomous platform. They support notice, pattern, and punitive damages arguments. But these public filings may lag months behind incident dates, so establishing a baseline before any future incident positions counsel to detect prior incidents quickly.
FMCSA motor carrier registration, MCS-90 filings, and safety fitness records. These are public records that identify who holds operating authority, what insurance is in place, and whether the carrier has a history of regulatory violations. The identity of the carrier of record for autonomous operations may not be immediately clear and requires investigation — but the records themselves are durable.
The single fastest-dying source in an autonomous-truck crash is the sensor-pod video and the autonomous driving system’s real-time perception logs. These can be gone in days. The preservation letter that saves them has to go out the day you call — not the week after, not the month after, not when the family has had time to grieve and think about it. The day you call.
When a defendant lets required evidence die after receiving a preservation demand, the law answers. Texas courts can impose an adverse-inference instruction — meaning the jury may be told to assume the lost record was as bad for the defendant as the plaintiff says it was. Sanctions are available. In some circumstances, the destruction itself becomes a separate claim. The leverage begins the moment the preservation letter is on file. But it has to be on file before the data cycles.
What an 80,000-Pound Driverless Truck Does to a Human Body
A fully loaded Class 8 truck weighs up to 80,000 pounds. A passenger vehicle weighs about 4,000. That is a 20-to-1 weight disparity. In a collision between the two, the people in the smaller vehicle absorb a disproportionate share of the violent change in motion — the delta-V — which is the single best predictor of occupant injury severity. According to the Insurance Institute for Highway Safety, large trucks often weigh 20 to 30 times as much as passenger vehicles, and in fatal crashes involving large trucks, about two of every three people killed are not in the truck — they are in the other vehicle.
The injuries an 80,000-pound truck inflicts on a human body in a high-speed collision are catastrophic by physics, not by chance. The destructive energy in a crash increases with the square of the speed — double the speed and the energy quadruples. A truck moving at 65 miles per hour carries enormous kinetic energy that has to be absorbed in the fraction of a second it takes for the vehicles to deform and stop.
The damage pattern typically includes traumatic brain injury — the brain slamming against the inside of the skull as the head whips forward and stops, producing microscopic tearing of nerve fibers that a standard CT scan was never designed to see. Spinal cord injury — the vertebrae fracturing or dislocating under deceleration forces, damaging the cord and producing paralysis whose severity depends on where on the spine the injury sits. Crush injuries and amputation — the passenger compartment collapsing into the occupant’s space, trapping and crushing limbs. Thermal burns — if the fuel system ruptures and the crash ignites, which federal safety standards are specifically written to prevent but which still happens.
For catastrophic injuries like these, the damages are measured over a lifetime, not a hospital stay. A spinal cord injury at the cervical level can cost more than a million dollars in the first year alone and several million across a lifetime — and that figure deliberately excludes every lost paycheck. A severe traumatic brain injury can mean a lifetime of attendant care, lost earning capacity, and recurring medical treatment. A wrongful death means the family loses the financial support, the household services, and the companionship of the person who was killed.
When the truck that caused these injuries was being driven by a computer, not a human, the defense cannot argue that the driver was experienced, careful, or properly trained. There was no driver. The question becomes whether the company that built the computer, and the company that deployed it on those roads, are responsible for what the computer did — and the answer under Texas law is yes.
For families who have lost someone, we handle wrongful death claims with the full weight of our firm’s resources and experience.
The Insurance Tower: Where the Money Actually Sits
A regular freight carrier is required by federal law to carry at least $750,000 in coverage. An oilfield hazardous-materials hauler must carry $1,000,000. A carrier hauling the most dangerous hazmat in bulk must carry $5,000,000. These are federal floors — the regulatory minimum, not the ceiling.
But an autonomous truck case does not run on the carrier’s policy alone. The defendant stack includes a venture-backed technology company with defense contracts and a publicly traded fleet operator. Each of those entities carries its own insurance, and the coverage layers stack — the carrier’s primary policy, the technology company’s product-liability coverage, the fleet operator’s commercial auto and general liability, excess and umbrella layers above each, and potentially a self-insured retention that means the company’s own dollars sit on the first layer of any claim.
The critical insurance and regulatory question is which entity holds FMCSA operating authority for these driverless trucks. That determination drives MCS-90 applicability, minimum financial responsibility requirements, and the identity of the named insured on the primary commercial auto policy. If Kodiak holds the authority, the technology company’s insurance is the primary layer. If Atlas holds it, the fleet operator’s tower leads. If a third-party carrier is the carrier of record, that carrier’s MCS-90 endorsement triggers minimum financial responsibility obligations — and the technology company and fleet operator sit behind it with their own coverage.
Knowing which policies exist, in what order they pay, and what exclusions each policy contains is half the value of the case. The other half is proving the liability that triggers those policies. An insurer whose policy contains an exclusion for autonomous-vehicle operations — or whose coverage was written before anyone contemplated driverless trucks — will fight coverage as hard as it fights liability. That coverage fight is its own case, and it requires a lawyer who understands both the trucking regulatory framework and the technology company’s corporate structure.
The Insurance Adjuster’s Playbook — and Our Counter to Each Move
Lupe Peña spent years inside a national insurance-defense firm before he joined this firm. He sat in the rooms where adjusters and their software decided how to deny, delay, and devalue people exactly like the reader. He knows how the reserve is set in the first 48 hours, how the recorded-statement call is engineered, and how the claim is fed into valuation software that discounts pain it cannot see. Here are the plays the insurer will run in an autonomous-truck case, and what we do about each one:
Play 1: “The technology has a perfect safety record — this was a rare, unavoidable edge case.” The company will frame any crash as a statistical anomaly, a one-in-a-million event that no system could have prevented. The counter is the evidence the company generated before the crash — its own testing logs, its disengagement reports, its internal communications about known perception limitations in dust or mixed-traffic environments. If the company knew its system struggled with the exact conditions that caused the crash and deployed anyway, the “rare edge case” framing collapses. The NHTSA Standing General Order database may contain prior incident reports involving the same platform. The technology company’s own beta-test data from the Dallas-Houston corridor may show disengagement events in conditions similar to the crash scenario.
Play 2: The quick settlement check with a release attached, before the autonomous-system data is preserved. In a conventional truck case, the insurer’s first offer often arrives before the MRI results do. In an autonomous-truck case, the first offer will arrive before the perception logs are preserved — because the company knows that once the family signs a release, the data’s destruction is immune from consequence. The counter is timing: the preservation letter goes out the day you call, before any conversation with the insurer, and certainly before any check is accepted. No release is signed until the full system-log analysis is complete and the family understands what the AI actually saw and did in the seconds before impact.
Play 3: The recorded statement that sounds like a check-in. 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 later. In an autonomous-truck case, this call may come from the technology company’s claims team, the fleet operator’s insurer, or both. The counter is simple: do not give a recorded statement without counsel. The insurer’s representative is not your friend. The recording is built to minimize the claim. Every word you say will be transcribed, taken out of context, and used to reduce what the company pays.
Play 4: “The other vehicle was at fault — comparative negligence.” The defense will try to pin fault on the injured party — you were speeding, you changed lanes without signaling, you were in the truck’s blind spot. Texas’s 51% bar means every percentage point of fault they can pin on you reduces your recovery, and if they reach 51%, you recover nothing. In an autonomous-truck case, this argument is harder for the defense because there is no human truck driver to testify about what happened — but the technology company will use the truck’s own sensor data to reconstruct the other vehicle’s movements and argue the AI responded appropriately. The counter is an independent reconstruction using the same data the company holds, analyzed by experts who work for the plaintiff, not the defendant.
Play 5: Trade-secret protection to block access to the software and training data. The technology company will assert that its software source code, training data, and system architecture are protected trade secrets that cannot be disclosed in litigation. This is the single most fiercely contested discovery issue in autonomous-vehicle litigation. The counter is a protective order that allows the plaintiff’s independent experts to analyze system logs and performance data without requiring access to the raw source code — the logs show what the system did, and that is often enough to prove causation without needing the code itself.
Play 6: The “we need more time” delay aimed at the statute of limitations. Texas gives you two years from the date of the injury or death to file a personal injury or wrongful death lawsuit, under the Texas Civil Practice and Remedies Code’s statute of limitations. The insurer knows this deadline. The strategy is to keep the family talking, keep the negotiation “ongoing,” and let the clock run until the filing window closes. The counter is a firm that files the lawsuit when it needs to be filed — not when the insurer has finished using delay as a weapon.
How an Autonomous-Truck Case Is Built
Here is how a case like this is actually won, from the first phone call through the number at the end:
The preservation demand goes out in week one — freezing the autonomous-system data logs, the software version history, the sensor-pod captures, the telematics, the dispatch records, the remote-operations center records, and the NHTSA crash-report filings. This letter goes to the technology company, the fleet operator, the carrier of record, the truck OEM, and every third-party data vendor involved in the autonomous system’s operation. Each one gets a separate letter, because each one controls a different piece of the evidence.
The truck is inspected before it can be “serviced” or returned to the road. The physical evidence — the sensor pods, the braking system, the tires, the collision damage pattern — is photographed, measured, and documented by independent experts. In a conventional truck case, the truck might go back on the road within weeks. In an autonomous-truck case, the technology company may want to pull the data and then deploy the truck elsewhere — and the preservation demand is what stops that from happening.
The experts are retained early. An autonomous-truck case requires a different expert team than a conventional truck crash: an autonomous-systems engineer who understands how perception systems process sensor data and make driving decisions; a machine-learning and perception specialist who can evaluate whether the system’s training data was adequate for the deployment environment; a commercial-truck crash reconstructionist who understands autonomous actuation — how the system’s commands translate into physical braking and steering; and a human-factors expert who can address the absence of a human driver in the avoidance calculus and the role of any remote-monitoring personnel.
Discovery is fought on the software and training-data fronts. The technology company will assert trade-secret protections, requiring protective-order negotiation that balances the company’s legitimate intellectual-property concerns against the plaintiff’s right to understand what the system did and why. The independent experts analyze system logs without needing raw source access — because the logs, the decision traces, and the sensor-fusion records tell the story of what the AI perceived and what it chose to do about it.
The depositions are where the safety director, the software engineers, and the fleet managers explain the company’s choices under oath. When did the company know its system had limitations in dust conditions? What testing was done on unimproved roads before commercial deployment in the Permian Basin? What route-risk assessment, if any, was conducted before the truck was sent onto dirt lease roads? Was the remote-monitoring center adequately staffed? Were there prior disengagement events or near-misses that should have stopped the deployment?
The number at the end is built from all of it — the life-care plan that prices out every surgery, every therapy session, every wheelchair, every caregiver hour, every lost paycheck, across a full lifetime; the forensic economist who reduces that cost stream to present value; the human losses that no spreadsheet can price but a Texas jury can, with no statutory cap to cut the number down.
The First 72 Hours: A Roadmap
If you or someone in your family has been hurt by a commercial truck in the Permian Basin — autonomous or conventional — here is what the first 72 hours look like:
Medical first, and document everything. Symptoms lie. A person who walks away from a truck crash may have a brain injury that does not show up on a CT scan for days. A “mild” traumatic brain injury can come with a perfectly normal initial scan — that is the standard presentation, not the exception. Get to the emergency room. Get the MRI. Get the neuropsychological evaluation if cognitive symptoms appear. Keep every record, every appointment, every prescription.
Do not give a recorded statement to any insurance company. Not the trucking company’s insurer, not the technology company’s claims team, not the fleet operator’s representative. The call will sound friendly. It is not. Every word will be transcribed and used to reduce what the company pays.
Do not sign anything. A check may arrive fast, with a release attached, before the full medical picture is clear. Signing a release before the injuries are diagnosed and before the autonomous-system data is preserved is the single most common way a family loses the full value of a catastrophic case.
Do not post on social media. The insurer will be watching. A photo of you at a family event will be used to argue your injuries are not as serious as you claim. A comment about the crash will be taken out of context. Silence is protection.
Preserve the vehicle. If your vehicle was damaged, do not let it be repaired, sold, or scrapped until it has been inspected by experts. The physical evidence of the collision — the impact pattern, the crush zones, the paint transfer — is part of the reconstruction.
Call a lawyer who understands autonomous-truck litigation. The preservation letter that saves the autonomous-system data has to go out in days, not weeks. The technology company controls the servers. The data is on a clock. The day you call is the day the clock starts working for you instead of against you.
What a Case Like This Is Worth
No two cases are the same, and the value of any specific case depends on the facts — the severity of the injuries, the clarity of liability, the comparative-fault allocation, the available insurance coverage, and whether the defendant’s conduct rises to the level that supports punitive damages. But the framework for valuing a catastrophic autonomous-truck case in the Permian Basin can be stated honestly:
In a catastrophic-injury or wrongful-death matter involving a driverless Class 8 truck on Permian Basin roads, the exposure would likely range from $5,000,000 to $30,000,000 or more, driven by the 80,000-pound vehicle mass, the deep-pocket defendant stack — a venture-backed technology company plus a publicly traded fleet operator plus insurers — Texas’s absence of non-economic damage caps in commercial-vehicle cases, and the potential gross-negligence aggravators if prior testing limitations were known before deployment.
Punitive damages would be available upon a showing of gross negligence, malice, or fraud — a threshold that prior knowledge of autonomous-system limitations combined with deployment on known-dangerous roads could potentially meet. If the technology company knew its system struggled with dust conditions or unimproved-road perception and deployed in the Permian Basin anyway, that knowledge-plus-decision pattern is the raw material of a punitive-damages argument.
In Texas, when liability becomes clear and damages exceed policy limits, a Stowers demand letter to the insurer creates a duty to settle within those limits and exposes the carrier to bad-faith liability for refusal. This is a powerful tool — especially where the defendant stack includes a technology company whose own insurer may be unfamiliar with catastrophic trucking exposure and may not understand the risk of trying a case that a Texas jury could punish severely.
Actual value depends on liability clarity, comparative-fault allocation, the specific injury profile, and whether the Stowers duty is triggered by clear liability exceeding available policy limits. Past results depend on the facts of each case and do not guarantee future outcomes.
Frequently Asked Questions
Can I sue if a driverless truck hit me in Midland?
Yes. Texas law designates the automated driving system as the “operator” of the vehicle when it is engaged, which means the liability framework shifts from the human driver to the company that designed, built, and deployed the system. You can sue the technology company that made the autonomous driving system, the fleet operator that deployed the truck on the road, the motor carrier of record that holds the federal operating authority, and potentially the truck manufacturer if a mechanical failure contributed to the crash. The right defendant is not always obvious — identifying who holds FMCSA operating authority for a driverless truck is the first investigative step.
Who is liable when an autonomous truck crashes in Texas?
Liability depends on what caused the crash. If the autonomous driving system failed to perceive a hazard, made a bad driving decision, or executed an inadequate avoidance maneuver, the technology company that designed and integrated the system faces product-liability and technology-negligence theories. If the fleet operator deployed the truck on a route it should have known was unsafe for the system’s capabilities, the fleet operator faces negligent operation and negligent fleet management theories. If the truck had a mechanical failure — brakes, steering, tires — the chassis manufacturer or maintenance provider may be liable. In most crashes, multiple defendants share the fault, and the discovery process is how that allocation is proven.
How long do I have to file a lawsuit for an autonomous truck accident in Texas?
Texas gives you two years from the date of the injury or death to file a personal injury or wrongful death lawsuit, under the Texas Civil Practice and Remedies Code’s statute of limitations. Two years sounds like a long time, but the evidence in an autonomous-truck case — the sensor data, the perception logs, the video captures — can be legally destroyed in days or weeks. The deadline to sue is two years. The deadline to save the evidence is measured in days. Those are two very different clocks, and the second one is the one that actually decides the case.
What evidence disappears fastest after a driverless truck crash?
The autonomous driving system’s real-time perception logs and the sensor-pod video captures are the fastest-dying evidence. Depending on the technology company’s data-retention configuration, these records can be overwritten within days or weeks. No federal mandate currently requires long-term retention of Level 4 autonomous driving data. The technology company controls the servers, and the company decides how long the data lives. A preservation letter from a lawyer — sent the day you call — is the only thing that stops the clock. Without it, the single most important proof of what the AI perceived and decided can be legally erased before anyone asks for it.
Does Texas have damage caps for commercial truck accident cases?
No. Texas imposes no caps on non-economic or punitive damages in standard personal-injury and wrongful-death cases arising from commercial vehicle crashes. This means a jury can award the full measure of human loss — pain and suffering, mental anguish, loss of companionship, disfigurement — without a statutory ceiling cutting the number down. Punitive damages are also uncapped, though they require a showing of gross negligence, malice, or fraud. This distinguishes Texas from states with tort-reform caps and is one of the reasons autonomous-truck cases in Texas have potentially higher exposure than the same crash in a capped state.
What if I was partly at fault for the crash?
Texas follows a modified comparative negligence rule with a 51% bar. Your recovery is reduced by your percentage of fault, and if you are 51% or more at fault, you cannot recover anything. In an autonomous-truck case, the defense will try to pin fault on you — you were speeding, you changed lanes, you were in the truck’s path. But when there is no human truck driver to testify about what happened, the comparative-fault calculus shifts. The technology company and the fleet operator become the primary targets for fault allocation, and the system’s own sensor data — if preserved — is the evidence that shows what actually happened. Every percentage point of fault the defense tries to pin on you is money, and fighting that allocation is central to the case.
How much does it cost to hire an autonomous truck accident lawyer?
Nothing upfront. We work on contingency — 33.33% before trial and 40% if the case goes to trial. We do not get paid unless we win your case. The consultation is free. The preservation letter goes out at our cost. The experts are retained at our cost. The investigation is funded at our cost. If there is no recovery, you owe us nothing. If there is a recovery, our fee comes out of that recovery, and the percentage is agreed upon before we begin.
What makes an autonomous truck case different from a regular truck accident case?
Three things. First, the defendant stack is different — you are suing a technology company, not just a trucking company, and the technology company has its own insurance, its own corporate structure, and its own incentives to protect its intellectual property. Second, the evidence is different — instead of driver logs and hours-of-service records, you are fighting for perception data, decision traces, and sensor-fusion logs that the technology company controls and that can disappear in days. Third, the liability theory is different — instead of driver negligence, the case turns on product liability and technology negligence, which requires expert witnesses who understand autonomous systems, machine learning, and AI perception in a way that conventional truck-crash reconstructionists do not. A lawyer who handles conventional truck crashes but has never litigated an autonomous-vehicle case may not know what evidence to demand, what experts to retain, or what discovery battles to fight.
Why This Firm
Ralph Manginello has spent 27 years in Texas courtrooms, including federal court in the Southern District of Texas. He was a journalist before he was a lawyer — he knows how to find the story the company does not want told, and he knows how to tell it to a jury in plain language. He is a competitor who hates losing, and that is not a marketing line — it is the disposition that drives every case this firm takes. Ralph is admitted to practice in Texas state courts and the U.S. District Court for the Southern District of Texas, and he has been licensed since November 6, 1998.
Lupe Peña spent years inside a national insurance-defense firm before he joined this firm. He sat in the rooms where adjusters and their software decided how to deny, delay, and devalue people exactly like the reader. He knows how the reserve is set in the first 48 hours, how the recorded-statement call is engineered, how the IME doctor is selected, how surveillance works, and how the claim is fed into valuation software like Colossus that discounts pain it cannot see. Now he uses that knowledge for injured clients. Lupe is a third-generation Texan with family roots to the King Ranch, born and raised in Sugar Land, and he is fluent in Spanish — he conducts full client consultations in Spanish without an interpreter.
We are Attorney911 — The Manginello Law Firm, PLLC. We have recovered more than $50 million for our clients over more than two decades of practice. We have a 4.9-star rating with more than 251 Google reviews. We answer our phones 24 hours a day, seven days a week — live, not an answering service. We send preservation letters the same day we are hired. We have been in business since July 18, 2001. Our offices serve Houston, Austin, and Beaumont, and we take commercial-vehicle, catastrophic-injury, and wrongful-death cases across Texas, including the Permian Basin.
Past results depend on the facts of each case and do not guarantee future outcomes.
If a driverless truck has hurt you or someone you love in the Permian Basin — or if you drive these roads and want to know what your rights are before that day comes — call us. The consultation is free. The call is confidential. There is no fee unless we win your case. The number is 1-888-ATTY-911 — 1-888-288-9911. Someone will answer.
Hablamos Español. Lupe conducts full consultations in Spanish, and our bilingual staff serves your family in the language you pray in.
The autonomous trucks are already on the road in West Texas. The first crash has not been reported yet. When it happens, the evidence will start disappearing in days. The day you call is the day the clock starts working for you instead of against you.