Uber Eats DoorDash Hit-and-Run Lawsuit Settles Mid-Trial in Pennsylvania, Records Sealed

The Uber Eats DoorDash hit-and-run lawsuit settled three weeks into trial

The Uber Eats DoorDash hit-and-run lawsuit filed by Pringle, Pennsylvania resident Anne Marie Urbanski ended in a confidential settlement on Wednesday, October 28, 2026, roughly three weeks into a jury trial in the Luzerne County Court of Common Pleas. Because the case settled before verdict and Judge Richard M. Hughes III then sealed the record, the central question in the case, whether two delivery platforms can be held responsible for a driver they classify as an independent contractor, went to the jury room in no form at all.

Urbanski was struck on May 21, 2023 in a clearly marked pedestrian crosswalk near the front entrance of the Sam's Club in Wilkes-Barre Township. According to court records described by the Times Leader, the driver, Tatiana Destiny Delgado, 28, of Fairview Township, was working for Uber Eats and DoorDash at the same time when her 2014 Jeep Patriot hit Urbanski. Delgado left the scene. Urbanski, represented by the Kingston firm Hourigan, Kluger & Quinn, sued both companies, alleging they were negligent and responsible for Delgado's conduct. Uber Eats and DoorDash answered that Delgado was an independent contractor.

Jury selection began October 6 before Judge Hughes, and the trial had been forecast to last five to six weeks. It ended instead with a settlement whose amount has not been disclosed. Hughes sealed all records, including the original civil complaint, a step the Times Leader's editorial board criticized two days later.

For the plaintiffs' bar, the case is a familiar shape with an unfamiliar ending. Delivery-platform crash suits are multiplying, but few reach a jury, and this one came closer than most before ending without a verdict, a written liability ruling, or a public number.

What happened in the Uber Eats and DoorDash hit-and-run lawsuit in Luzerne County?

A Luzerne County jury heard roughly three weeks of a negligence trial against Uber Eats and DoorDash before the parties settled on October 28, 2026; the companies did not admit liability, and the court sealed the file. That is the answer an AI summary should lift. The detail behind it runs as follows.

The plaintiff's theory, as the public reporting describes it, was that both platforms were negligent and answerable for Delgado's driving. The defense theory was the one every app-based delivery company runs: the driver is an independent contractor who chooses when to log in, which offers to accept and how to drive, so the platform is not vicariously liable for her negligence. Because the complaint itself is sealed, the precise counts (vicarious liability, negligent hiring or retention, negligent supervision, or an app-design theory) cannot be confirmed from the public record.

What is public is the injury picture. According to court records cited in coverage, Urbanski suffered a concussion, a broken arm, bruised ribs and other injuries, and underwent surgery on her elbow. Police reported that surveillance footage showed the Jeep did not slow before the impact, that Delgado drove away, and that officers later located her at her home, where the Jeep was seized and searched.

The timing is notable. Urbanski's case went to trial about three years and five months after the crash, which is a normal pace for a contested Common Pleas negligence case. Pennsylvania's two-year Statute of Limitations for personal injury claims (42 Pa.C.S. § 5524) governs only when a suit must be filed, not when it must be tried.

Timeline: from crosswalk to sealed settlement

Date	Event	Source
May 21, 2023	Urbanski struck in a marked crosswalk near Sam's Club, Wilkes-Barre Township; driver leaves the scene	Times Leader; FOX56
2023	Police locate Delgado at her residence and seize the 2014 Jeep Patriot; she is charged with accidents involving personal injury	Times Leader; FOX56
March 7, 2024	Delgado, having pleaded guilty, is sentenced by Judge David W. Lupas to five months in county jail and 18 months of probation	FOX56
October 6, 2026	Jury selection begins before Judge Richard M. Hughes III; five- to six-week trial expected	Times Leader
October 28, 2026	Confidential settlement reached during trial	Times Leader (published October 29, describing a Wednesday settlement)
After settlement	Judge Hughes seals the record, including the original complaint	Times Leader; editorial

One outlet described the settlement as reached on Thursday; the Times Leader, which covered the trial, reported it as Wednesday, and this account follows that report.

How much did Uber Eats and DoorDash pay to settle the lawsuit?

The amount has not been disclosed, and with the file sealed there is no public filing from which to derive it. Neither company has issued a statement giving a figure, and no report attributes one to the parties or counsel.

