Columbus Gig Accidents: Ohio HB 33 Changes for 2026

The recent surge in demand for rapid delivery services has unfortunately led to a corresponding increase in commercial vehicle incidents, particularly involving gig economy drivers. A recent truck accident in Columbus involving an Amazon Flex driver highlights the complex legal landscape surrounding these incidents, especially with a significant legal development impacting how victims can seek compensation. Are you prepared for how these changes could affect your claim?

Ohio House Bill 33: A Game-Changer for Gig Economy Accident Claims

As an attorney who has spent years representing clients injured in collisions, I can tell you that Ohio’s legal framework for rideshare and gig economy accidents just got a lot more intricate. Effective January 1, 2026, Ohio House Bill 33 (HB 33) has fundamentally reshaped how liability is assessed when a driver operating under a transportation network company (TNC) or a delivery network company (DNC) is involved in a crash. This legislation, codified primarily under Ohio Revised Code (ORC) Section 3939.05, aims to clarify the insurance obligations and liability of these companies, a topic that has been a continuous battleground in courtrooms nationwide. We’ve seen similar legislative efforts in other states, but Ohio’s approach presents its own unique challenges.

Prior to HB 33, determining liability for a gig economy driver accident was often a convoluted process, heavily reliant on common law principles of agency and employment, which were not always a neat fit for the independent contractor model. Now, the law provides a more structured, albeit complex, framework. The core change is a clearer delineation of when a DNC or TNC can be held directly liable for an accident. The burden of proof has, in some respects, shifted, requiring victims to precisely establish the driver’s operational status at the moment of impact. This isn’t just a minor tweak; it’s a significant reorientation of how we approach these cases.

Injured in an accident?

Know what your case is worth with AI Injury Payout Calculator for FREE!

Start my free evaluation

For instance, if an Amazon Flex driver was involved in a truck accident on I-70 near the Broad Street exit in Columbus, the first question we now ask is: was that driver actively transporting a package or heading to pick one up? If the answer is no, the liability picture changes dramatically, potentially limiting recourse solely to the individual driver’s personal insurance. This contrasts sharply with the pre-2026 environment where arguments for vicarious liability against the platform were more broadly applicable, even during “off-app” periods if a connection to the company’s business could be established. I remember a case just two years ago where we successfully argued for a platform’s liability even though the driver was technically “offline,” but had just completed a delivery and was heading to a high-demand area. That kind of argument is now significantly harder to make under HB 33.

Who is Affected by HB 33?

The impact of HB 33 is broad, touching multiple stakeholders within the gig economy. Firstly, and most critically, victims of accidents involving gig drivers are directly affected. Their ability to recover damages from a deep-pocketed company like Amazon or Uber now hinges on more specific criteria. This means diligent investigation into the driver’s app status and activities at the time of the crash is paramount.

Secondly, gig economy drivers themselves face new responsibilities. The law mandates that they carry specific types and amounts of insurance coverage depending on whether they are logged into the app, actively engaged in a trip/delivery, or offline. Failure to comply can have severe personal financial consequences. According to a report by the Ohio Department of Insurance, compliance with these new requirements has been a significant focus for driver education initiatives throughout 2025. This means drivers must be acutely aware of their coverage status at all times, a detail often overlooked in the rush of making deliveries.

Thirdly, transportation and delivery network companies like Amazon Flex, Uber, Lyft, and DoorDash are directly impacted. While the law provides some protections by limiting their liability in certain scenarios, it also imposes clear obligations regarding insurance verification and data sharing. They must now maintain records that can definitively prove a driver’s online status, an aspect that will undoubtedly become a key piece of evidence in any litigation. The Ohio State Bar Association has issued several advisories to its members on navigating these new corporate responsibilities, emphasizing the need for robust internal record-keeping.

Finally, insurance companies operating in Ohio have had to adapt their policies and coverage offerings to align with HB 33’s multi-tiered insurance requirements. This includes developing specific “rideshare endorsements” or commercial policies tailored to the unique operational model of gig work. The complexity here often leads to disputes between personal and commercial insurers, making the claims process even more challenging for injured parties.

What Exactly Changed? Understanding the New Liability Tiers

The crux of HB 33 lies in its establishment of distinct “periods” of operation for gig drivers, each with corresponding insurance and liability implications. This is where the rubber meets the road, quite literally, for accident claims.

• Period 0: Driver is Offline. This is when the driver is not logged into the DNC or TNC app. In this scenario, the driver’s personal auto insurance policy is solely responsible for any damages. The DNC or TNC bears no liability. This is a critical distinction; if an Amazon Flex driver was simply driving home after their shift, not logged in, and caused an accident on High Street in Columbus, Amazon Flex would not be a party to the claim.
• Period 1: Driver is Logged In and Available, but Not Engaged in a Trip/Delivery. During this period, the driver is waiting for a request. HB 33 mandates that the DNC or TNC’s insurance policy provides contingent coverage. Specifically, ORC Section 3939.05(C)(1) requires coverage of at least $50,000 for bodily injury per person, $100,000 for bodily injury per accident, and $25,000 for property damage. This coverage kicks in if the driver’s personal insurance denies the claim or doesn’t cover the full amount. This is a significant improvement from the past, where personal insurers often denied claims outright if they discovered the driver was “working.”
• Period 2: Driver is Engaged in a Trip or Delivery. This period covers from the moment a driver accepts a request until the passenger is dropped off or the package is delivered. Here, the DNC or TNC’s primary insurance coverage applies, as stipulated in ORC Section 3939.05(C)(2). This coverage is much more substantial, typically $1,000,000 for bodily injury and property damage combined. This is the period where a victim has the strongest claim against the network company itself, making it imperative to verify the driver’s status immediately following an accident.

