Who Pays After an Uber or Lyft Crash in Massachusetts?

After an Uber or Lyft crash in Massachusetts, which insurance policy pays turns on what the driver’s app was doing at the instant of impact. The dollar figures are not in the rideshare chapter most people cite. M.G.L. c. 159A1/2, sec. 5 requires “adequate insurance, as required by this chapter and section 228 of chapter 175”, and it is M.G.L. c. 175, sec. 228 that sets the numbers: a driver logged on but not yet dispatched carries “at least $50,000 of coverage per individual for bodily injury, $100,000 of total coverage for bodily injury, $30,000 of coverage for property damage”, while a driver on a pre-arranged ride carries “at least $1,000,000 in per occurrence, per vehicle coverage for death, bodily injury and property damage”. A pre-arranged ride starts the moment the driver accepts the request, not at pickup. Section 228 also does something no other Massachusetts auto statute does: subsection (h) lets a personal auto insurer exclude personal injury protection, uninsured and underinsured motorist coverage during the trip, and says those exclusions apply “notwithstanding any requirement of said section 34A of said chapter 90 and section 113L”. To talk through a rideshare crash with a Massachusetts attorney, call Jim Glaser Law at (617) JIM-WINS; the first telephone consultation is free.

The Money Is Not in the Rideshare Statute

Massachusetts regulates Uber, Lyft and similar operators as transportation network companies under M.G.L. c. 159A1/2. That chapter is where the permits, the background checks, the driver certificates and the vehicle decals live. It is also the chapter almost every summary cites for the insurance numbers, and it does not contain them.

What section 5 of that chapter actually says is that “Each transportation network company shall carry adequate insurance, as required by this chapter and section 228 of chapter 175, for each vehicle being used to provide transportation network services”. The operative word is the cross reference. The dollar amounts, the coverage tiers, and every rule about what a personal auto policy may and may not refuse to do sit in the insurance code, at M.G.L. c. 175, sec. 228.

This is not a pedantic distinction. Section 228 contains provisions that change the outcome of a real claim and that no summary of chapter 159A1/2 will ever mention, because they are not in chapter 159A1/2. The most consequential of them is discussed further down: the statute permits a personal auto insurer to switch off no-fault benefits during a rideshare trip, which is something Massachusetts law does nowhere else.

The Three Coverage Layers, and What Each One Is Worth

Section 228 divides a rideshare driver’s day into layers, and a claim lands in exactly one of them.

The app is off. This is not a rideshare claim at all. Section 228(b) requires a driver to “maintain insurance coverage for the vehicle during those periods of time when the vehicle is being operated, but is not providing transportation network services”, which is the ordinary compulsory policy every Massachusetts registrant carries. The claim proceeds like any other car accident.

The app is on, no ride accepted. Section 228(c) governs a driver “logged onto the transportation network company’s digital network and is available to receive transportation requests, but is not engaged in a pre-arranged ride”. That driver must have liability coverage of “at least $50,000 of coverage per individual for bodily injury, $100,000 of total coverage for bodily injury, $30,000 of coverage for property damage, uninsured motorist coverage, to the extent required by said section 113L, and personal injury protection, to the extent required by section 34A of chapter 90”.

A ride is accepted or underway. Section 228(d) requires “at least $1,000,000 in per occurrence, per vehicle coverage for death, bodily injury and property damage”, along with uninsured motorist coverage and personal injury protection on the same terms.

One structural point runs through both of the middle layers. The statute does not say the rideshare company must be the one holding the policy. It says “The insurance may be held by the transportation network driver, the transportation network company or a combination thereof”. In practice the companies carry it, but the statutory duty is on the coverage existing, not on any particular party owning it, which is why an early claim letter should go to the driver and the company rather than to whichever one the police report happened to name.

The gap between the two rideshare layers is a factor of twenty on the per-person bodily injury limit. That is the entire reason the next section matters as much as it does.

A Pre-Arranged Ride Starts at Accept, Not at Pickup

The boundary between the $50,000 layer and the $1,000,000 layer is the phrase “pre-arranged ride”, and Massachusetts defines it in a way that surprises most people, including a fair number of drivers.

Under M.G.L. c. 159A1/2, sec. 1, a pre-arranged ride is “a period of time that begins when a transportation network driver accepts a requested ride through a digital network, continues while the driver transports the transportation network company rider and ends when the rider safely departs from the vehicle”.

Read the two ends of that sentence carefully, because both do work.