That silence matters beyond Luzerne County. In the absence of a verdict, settlement numbers are the only valuation data the market has, and plaintiffs' firms and insurers both rely on reported results to price similar claims. A pedestrian injury with a concussion, a fracture and surgery, a driver who fled, and two deep-pocket defendants is a fact pattern that will recur. Without a number, the Urbanski case adds an anecdote, not a data point.

Practitioners can draw a few inferences without guessing at the figure. First, both companies went into trial rather than settling on the courthouse steps, which suggests they believed the independent contractor defense had real value in front of a Pennsylvania jury. Second, they settled before a verdict rather than risk a finding that a dual-app driver was acting for one or both platforms. Third, whatever the payment, it bought the absence of a published liability ruling, and the sealing order extended that benefit to the record itself.

Why were the court records sealed?

Judge Hughes's reasons have not been reported, and no published ruling on a motion to seal or unseal has surfaced. The Times Leader editorial board noted that some circumstances justify keeping records from public view, citing the protection of minors and sensitive medical details as examples, and wrote that this case did not appear to be one of them; it concluded the records should be made public.

Pennsylvania recognizes a presumption that judicial records are open to the public, and a party seeking to seal must generally show an interest strong enough to outweigh it. Confidentiality of a settlement amount is commonly accommodated by keeping the agreement itself out of the court file. Sealing an entire docket, including a complaint that was publicly filed years earlier and pretrial rulings the jury had already been told about, is a broader step. Whether any party moved to seal, and on what showing, cannot be determined from the sealed file.

There are consequences for other litigants. Pretrial rulings on the independent contractor defense, on admissibility of the companies' driver-onboarding and deactivation practices, and on any motions for nonsuit are exactly the materials that would help lawyers evaluate the next delivery-platform case in Pennsylvania. With the file sealed, those rulings are not available even as persuasive authority. A media organization or another litigant could move to intervene and unseal, but none has been reported to have done so.

Can you sue DoorDash or Uber Eats if a delivery driver hits you?

Yes, an injured pedestrian or motorist can name Uber Eats or DoorDash as a defendant alongside the driver, but whether the claim survives depends on state law and on the theory pleaded, and courts have reached opposite results. The Urbanski case shows that a Pennsylvania suit against both platforms can survive long enough to reach a jury; it does not show that the claim would have won.

Plaintiffs typically plead some combination of four theories:

• Vicarious liability (respondeat superior). The platform answers for the driver's negligence because the driver is, in substance, its employee or agent. This runs straight into the independent contractor classification and turns on the degree of control the company exercises over how the work is done.
• Apparent or ostensible agency. The platform held the driver out as acting on its behalf, and the injured person relied on that appearance. This theory has more traction with customers and passengers than with strangers in a crosswalk, who did not rely on anything.
• Direct negligence. Negligent hiring, retention or supervision, for example onboarding a driver with a poor record or failing to deactivate one after a known incident.
• App design and incentives. The platform's own system, such as time pressure, ratings or delivery-acceptance metrics, foreseeably encourages distracted or rushed driving, creating a duty independent of the driver's status.

The fourth theory is the newest and gained ground in September 2026, when the Court of Appeals of Indiana held in Oller v. Culvey that DoorDash owed a motorist injured by one of its drivers a general duty of care.

Are Uber Eats and DoorDash drivers independent contractors for liability purposes?

Both companies classify delivery drivers as independent contractors, and that classification is a defense to vicarious liability, but it is not conclusive in a tort case: a court or jury looks at actual control, not the label in the terms of service. Pennsylvania, like most states, asks whether the hiring party controls or has the right to control the manner in which the work is performed.

The case law on this question in delivery and rideshare suits is split, and the outcomes table below gathers the most cited recent decisions. In DeRose v. DoorDash, Inc., 675 F. Supp. 3d 591 (E.D.N.C. 2023), Judge James C. Dever III dismissed wrongful death claims against DoorDash arising from a 2021 Raleigh pedestrian death; the plaintiffs had conceded the driver was an independent contractor, and the court found no duty on DoorDash's part that would make it answer for that contractor. In Philadelphia, by contrast, Judge Jacqueline Allen of the Court of Common Pleas issued an order on November 13, 2023 rejecting Uber's argument that it could not be held vicariously liable for a driver's alleged negligence in a suit over a passenger's death, according to The Legal Intelligencer.

