In July 2026, a Massachusetts jury awarded $56 million to a 77-year-old man whose car was hit head-on when an Amazon-branded delivery van driver allegedly fell asleep at the wheel. The most important thing about the case is not the number. It is that, days before trial, Amazon stopped insisting the driver was “someone else’s” problem — and accepted liability. Behind that reversal is a question every catastrophic delivery-crash case turns on: when the logo on the door is a giant company, who does the law say is actually responsible?
Malcolm Carnwath was 77 years old when an Amazon-branded delivery van crossed the center line on a New Hampshire road and struck his car head-on. The van’s driver, the family alleged, had fallen asleep at the wheel. Carnwath survived, but with the kind of injuries that redefine a life: multiple strokes, a traumatic brain injury, and the amputation of a leg, leaving him dependent on around-the-clock nursing care. In July 2026, after a two-day deliberation, a jury in Middlesex Superior Court, Massachusetts returned a verdict of $56 million — reported as the largest single-plaintiff personal injury verdict in the state’s history and the largest nationwide against Amazon.
The number is what made headlines. The legal turning point came a week earlier. The driver was not an Amazon employee on paper; he worked for Agora Logistics, one of the small companies Amazon calls a “Delivery Service Partner.” For years, Amazon’s standard position in these cases has been that those companies — not Amazon — own the drivers, the vans, and the liability. Then, days before trial, Amazon filed a stipulation accepting liability “to simplify the trial and conserve judicial resources.” A company that had fought agency hard through discovery conceded the point on a public docket. That reversal, not the verdict, is the reason this case matters to anyone hurt by a delivery van. It should be said plainly at the outset: a verdict is a reported outcome in one case on its own facts, and past results never guarantee what any other case will do.
More than one party usually is. The driver is responsible for the negligent driving itself — falling asleep, speeding, running a light. The delivery company that employs the driver (in Amazon’s system, the Delivery Service Partner, or DSP) is ordinarily responsible for that driver’s on-the-job conduct and for its own decisions in hiring, training, scheduling, and supervising. And the national brand on the side of the van — Amazon, FedEx Ground, or another — can be responsible too, but only if the facts show it functioned as the driver’s principal rather than a distant customer. The label on a contract does not settle any of this. What settles it is evidence of who controlled the work.
That layered structure is not an accident. As a Capital University Law Review analysis of the DSP program explains, Amazon built a three-tier delivery workforce — DSPs, Amazon Flex gig drivers, and a small core of direct employees — in a way that keeps the corporate parent at arm’s length from the drivers who actually move the packages. For an injured person, that means the first question after a delivery crash is rarely “was the driver negligent?” It is almost always “which of these entities does the law let me hold responsible, and how do I prove it?”
The doctrine underneath all of this is respondeat superior — the rule that an employer is vicariously liable for the negligence of an employee acting within the scope of employment. The mirror-image rule is that a company generally is not liable for the acts of a genuine independent contractor. That is precisely why large companies structure delivery through intermediaries and paper the relationship as “independent.” If the label controlled, the biggest defendant would disappear from the case.
But the label does not control. Courts look to the substance of the relationship, and the central test is the right to control the manner and means of the work — the framework reflected in the Restatement (Second) of Agency § 220 and echoed across state law. The more a company dictates the details — the exact route, the number of stops per shift, the delivery windows, the app that tracks every movement, the uniform and van branding, the on-board cameras, the performance scorecards — the closer the arrangement moves to agency or employment, no matter what the paperwork says. When a company controls the pace and method of the work that tightly, the law can treat it as responsible for the harm that pace and method cause. That is the fault line Amazon chose not to litigate in front of the Carnwath jury.
The Carnwath crash reportedly began with a driver asleep at the wheel, and that detail is not incidental — it is a pattern. The National Highway Traffic Safety Administration treats drowsy driving as a serious and badly underreported crash cause, noting that fatigue degrades reaction time, attention, and decision-making in ways comparable to alcohol impairment. A driver who nods off does not brake, does not steer, and does not react; a fatigued head-on impact delivers the full, unmitigated force of both vehicles to the occupants.
In last-mile delivery, fatigue is often a system output, not just a personal failing. Routes engineered for hundreds of stops, tight delivery windows, and metrics that reward speed can push a driver to keep going past the point of safety. That is why the Federal Motor Carrier Safety Administration’s hours-of-service regime exists for commercial drivers in the first place — the same fatigue logic we cover in our explainer on truck driver hours-of-service violations. When a delivery crash traces back to exhaustion, route data, delivery timestamps, telematics, and scheduling records can show whether the driver was pressed to work impaired — evidence that speaks not only to the driver’s negligence but to the choices of the companies that set the pace.
A catastrophic delivery crash is a medical problem before it is a legal one. The Carnwath injuries — strokes, a traumatic brain injury, an amputation — are exactly the constellation that a high-energy head-on collision produces in an older occupant, and characterizing them accurately is the work of Herb Borroto, M.D., J.D., the firm’s medical-legal expert. Reading the imaging, distinguishing an acute traumatic brain injury from a stroke triggered by the trauma, and documenting why the injury pattern is consistent with an unbraked, full-force impact is a clinical judgment. It is also the answer to the defense’s favorite argument — that an older plaintiff “would have had these problems anyway” — a version of the pre-existing-condition defense we take apart in our piece on the eggshell-plaintiff rule.
On the legal side, Alex Alvarez, Managing Partner and Board Certified Civil Trial Lawyer, builds that medicine into the liability structure: proving the control that establishes agency, tracing the fatigue back to the schedule, and lining up every responsible party — driver, DSP, and brand — so that no defendant can point at an empty chair. Paired, the medical and legal work answers both halves of the case: what forces reached the body, and whose decisions put those forces on the road. That is the same evidence-first method the firm brings to the traumatic brain injury and spinal cord injury claims these crashes so often produce.
The evidence that decides a delivery-crash case is perishable. Route and telematics data, the delivery app’s timestamps, dispatch communications, the driver’s hours, and the van’s on-board camera footage can be overwritten, recycled, or simply lost on a corporate retention schedule long before a family knows to ask for them. Preserving that record early — through prompt legal notice to every entity that might hold it — is often what makes the agency and fatigue proof possible at all. We describe that race against the clock in our guide to the first 24 hours after a crash, when evidence disappears fast.
The larger lesson of the Carnwath case is the one plaintiff’s counsel voiced in hoping other lawyers would cite the docket: a national brand cannot always hide behind an intermediary’s name on a contract. Whether a company is legally an agent’s principal is a fact question about control, and it is one that can be proven. The same instinct — follow the crash to every party whose choices contributed to it — runs through our work on rideshare crashes and wrongful death alike. This article is general information about a category of injury claim, not legal or medical advice about any particular case, and the verdict discussed here is reported for context only. Past results do not guarantee similar outcomes, and every case is evaluated on its own facts.
Several parties can be responsible. The driver is responsible for the negligent driving. The Delivery Service Partner (DSP) that employs the driver is usually responsible for that driver’s on-the-job conduct and for its own hiring, training, and scheduling. And Amazon itself can be held responsible if the facts show it acted as the driver’s principal — controlling routes, delivery quotas, timing, and safety requirements closely enough that an agency relationship existed despite the independent-contractor label. Which parties are on the hook depends on the evidence of control, not on the words in a contract.
In July 2026, a Massachusetts jury in Middlesex Superior Court awarded $56 million to Malcolm Carnwath, who was catastrophically injured — multiple strokes, a traumatic brain injury, and a leg amputation — when an Amazon-branded delivery van driver allegedly fell asleep, crossed the center line on a New Hampshire road, and hit his car head-on. The van driver worked for Agora Logistics, an Amazon Delivery Service Partner. Days before trial, Amazon stipulated that it accepted liability, dropping its long-fought position that it was not vicariously responsible for the driver. The verdict is a reported case outcome and does not guarantee any result in another case.
An employer is generally vicariously liable for the negligence of an employee acting within the scope of employment, but usually is not liable for the acts of a true independent contractor. Companies use the independent-contractor label to try to place crashes on a smaller intermediary. Courts, however, look past the label to the substance of the relationship — how much the company controlled the manner and details of the work, including routes, schedules, appearance, technology, and performance metrics. When control is extensive enough, the law can treat the arrangement as an agency or employment relationship regardless of what the paperwork calls it.
Drowsy driving impairs reaction time, attention, and judgment much like alcohol, and the NHTSA identifies it as a serious, underreported crash cause. In last-mile delivery, tight quotas and long routes can push drivers past safe limits, so fatigue is not just the driver’s lapse — it can be evidence of a system that made the lapse foreseeable. Route data, delivery timestamps, telematics, and scheduling records often show whether a driver was pressed to work while impaired by exhaustion, which is central to both the driver’s negligence and any claim against the companies that set the pace.
The fatigue rules for commercial drivers — and how the records become crash evidence.
Why telematics, route data, and dispatch records have to be preserved immediately.
Answering the “they would have been hurt anyway” defense in an older-victim case.
The catastrophic head injuries a high-energy delivery-van impact can cause.
The same control-and-agency questions in the Uber and Lyft context.
When a delivery crash takes a life, the law recognizes a claim for the family.
Behind the logo on the door can be a driver, a delivery-partner company, and a national brand — and the route, telematics, and scheduling records that prove who controlled the work. Herb Borroto, M.D., J.D., reads the injury against the crash; Alex Alvarez applies the agency rules. Preserve the evidence early. Free, confidential.
Free, confidential case review. We respond within 24 hours.
No fees unless we recover compensation for you.
Your information is confidential. Submitting this form does not create an attorney-client relationship.
What Happens Next
If your information appears to qualify you for help, a lawyer or someone from their team will reach out to you. If you don't hear back within seven days, please speak with another law firm — every legal matter has a filing deadline, and waiting too long can cost you the right to recover.