It begins at acceptance. A driver who taps accept and then drives six minutes across town to the pickup is, for the entire six minutes, inside the million-dollar layer. There is no passenger in the car. There may be no visible sign that anything is different from the minute before. But a cyclist struck during that drive, or another motorist, or a pedestrian in the crosswalk, is looking at a $1,000,000 liability limit rather than a $50,000 one, on facts that are invisible at the scene and knowable only from the company’s records.

It ends when the rider “safely departs from the vehicle”. That is a different moment than the ride ending in the app, and it is the phrase to hold onto if a passenger is hurt while getting out: struck by a passing car when the door opens, injured on the step down, caught by a driver pulling away. The statutory period has not closed until the rider has safely departed.

There is a second definition worth knowing, because it sets the outer boundary of the whole scheme. “Transportation network services” is defined in the same section as “covering the period beginning when a transportation network driver is logged onto the transportation network company’s digital network and is available to receive a pre-arranged ride or while in the course of providing a pre-arranged ride”. Everything in section 228 keys off that window.

Answer Capsule

Which policy pays after a Massachusetts Uber or Lyft crash depends on what the driver’s app was doing at the instant of impact, and the dollar figures come from M.G.L. c. 175, sec. 228 rather than from the rideshare chapter itself. A driver logged on but not yet dispatched carries “at least $50,000 of coverage per individual for bodily injury, $100,000 of total coverage for bodily injury, $30,000 of coverage for property damage”. A driver on a pre-arranged ride carries “at least $1,000,000 in per occurrence, per vehicle coverage for death, bodily injury and property damage”. Under M.G.L. c. 159A1/2, sec. 1 a pre-arranged ride begins the moment the driver accepts the request and ends when the rider “safely departs from the vehicle”, so the twenty-fold jump in available coverage happens before there is any passenger in the car. Subsection (h) of section 228 separately permits a personal auto insurer to exclude personal injury protection and uninsured and underinsured motorist coverage for the duration of transportation network services, so the no-fault floor that exists in every other Massachusetts auto claim can lawfully be absent here. Section 5 of chapter 159A1/2 gives directly interested parties a right to the driver’s app status and to log-on and log-off times for the 12 hours either side of the crash.

The Provision Nobody Mentions: Your No-Fault Benefits Can Be Switched Off

Massachusetts no-fault benefits are the floor under every auto injury claim in this state. Personal injury protection pays medical bills and lost wages regardless of who caused the crash, and the rest of the library is written on the assumption that the floor is there, because in ordinary cases it always is.

Section 228(h) is the exception, and it is written in unusually plain language. “Insurers that write automobile insurance may exclude any and all coverage afforded under the policy issued to an owner or operator of a vehicle for any loss or injury that occurs while a driver is providing transportation network services or while a driver provides a pre-arranged ride.”

The statute then lists what “any and all coverage” reaches, and the list is comprehensive: “(i) liability coverage for bodily injury and property damage; (ii) personal injury protection coverage as defined in section 34A of chapter 90; (iii) uninsured and underinsured motorist coverage; (iv) medical payments coverage; (v) comprehensive physical damage coverage; and (vi) collision physical damage coverage”.

Then comes the sentence that makes this different from every other exclusion argument in Massachusetts auto law: “Such exclusions shall apply notwithstanding any requirement of said section 34A of said chapter 90 and section 113L”. Section 34A is the compulsory personal injury protection statute. Section 113L is the compulsory uninsured motorist statute. Both are the reason a Massachusetts driver cannot ordinarily be left without no-fault benefits or uninsured motorist protection. Section 228(h) suspends both of them for the duration of a rideshare trip, if the personal policy is written to do so.

The statute is equally direct about what a personal policy owes: “Nothing in this section implies or requires that a personal automobile insurance policy provide coverage while the transportation network driver is logged on to the transportation network company’s digital network”. And it removes the defense obligation as well: “Automobile insurers that exclude the coverage described in this section shall not have a duty to defend or indemnify any claim expressly excluded by a policy”.

Two things follow from this, and they point in opposite directions for different people.

For an injured rideshare driver, the personal policy may be a dead end for exactly the trip that hurt them, and the section 228 layer is not a supplement to their own coverage but a replacement for it. The general shape of no-fault benefits is covered in the Massachusetts PIP article, and the coverage that normally responds when the other driver has nothing is covered in the uninsured and underinsured motorist article; both describe the ordinary case, and subsection (h) is the statutory carve-out from it.