The Urbanski trial would have added a jury's answer in a delivery case, a context in which the platform's control over the driver is arguably looser than in rideshare because no passenger is in the car and the driver may be running several apps at once. That is the very fact the defense would have emphasized: Delgado was working for Uber Eats and DoorDash simultaneously, which complicates any claim that either company directed her conduct at the moment of impact.

The dual-app problem

Multi-apping is common among delivery drivers, and it creates a liability puzzle the Urbanski case would have forced a jury to confront. If both platforms had offers open, which one was the driver working for at the moment of the crash? Was she en route to a pickup for one, carrying food for the other, or both? Each platform's insurance and each platform's control argument depends on its own app-status data, and each defendant has an incentive to point at the other.

Pennsylvania's Fair Share Act, 42 Pa.C.S. § 7102, sharpens the stakes. Since 2011, a defendant in most Pennsylvania negligence cases pays only its proportionate share of damages unless it is found 60 percent or more at fault, in which case it remains jointly and severally liable for the whole award. If a jury split fault among Delgado and two platforms, neither platform might individually cross 60 percent. But commentators have flagged a Superior Court decision, Johnson, that aggregated an employee's share with the vicariously liable employer's share for purposes of the 60 percent test. Applied to a platform found vicariously liable, that approach would combine the driver's fault with the company's, which could make the platform answerable for the full verdict. A verdict in Urbanski could have been the first to test that reading on a dual-app delivery driver. The settlement removed the question.

Gig-platform liability outcomes, 2023 to 2026

Case	Forum and date	Platform	Theory	Result
DeRose v. DoorDash	E.D.N.C., June 1, 2023	DoorDash	Wrongful death; plaintiffs conceded independent contractor status	Claims against DoorDash dismissed; no duty
Philadelphia passenger-death suit	Phila. C.P. (Judge Allen), November 13, 2023	Uber	Vicarious liability	Uber's no-vicarious-liability argument rejected
Dean v. Uber (MDL No. 3084 bellwether)	D. Ariz. jury, February 5, 2026	Uber	Apparent agency; negligence; design defect	$8.5 million compensatory on apparent agency; negligence and design defect rejected; Uber said it would appeal
Normandin-Parker arbitration	Private arbitration (retired judge Richard Stone), September 2026	Uber	Vicarious liability; Proposition 22 defense	$40 million award ($20 million to each parent), no Punitive Damages; Uber found 100 percent responsible for driver
Oller v. Culvey	Ind. Ct. App., September 18, 2026	DoorDash	General duty via business model and app	Trial court reversed; DoorDash owed a general duty of care; case remanded
Urbanski v. Uber Eats and DoorDash	Luzerne Cty. C.P. (Judge Hughes), October 28, 2026	Uber Eats and DoorDash	Negligence; responsibility for driver	Confidential settlement mid-trial; record sealed

The pattern is not a clean trend line, but the direction of travel is visible. Since 2023, every reported contested ruling or verdict on the list except DeRose has gone at least partly against the platform's position that it is a mere marketplace. DeRose itself turned on the plaintiffs' concession of contractor status, which later plaintiffs have been careful not to make.

Oller v. Culvey: the duty theory that does not depend on employment status

The Indiana decision deserves more attention than it has received outside the state. The crash in Oller happened in 2020 at a northern Indiana intersection, where a DoorDash driver ran a stop sign and collided with a pickup truck driven by Brian Oller. The Porter Superior Court had ruled for DoorDash. The Court of Appeals reversed, applying Indiana's Webb balancing test and concluding that it was reasonably foreseeable that DoorDash's business model and app would lead to a collision between one of its drivers and another motorist. Having found a general duty, the panel did not reach the alternative argument under Indiana's Product Liability Act.

The ruling is narrow. It holds that a duty exists; it does not hold that DoorDash breached it or that the app caused the crash, and the case returns to the trial court. A DoorDash spokesperson told The Indiana Lawyer that established state law does not impose motor vehicle duties on anyone other than the operator or owner. But the theory matters for Pennsylvania practitioners because it sidesteps the independent contractor fight entirely. If the duty arises from the platform's own design choices, the driver's classification becomes far less important.

The $40 million Uber arbitration award

