Written and reviewed by Cory Cannon, Esq.
Published Updated
A rideshare collision in St. Petersburg involves the same immediate medical and roadway concerns as another crash, with an added evidence layer: the application can show whether the driver was offline, available, traveling to a pickup, carrying a passenger, or completing a trip. Preserve the trip and vehicle evidence before app records, video, electronic data, and witness memories change. Florida generally provides two years to file an ordinary negligence action accruing after March 24, 2023.
Cory Cannon represents injured plaintiffs. A rideshare case may involve an injured passenger, driver, occupant of another vehicle, cyclist, or pedestrian. Potential coverage and parties depend on the trip phase, driver conduct, vehicle ownership, another motorist, app records, and policy language. Obtain the data before deciding which insurer must respond.
What to do after a St. Petersburg rideshare crash
- Address safety and care. Call 911 for an emergency and follow responder instructions.
- Identify every person and vehicle. Record drivers, passengers, owners, plates, vehicle descriptions, insurers, and company or rental information.
- Preserve the trip. Screenshot the ride receipt, driver and vehicle profile, route, pickup, destination, timestamps, fare, messages, and platform report.
- Document the scene. Photograph positions, damage, debris, marks, lanes, signals, signs, lighting, weather, sight lines, and cameras.
- Find witnesses. Save reliable contact information and note each person’s location and view.
- Request electronic evidence. Platform, driver, vehicle, camera, phone, and third-party records may have short retention or difficult access.
- Keep medical and income proof. Organize records, bills, restrictions, wage documents, and a dated functional chronology.
- Review insurance before release. Determine the app phase, insureds, limits, exclusions, and remaining claims before accepting payment.
Preserve the app record immediately
A passenger should save the complete receipt and trip screen before the account view changes. Capture the platform, trip identifier, date, pickup, destination, route, driver, vehicle, plate, fare, timestamps, support messages, rating prompts, and safety reports. Export available account data while preserving original emails and text messages.
The driver should preserve the app’s status, trip offer, acceptance, pickup, route, communications, cancellation, completion, earnings, and any safety or collision prompts. Do not alter an account or delete the application. Screen captures help, while native platform data may contain additional fields and system timestamps.
A focused preservation notice should identify the account, trip, vehicle, date, location, and time window. Potential records include status changes, offers, acceptance, navigation, GPS, communications, customer and driver reports, telematics, identity verification, vehicle records, insurance notices, and support contacts. Scope should remain tied to the event.
Why the rideshare phase matters
Florida’s Transportation Network Companies statute separates coverage according to app status and whether the driver is engaged in a prearranged ride. The factual timeline may include offline driving, logged-on availability, acceptance, travel to pickup, passenger entry, the trip, passenger exit, and app completion.
Section 627.748 addresses TNC operations and automobile insurance requirements. It provides different coverage requirements while a participating driver is logged on but not engaged in a prearranged ride and while the driver is engaged in one.
While the driver is logged on but has not accepted a ride, the statute requires at least $50,000 in bodily injury liability per person, $100,000 per incident, and $25,000 in property-damage liability, together with required PIP and UM or UIM coverage. From ride acceptance through the last rider’s exit, it requires at least $1 million in primary liability coverage, together with required PIP and UM or UIM coverage. The driver, vehicle owner, TNC, or a combination may maintain the required insurance, so the actual policies still matter.
Do not infer status from whether a passenger was physically present. Travel after acceptance toward the pickup can fall within a ride phase defined by the statute. Conversely, a driver waiting with the app available may occupy a different coverage period. Platform data, driver records, passenger records, and timestamps should be compared.
Build a minute-by-minute trip timeline
Begin before the collision. Record when the driver logged on, received and accepted an offer, began navigation, arrived, marked pickup, started movement, changed route, stopped, and ended the trip. Add the crash, 911 call, platform report, tow, medical response, and later communications.
Compare time zones and clock settings. A receipt, phone screenshot, vehicle system, police record, camera, and platform database may display different time bases. Retain source metadata before converting everything to a common timeline.
Route deviations can have ordinary explanations such as traffic, rider instructions, road closure, pickup access, or navigation. Preserve messages and map prompts. A deviation matters only if evidence connects it to fault, coverage, or damages.
Scene evidence in St. Petersburg
Record the road, direction, lane, intersection, address, pickup zone, drop-off point, driveway, or parking area. St. Petersburg rides can involve state roads, bridge approaches, residential pickups, event traffic, hotels, restaurants, medical facilities, and commercial properties. Each setting identifies different camera and record holders.
A pickup pin can sit on a city street while the collision occurs on a state road, in a hotel drive, at a parking facility, or beside a transit stop. Record the actual vehicle path and impact point instead of relying on the app’s place label. The route can identify separate custodians for cameras, traffic controls, access logs, curb rules, and roadway records.
Businesses, residences, hotels, parking facilities, buses, fleets, and other vehicles may hold video. Public agencies may hold traffic-control, roadway, dispatch, or body-camera files. Requests should identify a narrow time window and exact camera or location where possible.
Passenger claims
An injured passenger should identify both the rideshare driver and every other motorist. A passenger may have no role in causing the collision, yet liability between drivers can remain disputed. Preserve evidence against all responsible parties while insurers investigate.
The passenger’s ride receipt can identify the platform relationship, vehicle, driver, pickup, destination, and app phase. Preserve it with the passenger’s seat position, seatbelt condition and use, child restraint when involved, luggage, interior photographs, statements, and view of the approach.
A passenger may have PIP through the vehicle, the passenger’s own policy, or another priority source depending on insured status and policy facts. Rideshare liability and UM or UIM coverage may also be relevant. Obtain the full policy and statutory coverage information rather than relying on an app help page.
Claims by occupants of another vehicle
A person in another vehicle should document the rideshare vehicle, plate, driver, occupants, markings if any, and any statement about app use. A rideshare vehicle often has no permanent exterior sign that resolves the driver’s status. The platform record is needed.
Preserve both vehicles, video, electronic data, marks, damage, witness information, and insurance. The ordinary collision analysis remains important: speed, following distance, signals, right of way, lane movement, distraction, impairment, and opportunity to avoid the event.
The other vehicle’s PIP and UM or UIM can apply alongside liability coverage. Give required notices while avoiding premature conclusions about which policy is primary. App status may affect the available rideshare layer.
Pedestrians and cyclists struck by a rideshare vehicle
Pickup and drop-off activity can place a vehicle near curbs, bicycle lanes, crosswalks, sidewalks, and loading zones. Document where the driver stopped, passenger-side doors, app pin, traffic, lighting, signs, and the movement of every person or bicycle.
A rideshare driver may turn, pull from a curb, cross a bicycle lane, back, or open a path for a passenger door. Determine whether the driver or passenger opened a door and preserve vehicle, app, and trip records. The respective duties and insurance require fact-specific review.
PIP may apply to a pedestrian or cyclist struck by a covered motor vehicle, with priority depending on policies and household or ownership facts. Liability and UM or UIM coverage can add separate sources. Review the pedestrian and bicycle guides for additional evidence issues.
Rideshare driver injuries
An injured rideshare driver can have a claim against another responsible driver and may also need to navigate PIP, collision, UM or UIM, platform coverage, health insurance, and personal-policy terms. App status, vehicle use, ownership, and endorsements should be established immediately.
Preserve earnings records from before and after the collision, trip history, incentives, expenses, tax records, platform communications, vehicle downtime, rental or substitute transportation, and account restrictions. Gross fares are different from net earnings.
The driver’s classification and relationship with the platform can affect certain theories, while section 627.748 includes statutory provisions concerning TNC drivers. Do not assume that everyday labels resolve employment, agency, coverage, or liability.
Identify the driver, vehicle owner, and platform
Verify the driver’s legal name, license, app profile, vehicle, plate, registration, owner, insurance, and platform. The app vehicle may differ from the vehicle present. Photograph both the displayed profile and actual vehicle.
A spouse, family member, rental company, leasing company, or business may own the vehicle. Ownership can affect insurance and liability. Obtain registration, lease or rental terms, permission, maintenance records, and policy information.
The platform may hold driver onboarding, license, vehicle, insurance, screening, safety, complaint, deactivation, and trip records. Relevance and available legal theories depend on the supported facts and current law. Requests should target the event and a defined issue.
Personal auto and rideshare insurance can conflict
A personal auto policy may contain a transportation-network, livery, delivery, or business-use exclusion. A rideshare endorsement may restore some coverage. The platform policy may respond only during defined periods or after specified conditions.
Obtain the declarations, complete policy, endorsements, application, renewal material, reservation of rights, and claim correspondence. Identify the named insured, listed vehicle, driver, effective dates, limits, deductible, exclusions, and other-insurance provisions.
Coverage statements should be tied to the precise app status. If the driver used several platforms, preserve status records from each. Simultaneous availability or a delivery application can create additional factual and policy questions.
PIP after a rideshare crash
Qualifying initial services and care generally must occur within 14 days for covered medical benefits under section 627.736(1)(a). The policy, priority, deductible, provider rules, EMC framework, exclusions, and limits control.
A passenger, rideshare driver, occupant of another vehicle, pedestrian, or cyclist can have a different PIP path. Gather household and vehicle-ownership information and every auto policy. Track applications and denials so the proper carrier can be addressed.
PIP does not decide who caused the collision and may cover only part of medical expense and wage loss. Health insurance, medical-payment coverage, liability, and other benefits can also affect bills. Preserve explanations and payment histories.
UM or UIM coverage
UM or UIM may apply when a responsible driver is uninsured, underinsured, or unidentified. Potential sources can include a rideshare policy, occupied vehicle, passenger household, driver’s personal policy, employer vehicle, or another applicable policy. Insured status and exclusions require review.
Section 627.727 addresses UM coverage, rejection or selection forms, stacking, nonstacking, and an underinsured settlement-notice procedure. Rideshare statutes and policy provisions can add issues.
Do not accept the at-fault driver’s limits or sign a release before protecting applicable UM rights. Provide required notice, supporting information, and an opportunity to respond under the governing procedure.
Driver distraction and app use
The app may require attention for offers, navigation, pickup details, calls, or messages. Potential distraction evidence can include phone activity, app events, infotainment, vehicle systems, dispatch, passenger observations, and camera files. Requests should cover the relevant minutes.
A phone’s presence does not establish distraction. Determine whether the driver was touching, viewing, listening, speaking, or following navigation, and whether the conduct contributed. System logs require interpretation of foreground activity, automated processes, time, and device ownership.
Preserve the passenger’s communications too. A request to change route, locate a pickup, stop, adjust temperature, or handle luggage may explain part of the timeline. Passenger interaction still must be connected to driving conduct and causation.
Fatigue, timing, and multiple apps
Driver fatigue may be explored through trip history, platform time, other work, earnings, phone location, receipts, communications, and rest evidence. A long online period does not by itself establish impairment. The analysis should connect schedule and symptoms to driving.
A driver may use rideshare and delivery platforms during the same day. Preserve each account’s status and trips. The records can establish work time, route, app phase, and insurance questions without assuming that every logged-on minute involved driving.
Platform limits or prompts concerning driving time should be obtained when relevant. The event-date system and actual alerts matter. General descriptions from current marketing material may not reflect what the driver saw.
Vehicle cameras and electronic data
The vehicle may contain event data, dash-camera files, cabin video, GPS, collision alerts, telematics, and driver-assistance information. The driver, owner, rental company, manufacturer, insurer, platform, or vendor may hold different portions. Locate the vehicle before repair or sale.
A qualified download should identify the module, software, method, time basis, units, trigger, and limitations. Compare data with video, marks, damage, signal timing, and witness accounts. A speed field or alert does not supply every movement.
Cabin video can document passenger position, seatbelt use, driver attention, conversations, and impact movement. Privacy concerns should be handled through focused preservation and lawful discovery. Avoid public release of sensitive recordings.
Pickup and drop-off safety
Record whether the app pin directed the vehicle to a legal and reasonably safe stopping place. Photograph curb restrictions, traffic, bicycle lanes, sight lines, lighting, venue instructions, barriers, loading zones, and alternate access. Platform maps and property rules may be relevant.
A driver may stop in a travel lane, crosswalk, bicycle lane, driveway, bus area, or private loading zone. Determine the reason, duration, warning signals, passenger instructions, and vehicle position. Another driver’s conduct remains separately relevant.
Property owners or event operators may control pickup zones, signs, barriers, staffing, lighting, and traffic flow. Contracts, plans, permits, instructions, and video can identify control. The fact that rides occur at a property does not establish property fault.
Commercial, rental, and defective-vehicle issues
A rideshare vehicle may be rented or leased through a program. Preserve the agreement, inspection, maintenance, repair, recall, mileage, and insurance records. Identify who selected, maintained, and possessed the vehicle.
When brakes, tires, steering, lights, seatbelts, airbags, doors, or another system may have contributed, preserve the vehicle and component. Give interested parties notice before repair or destructive testing. A qualified analysis should distinguish pre-event failure from collision damage.
A collision with a commercial truck, delivery vehicle, or government vehicle adds company, driver, route, maintenance, and layered coverage records. Review the St. Petersburg truck accident guide when commercial evidence is involved.
Comparative fault
Insurers may allege speed, following distance, lane movement, distraction, impairment, seatbelt nonuse, unsafe stopping, or failure to avoid the event. Passengers may also hear competing driver accounts. Preserve neutral data and statements before positions harden.
Under section 768.81(2) and (6), Florida Statutes, each injured claimant’s damages are generally reduced by that claimant’s assigned fault. A claimant found greater than 50 percent at fault for the claimant’s own harm cannot recover in a negligence action governed by subsection (6).
Fault between drivers can be allocated even when the passenger bears none. Identify every responsible party and preserve claims against each. Settlement with one defendant may affect remaining rights, setoffs, coverage, and release language.
Medical proof and daily function
Rideshare collision injuries can involve the brain, spine, joints, limbs, internal organs, skin, and psychological health. A chronology should identify baseline, onset, emergency findings, imaging, procedures, rehabilitation, restrictions, improvement, setbacks, and prognosis.
A passenger may not know that impact is imminent and can have a different body position from a driver. Document seat, orientation, luggage, seatbelt, head restraint, interior contact, and airbag deployment. Medical and engineering evidence should address mechanism when disputed.
Record sleep, driving, walking, lifting, self-care, household work, childcare, recreation, and job tasks. Specific dates and examples show change. Ride receipts for medical transportation or replacement travel can document expense and appointment burden.
Medical expenses, liens, and future care
Keep itemized bills, provider ledgers, PIP and health-insurance payments, government-benefit records, personal payments, balances, write-offs, letters of protection, and reimbursement notices. Section 768.0427 governs medical-expense evidence in many Florida personal injury actions.
Future care should identify the service, medical basis, frequency, duration, and reasonable cost. It may include follow-up, therapy, medication, injections, surgery, counseling, equipment, home assistance, and scar treatment. Recommendations should be supported and current.
Before settlement, validate liens and outstanding balances and estimate the client’s net recovery. A gross policy-limit offer can be inadequate after expenses and repayment. Keep benefit and billing records consistent.
Income loss for passengers and drivers
Employees should preserve pay, schedules, attendance, leave, restrictions, employer communications, tax forms, and benefits. Separate missed treatment time from disability. Overtime, commissions, tips, bonuses, and promotion effects need documentation.
A rideshare driver should preserve platform statements, trip detail, online time, booked time, fares, tips, incentives, fees, mileage, vehicle costs, taxes, and account restrictions. Compare consistent periods and explain seasonal or voluntary schedule changes.
Other self-employed claimants may need contracts, invoices, calendars, customer communications, bank records, expenses, returns, and substitute-labor costs. Gross business receipts are different from personal earnings. A reduced-capacity claim should connect restrictions to actual work.
Fatal rideshare collisions
A fatal crash adds estate and wrongful-death issues while trip and vehicle data still require immediate preservation. Secure app records, vehicles, video, electronic data, medical and death records, family information, income and support proof, expenses, and every policy.
Florida’s Wrongful Death Act generally places the claim with the personal representative for statutory survivors and the estate. Survivor identity and damages depend on the statute and family structure. Review the St. Petersburg wrongful death guide.
How a rideshare case may proceed
The early file separates app phase, trip data, collision evidence, drivers and vehicles, personal and platform policies, medical proof, income loss, coverage, and liens. A demand can follow when liability, prognosis, damages, and policy information allow meaningful evaluation.
Litigation may include written discovery, platform and phone subpoenas, vehicle inspections, depositions, corporate testimony, qualified witnesses, mediation, and trial preparation. Each step should address an actual dispute. Settlement authority remains with the client.
Preserve relevant posts, messages, photographs, location data, and platform communications. Avoid public discussion of the collision, injury, or recovery. Do not delete an account or edit original evidence.
St. Petersburg resources and case evaluation
For a collision investigated by St. Petersburg Police, the department’s Records Division page supplies its crash-report and public-record request routes. Ask for available supplements, photographs, body-camera files, measurements, and recordings tied to the report number. Keep those materials separate from the ride receipt and platform claim file.
Police, roadway, property, vehicle, and platform records come from different custodians. A local report request will not produce the driver’s precise log-on and log-off times, trip acceptance, route, support communications, or applicable TNC policy. Preserve and request each source directly, using a narrow time window and consistent vehicle, driver, trip, and location identifiers.
Bring the ride receipt, screenshots, messages, photographs, video, report, witness contacts, vehicle information, policies, medical records, bills, wage documents, and insurer correspondence. Cory Cannon represents injured clients in St. Petersburg and surrounding Pinellas County communities. The firm’s only office is at 1512 McKay Bay Ct, Suite 2, Tampa, FL 33619, and meetings at that Tampa location are scheduled by appointment.
Review the St. Petersburg personal injury hub and related guides for car accidents, uninsured motorist claims, hit-and-run crashes, and catastrophic injuries. The Florida personal injury overview covers the shared claim process beyond app-specific issues. Request a free consultation.
You owe no attorney’s fees, case costs, or expenses unless there is a recovery. The written representation agreement controls and should be reviewed before signing.