For everyone else in the crash, the practical effect is smaller than it sounds, because the exclusion runs against the rideshare driver’s own policy while the section 228 layer is the one that answers to third parties. But it explains something that otherwise reads as stonewalling: a personal auto insurer that responds to a rideshare crash by saying the policy does not apply may be stating a position the Legislature explicitly authorized rather than inventing one.

The statute also preserves the other direction. “Nothing shall preclude an insurer from providing coverage for the transportation network driver’s vehicle if the insurer so chooses to do so by contract or endorsement.” Rideshare endorsements exist and some Massachusetts drivers carry them. Whether one was in force is a question about the specific policy, not about the statute.

You Do Not Have to Get Denied First

A recurring obstacle in rideshare claims is being told to go exhaust the driver’s personal policy before the company’s insurer will engage. The statute forecloses that sequence in two places.

Section 228(f) provides that coverage under the company’s policy “shall not be dependent on a personal automobile insurer first denying a claim nor shall a personal automobile insurer be required to first deny a claim”. There is no exhaustion requirement and no denial prerequisite.

Section 228(e) then addresses the case where the driver’s required coverage fails. Where insurance the driver maintained to satisfy subsections (c) and (d) has “lapsed, failed to provide the required coverage, denied a claim for the required coverage or otherwise ceased to exist”, the company’s insurance “shall provide the coverage required by said subsections (c) and (d), beginning with the first dollar of a claim, and shall have the duty to investigate and defend that claim”. First dollar, plus a duty to investigate and defend. That is a stronger backstop than most claimants are told they have.

How adjusters frame these positions, and what a claimant does and does not owe them, is the subject of dealing with the insurance adjuster after a Massachusetts car accident.

Where a Passenger Sits

A rideshare passenger is in the most protected position of anyone in these crashes, and the reason is a phrase written into the no-fault statute decades before rideshare existed.

M.G.L. c. 90, sec. 34A defines personal injury protection to cover “any authorized operator or passenger of the insured’s or obligor’s motor vehicle including a guest occupant”. A passenger in an Uber is a guest occupant of that vehicle. Section 228 requires personal injury protection in both the logged-on layer and the pre-arranged-ride layer, so the coverage is there. Benefits run to “at least eight thousand dollars on account of injury to or death of any one person” and are paid “without regard to negligence or gross negligence or fault of any kind”, which means a passenger never has to wait for the two drivers to finish arguing about who ran the light.

Above the no-fault layer, a passenger aboard the vehicle is by definition inside a pre-arranged ride, so the $1,000,000 limit under section 228(d) is the one in play. And a passenger has a structural advantage that a driver does not: a passenger is essentially never at fault, so the comparative-fault argument that shapes most Massachusetts claims has nothing to attach to. How fault is allocated when it is contested is covered in how fault is determined in a Massachusetts car accident.

If a Rideshare Vehicle Struck You Outside the Car

If you were on foot or on a bicycle, the legal analysis is the ordinary one and only the size of the policy changes.

M.G.L. c. 90, sec. 34A puts “any pedestrian struck by the insured’s or obligor’s motor vehicle” on the striking vehicle’s personal injury protection, which is the same route described in the pedestrian accident rights article. Because section 228 requires personal injury protection in both rideshare layers, that route is intact regardless of app status. A cyclist reaches the same benefits, and the rules of the road that decide fault in a bike crash are set out in the Massachusetts bicycle laws article.

What changes is the ceiling above the no-fault layer, and it changes by a factor of twenty depending on a fact you cannot observe from the roadway. This is the single strongest reason to establish app status early rather than treat it as a detail for later.

Proving App Status Is a Statutory Right, Not a Discovery Fight

Because everything turns on what the app was doing, the obvious worry is that the only party who knows is the one with a financial reason not to say. The Legislature anticipated that.

Section 5(b) of chapter 159A1/2 requires that after an incident causing injury or property damage, “a transportation network driver shall provide insurance coverage information to directly interested parties, automobile insurers and law enforcement”, and that on request the driver “shall disclose to directly interested parties, automobile drivers, automobile insurers and law enforcement whether the driver was providing transportation network services at the time of the incident”. That is a disclosure duty owed at the scene and afterward, not something that waits for a lawsuit.

Section 5(e) reaches the underlying data. In a claims coverage investigation, the company, the driver and the responding insurer must disclose to each other a clear description of the coverage, exclusions and limits, and must “cooperate to facilitate the exchange of relevant information with directly involved parties including, but not limited to, the precise times that a transportation network driver logged on and off of the transportation network company’s digital network” in the twelve hours before and the twelve hours after the accident. A twenty-four hour window of log-on and log-off times is exactly what is needed to place a collision in the right coverage tier.

