Wrongful Death

How can I find out which rideshare company the at-fault driver was working for at the time of the crash? – North Carolina

Short Answer

In North Carolina, the fastest way to identify the rideshare company is to request the driver’s rideshare status and insurance details from the driver, the investigating law enforcement agency, and the insurers involved. North Carolina law requires a rideshare (TNC) driver to provide coverage information and disclose whether they were logged into the rideshare app at the time of the crash when asked. If informal requests do not work, the next step is usually a formal records request or subpoena to the rideshare company (and sometimes its insurer) for the driver’s “log on/log off” and trip-status records around the crash time.

Understanding the Problem

Under North Carolina wrongful death and injury claims, the key question is often: can the at-fault driver’s insurer deny coverage because the driver was working for a rideshare company at the time of the crash, and if so, which rideshare company’s coverage applies. The decision point is identifying whether the driver was logged into a transportation network company (TNC) app and whether the driver was actively providing a ride (or just available) at the moment of the collision. That identification step matters because it determines which insurance policy should be investigated and put on notice.

Apply the Law

North Carolina regulates rideshare companies as “transportation network companies” (TNCs). When a crash happens, North Carolina law requires information-sharing about insurance and the driver’s app status. A TNC driver must carry proof of the required coverage and, upon request, provide coverage information and disclose whether the driver was logged on or off the TNC app at the time of the accident. North Carolina law also requires the driver, the TNC, and insurers potentially providing coverage to exchange specific timing information about logins and TNC service around the crash, which is often the most direct way to confirm which platform was involved and whether TNC coverage should apply.

Key Requirements

  • Confirm TNC status at the time of the crash: Determine whether the driver was logged into a rideshare app and whether the driver was in “TNC service” (for example, en route to pick up a rider or transporting a rider) versus merely logged in and waiting.
  • Identify the correct coverage source: Figure out whether coverage should come from the driver’s personal auto policy, the rideshare company’s policy, or a combination depending on the driver’s status at that moment.
  • Get time-stamped proof: Obtain records showing precise log on/log off times and trip status around the crash time so an insurer cannot rely on vague statements.

What the Statutes Say

Analysis

Apply the Rule to the Facts: The insurance carrier’s denial letter suggests the at-fault vehicle was operating as a rideshare or similar service, which commonly means the personal auto insurer is pointing to a rideshare exclusion and implying a TNC policy may apply. Under North Carolina law, the most direct fact to lock down is whether the driver was logged into a TNC app and whether the driver was providing TNC service at the time of the crash, because those time-stamped facts drive which coverage layer should respond. Once the platform is identified, the claim can be redirected to the correct TNC insurer and supported with the required log on/log off and trip-status documentation.

Process & Timing

  1. Who requests first: The injured party’s representative (or attorney) typically requests information. Where: Through written requests to the at-fault driver, the driver’s insurer, and the investigating law enforcement agency that prepared the crash report in North Carolina. What: A written request for (a) the rideshare company name, (b) the driver’s app status at the time of the crash, and (c) the rideshare insurer/claim contact information, along with any screenshots or “trip” details the driver can provide. When: As soon as a denial letter suggests rideshare activity, because app and platform records can be time-sensitive and insurers often need prompt notice.
  2. Escalate to the TNC/insurer with a targeted demand: If the driver or personal insurer will not identify the platform, send a focused written demand citing the need for the precise log on/log off and service times around the crash and asking the insurer to confirm whether it is “potentially providing coverage” under the TNC framework. This step is aimed at forcing a clear yes/no response and creating a paper trail.
  3. Use formal legal process if stonewalled: If informal requests fail, the next step is usually a lawsuit (or other formal proceeding) followed by discovery requests and subpoenas directed to the rideshare company and/or its insurer for the driver’s platform records around the crash time. The goal is a custodian-certified record showing which platform the driver was using and the driver’s status at the moment of impact.

Exceptions & Pitfalls

  • “Rideshare or similar service” is not always a TNC: Some denials use broad language that could include delivery driving or other commercial use. The fix is to demand time-stamped app-status proof and the company name rather than relying on labels.
  • Driver statements can be incomplete: A driver may say they were “off the app” or “between rides,” but the coverage question often turns on precise log on/log off and trip status. Written confirmation backed by platform records matters.
  • Delay can complicate proof: Platform records may be retained for limited periods or be harder to retrieve without the right identifiers (date/time window, driver name, phone number/email used on the platform, vehicle plate, and crash location). Early, narrow requests reduce friction.
  • Multiple policies may be involved: Depending on status, there may be a personal policy, a TNC policy, and uninsured/underinsured issues. A denial from one insurer does not automatically resolve which other insurer must step in.

Conclusion

In North Carolina, identifying the rideshare company usually comes down to proving the driver’s app status and platform identity at the time of the crash. State law requires a TNC driver to provide insurance information and disclose whether the driver was logged on or off the app when asked, and it contemplates exchanging precise log on/log off and service times during a coverage investigation. The next step is to send a prompt written request for the company name and time-stamped app-status records, and escalate to subpoenas through a filed case if the information is withheld.

Talk to a Wrongful Death Attorney

If a carrier denied coverage because the at-fault driver was doing rideshare work and the rideshare company is still unclear, our firm has experienced attorneys who can help identify the correct insurer, request the right records, and track deadlines. Call us today at [919-341-7055].

Disclaimer: This article provides general information about North Carolina law based on the single question stated above. It is not legal advice for your specific situation and does not create an attorney-client relationship. Laws, procedures, and local practice can change and may vary by county. If you have a deadline, act promptly and speak with a licensed North Carolina attorney.