Glendale generates rideshare volume its population does not explain. A stadium event pulls surge-priced drivers in from across the Valley, most unfamiliar with the streets they are navigating, and empties thousands of people into pickup zones at once. Any Uber accident lawyer Glendale riders call starts in the same place: the available insurance can swing from $25,000 to $1 million on a fact nobody can see from the roadside.
Whichever policy the driver’s app status triggers. Arizona sets minimum coverage by status under A.R.S. § 28-4038:
Driver status | Required primary coverage |
App off | No rideshare coverage; the driver’s personal policy applies |
Logged in, waiting for a request | $25,000 per person / $50,000 per accident, $20,000 property damage |
Ride accepted, driving to pick up | Minimum $250,000 per incident |
Passenger in the vehicle | Minimum $1,000,000 per incident |
The statute also requires primary commercial uninsured motorist coverage while a driver is providing transportation network services.
If you were the passenger, you sat in the top tier. If you were another motorist, a pedestrian, or a cyclist, the number could be any of the four and establishing which one applied is the first real task in the claim.
Dramatically, and the difference can be forty-fold. A driver logged in and idling in a Westgate staging lot waiting for a request sits in the $25,000 tier. Thirty seconds later, with a ride accepted, the floor rises to $250,000. With a passenger aboard it is $1,000,000. Nothing about the collision changed, only the app did.
With the app off entirely, the rideshare policy generally does not respond at all, and only the driver’s personal policy is in play. That is where claims stall, because A.R.S. § 28-4038 provides that unless a policy expressly says so, or carries an endorsement expressly providing it, a driver’s personal auto policy is not required to cover them while logged in or providing rideshare services. Most standard policies carry a livery exclusion for exactly this reason.
The result is a familiar loop: the personal carrier denies and points at the rideshare policy, and the rideshare carrier disputes app status and points back. A denial from one insurer is not a denial of coverage overall, and treating it as one is how valid claims get abandoned. Our page on what to do when a carrier refuses to pay covers the next step.
Yes, and passengers have the cleanest position of anyone involved. A passenger occupying the vehicle triggers the $1,000,000 layer, and that coverage generally responds regardless of which driver caused the crash, the rideshare driver or someone else.
Passengers also sit outside the usual fault fight. Because you were not operating a vehicle, there is rarely a credible argument that you contributed, which removes the issue that dominates most claims. Everyone else is exposed to Arizona’s pure comparative fault rule under A.R.S. § 12-2505, which reduces an award by the claimant’s assigned share with no cutoff.
One practical step matters more for passengers than anything else: screenshot the trip receipt, route map, and any in-app messages immediately. That receipt is proof of app status, and you are the only person in the collision who has it.
Only while a passenger is in the vehicle. That is the single distinction worth remembering. Between orders, en route to a pickup, or with the app off, lower tiers or no rideshare coverage apply.
That produces an outcome specific to Glendale. Someone struck on foot in a stadium pickup zone was likely hit by a driver who had accepted a ride but not yet collected anyone the $250,000 tier, not the $1,000,000 one. A rider in the back of that same car would be in the top tier. Same driver, same lot, same minute, very different ceilings.
Event nights, unfamiliar drivers, and private property. Three things stack up here.
Surge pulls in out-of-area drivers. The Grand Avenue / US-60 diagonal crosses the grid at oblique angles with a rail line alongside, producing offset multi-leg intersections that behave nothing like a square corner. A driver following GPS through it for the first time after an event is a recognizable fact pattern as are the arterial conflicts on Bell Road, 59th, and 67th Avenue, and higher-speed collisions on the Loop 101 Agua Fria Freeway.
Much of it happens on private property. Stadium lots, garages, and staging areas are where pickup actually occurs, and people assume the law is out there. A.R.S. § 28-661 applies to a collision causing injury “on public or private property,” so a driver who leaves the scene in a stadium garage has the same duties as on Glendale Avenue.
Alcohol is often in the mix. Where a licensee over-served a driver who then caused the crash, A.R.S. § 4-311 may support a claim against the establishment as well, and the impaired driving analysis turns on point-of-sale records and surveillance retained only briefly. Historic Downtown Glendale and ASU West commuter flow add their own pedestrian and cyclist exposure.
Court and deadlines. Glendale City Court hears no civil injury suits; claims above $10,000 go to Maricopa County Superior Court, smaller matters to a justice court. Glendale PD works city streets; DPS works Loop 101 and state routes including Grand Avenue. The filing deadline is generally two years under A.R.S. § 12-542, and where a publicly operated venue may share responsibility, notice is generally due within 180 days under A.R.S. § 12-821.01 which a rideshare company’s claims process does not toll.
Jason A. Harris has practiced personal injury and workers’ compensation law in Arizona since 2006, representing thousands of injury clients. Clients speak with him directly which matters when app data and venue camera footage are the evidence in dispute and both expire quickly.
Fee terms (ER 7.1 compliant): Cases run on a contingency fee no retainer, no hourly billing, no attorney fee unless compensation is recovered. Case costs are advanced and reimbursed from any recovery, with terms in writing before you sign. Consultations are free.
Where the driver had no coverage or left the scene, your own uninsured motorist coverage may respond, and a Glendale hit-and-run claim follows a different path. Serious outcomes run toward brain injury and pedestrian claims, and a Phoenix Uber accident attorney handles the same framework metro-wide from our Phoenix Uber and Lyft practice.
It depends on app status. Under A.R.S. § 28-4038, a driver logged in and waiting carries at least $25,000 per person and $50,000 per accident. Once a ride is accepted, the minimum rises to $250,000 per incident, and while a passenger is in the vehicle it is at least $1,000,000. With the app off, only the driver’s personal policy applies.
Yes, substantially. Between requests, the floor is $25,000 per person; once a ride is accepted, it is $250,000; with a passenger aboard, it is $1,000,000. That is why establishing app status at the moment of impact is the first task in a rideshare claim.
The $1,000,000 layer generally applies, and it responds regardless of which driver was at fault. Passengers are also rarely assigned any share of fault, since they were not operating a vehicle. Screenshot your trip receipt and route map immediately, as it can help establish the driver’s app status.
Usually not. A.R.S. § 28-4038 provides that a personal auto policy is not required to cover a driver while logged in or providing rideshare services, so a denial is often a personal carrier declining under a livery exclusion rather than a rejection of the claim itself. The commercial coverage is a separate layer.
App records, venue camera footage, and staging-lot surveillance all expire on schedules unrelated to the two-year filing deadline and they are what establish which policy applies.
Harris Injury Law, PLLC 1136 E Campbell Ave, Phoenix, AZ 85014 (480) 800-4878
An Arizona Uber accident attorney serving Glendale and the West Valley a Glendale Lyft accident lawyer and a Lyft accident attorney in Glendale for riders across Maricopa County. Request a free consultation or meet our attorneys. Every case depends on its own facts; no outcome can be promised or predicted.
This page provides general information about Arizona law and is not legal advice. Reading it creates no attorney-client relationship. Arizona law and insurance terms change, and coverage depends on the facts and policies involved. Consult a licensed Arizona attorney about your situation.
Reviewed by Jason A. Harris, Harris Injury Law, PLLC.
to assist you with your Uber/Lyft accident case.
Call or text now for a free consultation.
⭐⭐⭐⭐⭐
“After my Lyft accident near Westgate in Glendale, Harris Injury Law guided me through every step of the process. Jason personally reached out and explained the insurance process. I felt supported the entire time.”
- Maria T., Glendale, AZ
⭐⭐⭐⭐⭐
“I was an Uber passenger when another driver rear-ended us. The insurance coverage was confusing, but Harris Injury Law took care of everything. They helped me recover for my medical treatment and lost work days.”
- Robert L., Peoria, AZ
[Disclaimer: Results and client experiences may vary. Past outcomes do not guarantee future results.]
Located at 1136 E Campbell Ave, Phoenix, AZ 85014. Harris Injury Law, PLLC specializes in auto and truck accidents and workers’ compensation. Speak directly with your lawyer from the beginning. Same-day and emergency consultations are available. You never pay out of pocket. Call us at any time – 24/7.
Harris Injury Law
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers).
Despite our very best efforts to allow anybody to adjust the website to their needs. There may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to