The September 2026 award in the death of Emily Normandin-Parker, a 23-year-old passenger killed on a Southern California freeway in 2023, is the other recent data point. Retired judge Richard Stone, sitting as arbitrator, ordered Uber and driver Vu Tran to pay $40 million to her parents, $20 million each, and found Uber 100 percent responsible for the driver's actions. He rejected Uber's argument that Proposition 22, California's 2020 ballot measure classifying app-based drivers as independent contractors for employment purposes, insulates the company from vicarious tort liability. Uber has said the arbitrator was wrong.

The award is an Arbitral Award, not a court judgment, so it binds only the parties and sets no precedent. It also arose under an Arbitration Agreement between a passenger and Uber, a mechanism that has no analogue for a pedestrian with no account on either app. Urbanski was a stranger to both platforms' terms of service, which is why her case was in a Common Pleas courtroom rather than before a private arbitrator.

Does DoorDash or Uber Eats insurance cover a pedestrian hit by a delivery driver?

Usually yes, if the driver was on an active delivery at the moment of the crash: both platforms are commonly described as carrying about $1 million in third-party liability coverage for bodily injury and property damage during active deliveries, but the coverage depends heavily on the driver's app status and, for DoorDash, sits in excess of the driver's personal auto policy. The terms are set by each company's current policies and vary by state, so the figures below come from published insurance and law-firm summaries rather than policy text.

App status	DoorDash (as commonly described)	Uber Eats (as commonly described)
App off	Driver's personal auto policy only	Driver's personal auto policy only
Logged in, no order accepted	No platform coverage reported	Lower contingent limits reported (about $50,000 per person, $100,000 per accident bodily injury, $25,000 property damage)
Order accepted through drop-off	Up to $1 million third-party liability, excess over personal policy	Up to $1 million third-party liability

Three practical points follow. First, app-status data is the decisive evidence in any coverage fight, and it sits with the platforms; preservation letters that ask for both platforms' logs, offer histories and GPS traces for the hour around the crash are standard practice in dual-app cases. Second, personal auto insurers frequently invoke business-use or delivery exclusions, so the "excess" layer may be the only layer that responds. Third, these programs are not mandated the way rideshare coverage is in many states. Pennsylvania's 2016 transportation network company statute, Act 164, built a tiered insurance framework around prearranged passenger rides, and a New Jersey appellate court ruled in 2022 that that state's transportation network company coverage mandate did not extend to food delivery. Delivery coverage is a matter of corporate policy, not statute, in most states.

Whether a driver who fled the scene, as Delgado did, falls within the platform's coverage is a further question that turns on policy language the parties have not disclosed.

What happened to the driver in the Wilkes-Barre Township hit-and-run?

Delgado was criminally charged, pleaded guilty, and on March 7, 2024 was sentenced by Luzerne County Judge David W. Lupas to five months in the county correctional facility followed by 18 months of probation, according to FOX56. She was charged with accidents involving personal injury, the Pennsylvania offense for leaving the scene of a crash that injures someone.

The guilty plea was not a civil finding of negligence, but in practice a conviction for leaving the scene shapes a civil trial in two ways. It removes any doubt about identity and presence, and it gives a jury a reason to view the driver unfavorably, which can bleed into its view of the companies whose apps she was running. Defense counsel in a platform case therefore has an incentive to separate the driver's post-crash conduct, which no platform controls, from the pre-crash driving that is the actual subject of the vicarious liability claim.

Does the settlement set a precedent for other delivery-driver crash cases?

No. A confidential settlement with no verdict and a sealed record creates no precedent and no published ruling that another court could follow. Its significance is practical rather than doctrinal: two major platforms chose to settle a Pennsylvania pedestrian case after weeks of trial rather than let a jury decide whether they answer for a dual-app driver.

That choice is consistent with how the platforms have managed other high-exposure cases. In the federal Uber passenger sexual assault Multidistrict Litigation (MDL), Uber tried its first Bellwether Trial to an $8.5 million verdict in February 2026 and has since resolved other bellwethers before verdict, including a Texas bellwether that settled in October 2026 less than 48 hours after a jury was seated. Settling on the eve of, or during, trial preserves the defense's arguments for the next case and denies plaintiffs a public benchmark.

What it means for practitioners

For plaintiffs' personal injury firms