Section 5(d) is worth knowing for a different reason. It requires the company to tell a prospective driver, in writing and before certifying them, both what coverage it provides and “a statement that the transportation network driver’s own automobile insurance policy may not provide coverage while the driver is providing transportation network services, depending on the terms of the policy”. A driver who was never given that disclosure has a fact worth raising.

Above the No-Fault Layer, the Ordinary Massachusetts Rules Apply

Nothing about rideshare changes the tort side of a Massachusetts auto claim.

Pain and suffering damages still run through the threshold in M.G.L. c. 231, sec. 6D, which allows them only where reasonable and necessary medical expenses are “in excess of two thousand dollars” unless the injury “(1) causes death, or (2) consists in whole or in part of loss of a body member, or (3) consists in whole or in part of permanent and serious disfigurement”, or causes the statutory loss of sight or hearing, or “(5) consists of a fracture”. That threshold is examined in detail in the serious injury threshold article.

Uninsured and underinsured motorist coverage still works the way it always does when the at-fault party is someone other than the rideshare driver. Section 113L reaches damages recoverable from “owners or operators of uninsured motor vehicles, trailers or semitrailers and hit-and-run motor vehicles”, and section 228 requires uninsured motorist coverage inside both rideshare layers.

The deadline is the ordinary one. M.G.L. c. 260, sec. 2A provides that actions of tort “shall be commenced only within three years next after the cause of action accrues”. The full picture, including the situations that change the accrual date, is in the Massachusetts personal injury statute of limitations article.

What Usually Goes Wrong Early

A few patterns show up often enough in rideshare claims to be worth naming.

The app status is recorded loosely or not at all. A police report that says “Uber driver” does not distinguish between a driver waiting for a ping and a driver two minutes from a pickup, and that distinction is the difference between a $50,000 limit and a $1,000,000 one. Ask on the day, in writing, for the log-on and log-off times.

The wrong insurer is treated as the only insurer. There can be three policies implicated in a single rideshare crash: the driver’s personal policy, the company’s policy, and the other vehicle’s policy. Notifying one is not notifying the others.

A recorded statement gets given before anyone knows which policy is answering. What you say to an adjuster in the first week can be used in a coverage dispute you did not know was coming. What that request actually obligates you to do is covered in giving a recorded statement to an insurance company in Massachusetts.

The exclusion gets mistaken for bad faith. When a rideshare driver’s own insurer denies personal injury protection for an on-app crash, that may be the statute operating exactly as written under section 228(h) rather than an insurer misbehaving. The productive response is to move to the section 228 layer, not to argue with the exclusion.

Frequently Asked Questions

Q: Which insurance policy pays after an Uber or Lyft crash in Massachusetts?

A: It depends on what the driver’s app was doing at the moment of the collision, and the amounts are set by M.G.L. c. 175, sec. 228 rather than by the rideshare chapter. If the app was off, the crash is an ordinary auto claim against the driver’s personal policy. If the driver was logged on and waiting for a request, section 228(c) requires “at least $50,000 of coverage per individual for bodily injury, $100,000 of total coverage for bodily injury, $30,000 of coverage for property damage”. If the driver had accepted a ride or had a passenger aboard, section 228(d) requires “at least $1,000,000 in per occurrence, per vehicle coverage for death, bodily injury and property damage”.

Q: Does the $1,000,000 policy only apply once the passenger is in the car?

A: No, and this is the detail most people get wrong. The $1,000,000 layer attaches during a pre-arranged ride, and M.G.L. c. 159A1/2, sec. 1 defines a pre-arranged ride as “a period of time that begins when a transportation network driver accepts a requested ride through a digital network, continues while the driver transports the transportation network company rider and ends when the rider safely departs from the vehicle”. The clock starts at acceptance. A driver who has tapped accept and is still several minutes away from the pickup is already inside the million-dollar layer, so someone struck during that drive is in a very different position than the app-status label suggests.

Q: I was a passenger in the Uber. Do I still get PIP benefits?

A: Usually yes, through the policy on the car you were riding in. M.G.L. c. 90, sec. 34A defines personal injury protection to include “any authorized operator or passenger of the insured’s or obligor’s motor vehicle including a guest occupant”, which is what a rideshare passenger is, and section 228 requires personal injury protection in both the logged-on layer and the pre-arranged-ride layer. PIP pays medical expenses and wage loss up to “at least eight thousand dollars on account of injury to or death of any one person” and it pays “without regard to negligence or gross negligence or fault of any kind”, so it does not wait for anyone to establish who caused the crash.

