After a rideshare collision, three different questions are often combined: whether a driver is treated as an independent contractor or employee, who caused the crash, and which insurance applies. North Carolina law addresses transportation-network companies and drivers, but one answer does not decide the others. The app status, trip timeline, policy language, and collision evidence must be documented separately.

Worker classification, civil fault, and insurance coverage are separate questions.

North Carolina creates a rebuttable classification presumption

Article 10A of Chapter 20 regulates transportation-network companies in North Carolina. G.S. 20-280.8 creates a rebuttable presumption that a transportation-network driver is an independent contractor. The presumption may be rebutted under the common-law test for employment.

That classification provision does not decide whether the driver negligently caused a collision or whether a particular insurance policy responds. Civil fault turns on driving conduct and causation. Coverage turns on the applicable statutory period, policy terms, covered person or vehicle, exclusions, notices, and other facts.

The trip timeline defines the insurance period

The statute distinguishes a driver who is logged onto the company’s digital network but is not providing a transportation service from a driver who is providing the service. Under the statutory definitions, the service begins when the driver accepts a request and ends at the later of completion of the transaction in the application or the point when all passengers have exited and their property has been unloaded.

  • Offline: the driver is not logged onto the rideshare network.
  • Available: the driver is logged on and waiting but has not accepted a request.
  • Accepted request: the driver has accepted a trip and is traveling toward the passenger.
  • Passenger trip: the passenger is in the vehicle and transportation is underway.
  • Trip ending: identify both the application’s completion time and when every passenger and item left the vehicle.

Minutes can change the statutory category. Preserve the complete application activity, acceptance and cancellation records, route data, pickup and drop-off events, receipts, messages, phone data, and the company’s policy effective on the collision date.

North Carolina sets different minimum coverage requirements

G.S. 20-280.4 states that while a driver is logged on but not providing a transportation service, required primary automobile liability coverage must provide at least $50,000 for bodily injury or death per person, $100,000 per incident, and $25,000 for property damage, together with the combined uninsured- and underinsured-motorist coverage required by the statute.

While the driver is providing a transportation service, the statute requires at least $1,000,000 in primary automobile liability coverage for death, bodily injury, and property damage, plus at least $1,000,000 in combined uninsured- and underinsured-motorist coverage. The driver, the transportation-network company, or a combination may maintain the coverage described by the statute.

Those figures are statutory minimums, not a statement of the amount payable on a particular claim. The collision date, actual policies and endorsements, fault, covered status, exclusions, offsets, injuries, damages, and other insurance can affect the result.

A personal policy may not cover rideshare activity

The North Carolina Department of Insurance consumer guide cautions that a personal automobile policy generally excludes public-livery or conveyance use, including periods when a driver is logged in without a passenger. An endorsement may be available, and a driver should disclose the use to the personal insurer.

North Carolina’s statute allows a personal insurer to exclude specified losses while a driver is logged on or providing a transportation service. It also provides that the transportation-network coverage cannot depend on the personal insurer first denying a claim. A coverage investigation should obtain both policies rather than assume that one automatically replaces the other.

Required records extend beyond the crash report

  • The complete app-status timeline, accepted and canceled requests, pickup and drop-off data, route, receipt, and communications
  • The transportation-network policy, personal auto policy, rideshare endorsement, declarations, exclusions, reservation-of-rights letters, and coverage position
  • Driver, passenger, vehicle-owner, company, and other involved-party identities and their legal and insurance relationships
  • Original vehicle, phone, dash-camera, surveillance, event-data, 911, dispatch, witness, scene, and medical evidence
  • Required disclosures to insurers or lienholders and the driver’s exchange of login and service-period information after the collision

Fault analysis remains independent

The related guide to determining fault in a Charlotte rideshare collision addresses driving conduct, other motorists, passengers, vehicles, roads, and competing causes. App status helps identify potential coverage; it does not prove which person caused the crash.

Rosensteel Fleishman Car Accident & Injury Lawyers provides information about consulting a Charlotte rideshare-accident lawyer when app status and insurance coverage are disputed. Classification, liability, coverage, defenses, deadlines, and damages depend on the complete records and current law.

Sources