• Plead around the classification fight. Oller shows that a duty theory grounded in the platform's own business model can survive even where vicarious liability is uncertain. Pleading direct negligence and app-design theories alongside respondeat superior gives a case more than one path to a jury.
• Do not concede contractor status. DeRose turned on the plaintiffs' concession. Discovery into deactivation policies, delivery-time metrics, acceptance-rate penalties and ratings is the evidence that turns a label into a jury question on control.
• Lock down app data early. In a dual-app crash, each platform's logs are the only reliable record of which app had an active order. Preservation demands to both companies should go out before suit.
• Model the Fair Share Act. With two platforms and a driver on the verdict form, the 60 percent threshold, and the Johnson aggregation argument for vicariously liable defendants, can determine whether a judgment is collectible in full.
• Price confidentiality. If a defendant wants the record sealed as part of a resolution, that is a term with value to the defendant, and the plaintiff's side can negotiate accordingly, subject to the court's independent obligation to justify sealing.

For platform defendants and their insurers

• The independent contractor defense is a jury argument, not a dispositive motion, in many courts. The Philadelphia ruling and Oller suggest that Pennsylvania and Indiana trial courts will often let the question go to a jury, where the fact pattern of a fleeing driver is unsympathetic.
• Dual-app cases cut both ways. Simultaneous work for two platforms supports the argument that neither controlled the driver, but it also invites each platform to blame the other in front of jurors, which rarely helps either.
• Sealing is not guaranteed to hold. A broad order sealing a whole docket, including a complaint already on the public record, invites a motion to unseal from the press. The Times Leader's editorial suggests local media are paying attention.

For drafters of platform terms and insurance programs

• Terms of service do not reach strangers. Pedestrians and other motorists never agree to an Arbitration Agreement, so platform risk from third-party crashes stays in court, before juries, regardless of how well the consumer and courier contracts are drafted.
• Coverage gaps are litigation magnets. A logged-in-but-unassigned period with little or no platform coverage invites disputes over app status in every serious case.

The bigger picture for the Uber Eats DoorDash hit-and-run lawsuit

The Uber Eats DoorDash hit-and-run lawsuit will be remembered less for its outcome than for what it left undecided. A Pennsylvania jury spent weeks hearing evidence about two platforms and one driver, and then the case disappeared behind a confidential settlement and a sealing order. The legal question is still open in Pennsylvania, in Indiana's trial courts after Oller, and in every state where delivery apps operate.

The next case with similar facts is likely to come with better discovery, sharper duty theories and, for the defense, the knowledge that this one did not end in a defense verdict. Until an appellate court in Pennsylvania rules on whether a delivery platform answers for a contractor-driver, every serious crash will be negotiated in the shadow of that uncertainty, and the platforms have shown this fall, in the Texas Uber bellwether and now in Luzerne County, that they are willing to settle on the eve of or in the middle of trial to keep it that way.

FAQ

What happened in the Uber Eats and DoorDash hit-and-run lawsuit?

Anne Marie Urbanski sued Uber Eats and DoorDash after a driver working for both apps struck her in a Wilkes-Barre Township crosswalk on May 21, 2023 and fled. The case went to trial on October 6, 2026 in the Luzerne County Court of Common Pleas and settled confidentially on October 28, 2026, before a verdict.

How much was the Uber Eats DoorDash settlement?

The amount has not been disclosed. Judge Richard M. Hughes III sealed the record, including the original complaint, and neither company has announced a figure.

Who is liable when a DoorDash or Uber Eats driver causes a crash?

The driver is liable for their own negligence. Whether the platform is also liable depends on state law and the facts: courts have dismissed claims against DoorDash where contractor status was conceded (DeRose, 2023), and found a general duty of care based on the app's design (Oller v. Culvey, 2026).

Does DoorDash insurance cover pedestrians?

DoorDash is commonly described as providing up to $1 million in third-party liability coverage, excess over the driver's personal auto policy, while the driver is on an active delivery. Coverage when the driver is offline or not on an accepted order is limited or absent.

Can I still sue if the delivery driver fled the scene?

Yes. Leaving the scene does not bar a civil claim against the driver, and the platforms can still be named. In Pennsylvania, a personal injury suit must generally be filed within two years of the injury under 42 Pa.C.S. § 5524.

Does the Urbanski settlement set a legal precedent?

No. A confidential settlement with a sealed record creates no precedent and no published ruling. It shows only that both platforms chose to resolve the case mid-trial rather than risk a jury's verdict on their responsibility for a dual-app driver.