Q: Can the rideshare driver’s own insurer refuse to cover the crash?

A: Yes, and Massachusetts law expressly permits it. M.G.L. c. 175, sec. 228(h) provides that “Insurers that write automobile insurance may exclude any and all coverage afforded under the policy issued to an owner or operator of a vehicle for any loss or injury that occurs while a driver is providing transportation network services or while a driver provides a pre-arranged ride”, and the list of what may be excluded includes “(ii) personal injury protection coverage as defined in section 34A of chapter 90” and “(iii) uninsured and underinsured motorist coverage”. Subsection (h) then states that “Such exclusions shall apply notwithstanding any requirement of said section 34A of said chapter 90 and section 113L”. That is why the rideshare coverage layer matters so much: the personal policy may simply not be there.

Q: Do I have to be denied by the driver’s personal insurer first?

A: No. M.G.L. c. 175, sec. 228(f) states that coverage under the rideshare company’s policy “shall not be dependent on a personal automobile insurer first denying a claim nor shall a personal automobile insurer be required to first deny a claim”. Subsection (e) goes further: where the driver’s own required coverage has “lapsed, failed to provide the required coverage, denied a claim for the required coverage or otherwise ceased to exist”, the company’s insurance steps in “beginning with the first dollar of a claim, and shall have the duty to investigate and defend that claim”. An adjuster who says you must exhaust the personal policy before the rideshare policy will look at your claim is describing something the statute does not require.

Q: How do I prove what the app was doing when the crash happened?

A: The statute builds in a disclosure duty rather than leaving it to discovery. Under M.G.L. c. 159A1/2, sec. 5(b), a driver “shall disclose to directly interested parties, automobile drivers, automobile insurers and law enforcement whether the driver was providing transportation network services at the time of the incident”. Section 5(e) then requires the company, the driver and the responding insurer to “cooperate to facilitate the exchange of relevant information with directly involved parties including, but not limited to, the precise times that a transportation network driver logged on and off of the transportation network company’s digital network” in the twelve hours before and the twelve hours after the accident. Asking for those log times early, in writing, is the practical step that decides which coverage layer applies.

Q: A rideshare car hit me while I was walking. Does any of this change my claim?

A: The pedestrian analysis is the same one that applies to any vehicle, but the size of the policy behind it is not. M.G.L. c. 90, sec. 34A puts “any pedestrian struck by the insured’s or obligor’s motor vehicle” on the striking vehicle’s personal injury protection, and section 228 requires personal injury protection in both rideshare coverage layers. Above the no-fault layer, the liability limit available to you is whichever section 228 tier the driver was in, so the same crash can have a $50,000 per-person ceiling or a $1,000,000 one depending on facts that live entirely inside the company’s records.

Q: How long do I have to bring a Massachusetts rideshare claim?

A: Three years, on the same clock as any other Massachusetts injury claim. M.G.L. c. 260, sec. 2A provides that actions of tort “shall be commenced only within three years next after the cause of action accrues”. The practical deadline is much earlier than the legal one in a rideshare case, because the evidence that decides which coverage tier applies is app data held by a company that is not on your side, and no statute requires it to keep those records available to you indefinitely.

Q: Is Jimmy Knows AI giving me legal advice?

A: No. This is general information about Massachusetts law, not legal advice, and reading it does not create an attorney-client relationship. Statutes change and the way a rule applies depends entirely on the facts of a specific situation. For advice about a specific matter, speak with a Massachusetts attorney. The Jim Glaser Law line is answered 24 hours a day at (617) JIM-WINS, and the first telephone consultation is free.

Talking to a Lawyer

A rideshare claim looks like an ordinary car accident and is not one. The coverage that answers depends on a fact recorded only in a private company’s logs, the amount at stake swings by a factor of twenty on that fact, and the no-fault floor a Massachusetts claimant would normally stand on can be lawfully removed for the length of the trip. None of that is visible at the scene, and most of it is settled in the first two weeks by whoever asks for the right records.

Jim Glaser Law answers its line 24 hours a day at (617) JIM-WINS, and the first telephone consultation is free. The firm’s rideshare accident practice page describes how these matters are handled, and fee terms for personal injury matters are set out in how much personal injury lawyers charge in Massachusetts.