This tiered approach, while offering clarity, also creates complexity. Proving which “period” a driver was in at the time of a collision requires immediate and strategic evidence gathering. We at our firm always advise clients to try and get screenshots of the driver’s app status if they can safely do so, or at least note any identifying markings on the vehicle that suggest commercial operation. This kind of immediate action can make or break a claim under the new law. We had a case just last month where a client was involved in a fender bender with a DoorDash driver on Olentangy River Road. The driver initially claimed they were “offline,” but our rapid investigation uncovered GPS data from the DoorDash app (obtained through a subpoena) that showed they had just completed a delivery and were en route to another pick-up, firmly placing them in Period 2. That distinction ultimately secured a much larger settlement for our client.

Concrete Steps Readers Should Take After a Gig Economy Accident

If you or a loved one are involved in a truck accident or any collision with a gig economy driver in Columbus, particularly with the new HB 33 in effect, immediate and informed action is more crucial than ever. The following steps are essential:

1. Prioritize Safety and Seek Medical Attention: Your health is paramount. Even if you feel fine, get checked by paramedics or visit an emergency room like OhioHealth Grant Medical Center. Some injuries, especially whiplash or concussions, may not manifest immediately. Document all medical care meticulously.
2. Call the Police and File a Report: Always call 911. A police report creates an official record of the accident, including details like location, time, and initial statements. For a crash on a busy intersection like North High Street and Lane Avenue, this report can be invaluable.
3. Gather Evidence at the Scene: If safe, take photos and videos. This includes damage to all vehicles, skid marks, traffic signals, and any identifying logos on the gig driver’s vehicle. Critically, try to observe if the driver is using a delivery app on their phone and, if possible, get a clear photo of their phone screen showing their app status (though this can be difficult and should only be attempted if safe and non-confrontational). Exchange insurance information, driver’s licenses, and contact details.
4. Do NOT Admit Fault or Give Recorded Statements: Do not apologize or speculate about who was at fault. Do not give a recorded statement to any insurance company (yours or theirs) without consulting an attorney first. Anything you say can be used against you.
5. Contact an Attorney Specializing in Commercial Vehicle Accidents IMMEDIATELY: This is not a step you can delay. The complexities of HB 33, particularly regarding liability tiers and insurance coverage, demand expert legal guidance from the outset. An attorney can quickly begin gathering evidence, including subpoenaing data from the DNC/TNC to establish the driver’s “period” of operation, which is often the linchpin of these cases. We often find that crucial data can be lost or overwritten if not requested promptly.
6. Document Everything: Keep a detailed record of all medical appointments, treatments, medications, lost wages, and any other expenses related to the accident. Maintain a pain journal, noting how your injuries affect your daily life.

My editorial opinion on this is unequivocal: waiting to consult legal counsel after a gig economy accident is a grave mistake. The window to collect critical evidence and establish the driver’s status under HB 33 is narrow. The sooner you act, the stronger your position will be.

Navigating the Insurance Maze: What to Expect

The insurance aspect of a gig economy accident post-HB 33 is, frankly, a mess. You’re no longer just dealing with two personal auto policies. You might be dealing with a personal policy, a DNC’s contingent policy, and a DNC’s primary policy, all with different adjusters and competing interests. This is why specialized legal representation is non-negotiable.

When you file a claim, your own insurance company might initially process it under your Uninsured/Underinsured Motorist (UM/UIM) coverage if the at-fault driver’s insurance (or the DNC’s contingent coverage) is insufficient. However, they will also be looking to subrogate against the at-fault driver and their associated DNC/TNC. The DNC’s insurance carrier, on the other hand, will be scrutinizing the driver’s status at the time of the collision, often attempting to argue they were in Period 0 or Period 1 to minimize their payout.

A concrete example of this complexity involved a client of ours, Ms. Davis, who was hit by a Lyft driver on Cleveland Avenue in Columbus. The Lyft driver initially told the police he was “offline.” However, our immediate investigation, including a subpoena to Lyft, revealed that he had just dropped off a passenger and was en route to pick up another, placing him squarely in Period 2. Lyft’s insurance initially denied the claim, citing the driver’s “offline” statement. We presented the GPS data and the passenger manifest. After several months of negotiation and the threat of litigation in the Franklin County Common Pleas Court, Lyft’s insurer ultimately settled for $850,000, covering Ms. Davis’s extensive medical bills, lost wages, and pain and suffering. This outcome would have been impossible without a deep understanding of HB 33 and aggressive pursuit of the truth.

Don’t be surprised if there’s finger-pointing between the various insurance companies. This is a common tactic to delay payouts and confuse claimants. Your attorney will be the one to cut through this noise, identify the correct liable parties, and ensure you receive the compensation you deserve under Ohio law.

The legal landscape for accidents involving gig economy drivers in Ohio has fundamentally shifted with HB 33. Understanding these changes and taking immediate, decisive action after an incident are critical to protecting your rights and securing fair compensation. Don’t navigate this complex terrain alone; seek expert legal counsel to ensure your claim is handled effectively.