No. You probably did not kill your claim.

But you did step straight into the ugliest part of an Uber or Lyft wreck: figuring out which insurance company is supposed to pay, and who is about to start pointing fingers.

That matters a lot in New Mexico, where plenty of drivers are uninsured or barely insured, and a serious crash on I-25, I-40, or one of those long empty stretches down toward Las Cruces can leave a family trying to juggle ER follow-ups, orthopedic visits, childcare, missed work, and a stack of calls from adjusters who all suddenly "need more information."

If you told your own insurer you were driving for Lyft or Uber when the crash happened, that fact changes the coverage analysis. It does not automatically erase every possible source of recovery.

The whole fight usually turns on what "period" you were in

This is where most people get blindsided.

Rideshare crashes are not handled like a normal two-car wreck because there may be three different insurance layers in play:

• the at-fault driver's liability policy
• your own personal auto policy
• Uber's or Lyft's commercial policy, depending on whether the app was off, on and waiting, or you were actively on a trip

That's the period 1, 2, and 3 mess people keep hearing about.

If the app was off, you are usually back in regular personal auto territory.

If the app was on and you were waiting for a ride request, that is the classic period 1 problem. This is where coverage gaps and denials show up. Your personal insurer may say you were using the vehicle for commercial activity. The rideshare company may provide only limited liability coverage, and that does not automatically mean it covers your own injuries, your car, or every bill landing in your mailbox.

If you had accepted a ride and were on the way to pick up the passenger, or the passenger was already in the car, that is generally period 2 or 3, where the rideshare company's bigger policy is usually in play. That is the part people talk about when they mention the $1 million policy. But even then, "in play" does not mean "paid fast" or "paid without a fight."

Telling your insurer the truth was still the right move

A lot of gig drivers panic after the crash and start wondering if they should have kept quiet.

Bad idea.

If your phone records, app data, trip log, vehicle telematics, police report, passenger statement, or hospital chart later shows you were working a ride, and you hid that, now the insurer has a second excuse to come after your credibility.

And credibility matters when everybody is already looking for a reason to shift the loss somewhere else.

The adjuster is not confused about this system. They know exactly how it works. The shell game is the point.

Your personal carrier may say, "This was excluded commercial use."

The rideshare carrier may say, "We need proof of app status and trip status."

The other driver's insurer may say, "Our insured is only partly at fault."

And New Mexico is a pure comparative fault state, which means they do not need to prove you caused all of it. They just need to shave off a percentage and pay less.

What actually changes after you admit you were on a Lyft or Uber trip

Usually, three things happen fast.

First, your personal insurer starts reviewing whether your policy excludes livery or commercial activity. A lot of standard personal policies do.

Second, the rideshare company's insurer starts demanding exact timestamps: when you logged in, when you accepted the ride, whether a passenger was in the car, whether the trip had ended, whether you were driving between rides.

Third, everyone starts acting like the missing detail is the whole case.

Sometimes it is.

A crash at 5:42 p.m. on I-40 west of Albuquerque during a dust-and-wind mess is one case if the app was merely on and waiting. It can become a very different case if the ride had already been accepted at 5:41 p.m. That one-minute difference can change which policy has to respond.

If you were the driver and you got badly hurt, period 1 is where things get brutal

This is the part nobody explains well enough.

In period 1, the rideshare company may provide liability coverage for damage you cause to other people, but that does not automatically mean there is generous coverage for you, the driver, for your own injuries or your own vehicle.

That is why a driver can get hammered in a serious crash and still end up hearing a bunch of variations of, "That's not covered under this part."

If the other driver caused the wreck, their liability insurance should be first in line. But New Mexico only requires 25/50/10 minimum liability coverage, and that gets eaten alive by one ambulance ride, one CT scan, one MRI, and a few missed weeks of work. If the driver who hit you was uninsured or underinsured - not rare here - then uninsured/underinsured motorist coverage becomes a huge issue, and whether your own policy or another policy applies gets very technical very fast.

That is why telling your insurer you were doing Lyft did not destroy your claim. It just forced the real coverage question into the open.

The hospital paperwork is not the thing that usually wrecks these cases

A lot of people fixate on something they signed in the ER while trying to answer texts from school, line up a ride home, and figure out who is picking up the kids.

That paperwork is usually about consent to treatment, payment responsibility, privacy notices, assignment of benefits, or authorization to bill insurance.

The more dangerous mistake is often this: giving a recorded statement too early, before you know your app status, before you see the police report, before you know whether the crash was logged as passenger-on-board, and before you understand which insurer is trying to trap you in period 1.

What you need to lock down right away

If this happened in New Mexico, get obsessive about the timeline.

Save screenshots of the app.

Save the trip receipt.

Save the ride request time, pickup status, and drop-off status.

Save any message from Uber or Lyft about the crash.

Save the police case number.

If the wreck happened on a corridor like US-285 near Artesia, I-25 south of Albuquerque, or US-70 where high-speed crashes go bad fast, make sure the reported location and time are accurate down to the minute.

Because once the coverage fight starts, everybody suddenly claims the timestamp is unclear.

And when you are handling all this alone while your spouse is deployed, that confusion is exactly what the insurance companies are counting on.