Written and reviewed by Cory Cannon, Esq.
Published Updated
After a Tampa rideshare collision, save the trip evidence before it disappears from the app. Screenshot the ride receipt, driver and vehicle identification, pickup and destination, route, timestamps, fare, messages, support ticket, and any safety report. Photograph the scene and vehicles, collect witness information, obtain medical care, and record the crash-report number. App status at the moment of impact can determine which insurance requirements apply, so the digital record belongs at the center of the investigation.
Florida generally allows two years to file an ordinary negligence action arising after March 24, 2023. Section 95.11(5)(a), Florida Statutes, states that general period. A death, older collision, public defendant, or other specialized claim may be governed differently. The limitations period offers no assurance that ride records, dash-camera clips, platform messages, or third-party video will still exist. Preservation should begin promptly.
Immediate steps for a rider, driver, or third party
- Call for help. Use 911 for injuries or a dangerous roadway. Follow medical guidance and describe every symptom and body area accurately.
- Report the crash. Obtain the investigating agency, report number, all drivers’ information, vehicle owners, license plates, and insurance details.
- Preserve the app record. Capture the receipt, ride status, trip map, timestamps, driver profile, plate, vehicle, pickup, destination, fare, communications, and platform claim or support number.
- Photograph the physical evidence. Record vehicle positions, impact areas, debris, lanes, signals, signs, lighting, weather, construction, sight lines, restraints, and visible injuries.
- Identify every witness. Include passengers, other drivers, nearby workers, and independent observers. Save where each person sat or stood and what portion of the event the person saw.
- Protect video and device information. Retain dash camera files, phone photographs, navigation data, and relevant messages in original form. Identify nearby business, home, vehicle, and traffic cameras.
- Notify the right insurers. Report the event through the platform and to applicable personal or household insurers as required. Record each claim number, adjuster, policy identified, and request.
- Review documents before signing. A release, authorization, app acknowledgment, property payment, or statement can affect claims. Obtain the full text and understand its scope.
The first coverage question is the driver’s app status
Florida regulates transportation network companies through section 627.748, Florida Statutes. The statute defines a prearranged ride as beginning when the driver accepts a rider’s request through the platform’s digital network, continuing while the rider is transported, and ending when the last rider exits and no longer occupies the vehicle. That definition makes precise timestamps important.
Three practical periods usually require analysis. The driver may be offline and engaged in ordinary personal use. The driver may be logged onto the network and available but have no accepted ride. The driver may have accepted a request or be transporting a rider during a prearranged ride. Personal and platform coverage can change at each transition.
Do not rely only on the driver’s memory or a single app screen. Request platform records showing acceptance, cancellation, arrival, pickup, ride start, route, completion, and log-on or log-off events. Section 627.748(8)(d) requires a TNC, on proper request in a coverage investigation, to provide precise log-on and log-off times for the 12 hours before and after the accident. Insurers involved in the claim can also request applicable coverage, exclusions, and limits under that provision.
Insurance while logged on without an accepted ride
When a participating TNC driver is logged onto the network but is not engaged in a prearranged ride, section 627.748(7)(b) requires primary automobile liability coverage of at least $50,000 per person for death and bodily injury, $100,000 per incident for death and bodily injury, and $25,000 for property damage. The paragraph also requires PIP and UM/UIM coverage as stated in the statute.
The driver, vehicle owner, TNC, or a combination can satisfy the statutory requirement. The applicable policy and facts still control the claim. A personal auto carrier may invoke an exclusion for compensated or app-based use, and the TNC policy may require proof that the driver was logged on. Obtain both coverage positions and the policies supporting them.
A driver who had logged off before impact may fall outside the TNC period. Conversely, a driver who was waiting for a request may be logged on even without a passenger. Phone records, platform data, screenshots, trip history, and the driver’s statements can establish the state more reliably than the absence of a rider.
Insurance during an accepted or active ride
While a driver is engaged in a prearranged ride, section 627.748(7)(c) requires primary automobile liability coverage of at least $1 million for death, bodily injury, and property damage. It also requires PIP and UM/UIM coverage as specified in that paragraph. The accepted-ride period begins before the passenger enters because the statutory definition starts when the driver accepts the request.
That timing matters in a crash while the driver travels toward pickup. The rider may be elsewhere, yet the accepted trip can place the driver within the statutory prearranged-ride period. Preserve acceptance and route records instead of equating an empty back seat with the lower logged-on period.
The $1 million requirement does not establish liability, injury value, or the amount available to one claimant. Several people can make claims against the same occurrence limit. Coverage exclusions, responsible parties, and excess insurance also require review. A supported claim still needs proof of fault, medical causation, and damages.
Personal-policy exclusions and overlapping coverage
Section 627.748(8)(b) permits personal automobile policies to exclude coverage for losses occurring while a TNC driver is logged on or providing a prearranged ride, subject to the statute and policy. Potential exclusions can reach liability, UM/UIM, medical payments, collision, comprehensive, and PIP. The TNC must disclose that the driver’s personal policy might provide no coverage during those periods.
An exclusion should be evaluated using the full policy, endorsement, effective dates, vehicle, driver, and app status. A personal carrier’s denial does not itself prove that the platform policy applies, and section 627.748(7)(e) states that TNC-maintained coverage cannot depend on the personal carrier first denying the claim. Coverage investigation can proceed with both insurers at the same time.
The driver’s own collision or comprehensive claim presents a separate issue from an injured passenger’s liability claim. Vehicle ownership, lienholder, deductibles, and platform endorsements can affect payment. Passengers should focus on their injury and coverage sources while preserving evidence about the rideshare vehicle’s condition.
Tampa location and route evidence
A rideshare receipt may identify only pickup and destination, while the crash occurs between them. Preserve the trip map and precise location. Note the street, cross street, direction, lane, traffic control, and whether the driver was approaching pickup, carrying a passenger, or ending the ride. That information links the physical crash to the platform period.
Match the app record to the physical scene. Save the route pin and timestamps, then record the street, nearest cross street, direction, lane, pickup or drop-off point, traffic control, and nearby properties. Those details can identify business or residential cameras, parking and access records, signal material, construction records, and the public body or private property entity responsible for a disputed feature. They also help test whether the recorded route is consistent with the driver’s account.
Some postal Tampa addresses are outside incorporated city limits. Use the city’s official boundary guidance to confirm the jurisdiction. The answer may identify the proper law-enforcement report, public-records custodian, road owner, and venue.
Driver fault and platform-related evidence
Common allegations include distraction by the app, an unsafe pickup or drop-off, sudden lane movement, missed turn, speeding, following too closely, fatigue, or impairment. App use alone does not prove negligence. The evidence should show what the driver viewed or did, when it occurred, and how it caused the collision.
Possible records include navigation instructions, accepted-trip data, messages, route deviations, phone mounts, telematics, dash camera video, rider communications, ratings, safety reports, and support contacts. Relevance and lawful access matter. A claim should seek records tied to the driver, trip, event, and reasonable surrounding period.
Florida’s TNC statute requires companies to maintain individual ride records for at least one year after each ride and individual driver records for at least one year after the driver relationship ends. Section 627.748(15), Florida Statutes. That statutory minimum does not guarantee that every category of telemetry, video, or message remains available for the same period. Targeted preservation remains important.
Responsibility beyond the rideshare driver
The other vehicle’s driver or owner may be responsible even when an injured person occupied a rideshare. Employers, rental companies, maintenance businesses, component manufacturers, or public entities may also require investigation. Every vehicle and entity should be mapped before a demand is limited to one policy.
Section 627.748 contains a vicarious-liability provision for a TNC when the statutory conditions are met. Platform liability cannot be assumed from branding or app use. Direct negligence, statutory compliance, vehicle ownership, driver status, and the TNC’s obligations require separate analysis.
The statute describes circumstances under which a TNC driver is treated as an independent contractor. Contracts and statutory requirements matter, though a label does not erase available insurance. Coverage under subsection (7) must be analyzed independently from a theory of direct or vicarious liability against the platform.
Comparative fault
A rideshare passenger usually has little control over either vehicle, though seat position, restraint, distraction allegations, and post-impact conduct can still appear in a claim. A third-party driver or rideshare driver may face competing accounts about lane movement, speed, or right of way. Preserve the app route, vehicle data, witnesses, and scene evidence.
Florida reduces damages according to the claimant’s assigned fault. Under section 768.81(2) and (6), Florida Statutes, a claimant found more than 50 percent at fault for the claimant’s own harm generally cannot recover in a negligence action governed by subsection (6). Fault among defendants and nonparties can also affect allocation under current law.
PIP after a rideshare collision
Section 627.748 requires PIP during the TNC insurance periods, but the correct PIP carrier and priority depend on who was injured, vehicle ownership, household policies, and the statutory framework. An injured passenger should disclose every household vehicle and auto policy.
Covered people generally must receive qualifying initial services and care within 14 days after the motor-vehicle accident for PIP medical benefits. Section 627.736(1)(a), Florida Statutes, contains the timing and benefit structure. Follow medical need and keep provider, bill, and claim information organized.
Health insurance, medical payments, employer benefits, Medicare, Medicaid, or other coverage can also be involved. These sources may assert reimbursement or lien rights. Keep explanation-of-benefits forms, provider ledgers, recovery notices, and correspondence for settlement accounting.
UM/UIM in a rideshare case
The TNC statute requires UM/UIM during its stated insurance periods as required by section 627.727. The actual limits, selections, insured status, and policy terms should be obtained and reviewed. A rider may also qualify under a household UM policy, depending on its language and Florida law.
Section 627.727, Florida Statutes, addresses UM coverage, rejection or lower-limit selections, stacking, and procedures. Personal-policy exclusions during app use, the occupant’s insured status, and the vehicle involved can produce contested coverage. Obtain written positions and the policies cited.
Section 627.727(6) establishes notice steps before an insured settles with an underinsured motorist. A rideshare case may involve several liability carriers and UM carriers. Coordinate proposed releases so settlement with one party does not impair another claim.
Medical evidence and the no-fault threshold
A medical chronology should document symptoms, examinations, imaging, treatment, referrals, restrictions, recovery, and prognosis. Tell providers that the person was a passenger, driver, pedestrian, bicyclist, or occupant of another vehicle because the mechanism can differ. Record seating position, restraint use, air-bag deployment, and impact direction.
In motor-vehicle actions governed by Florida’s no-fault law, section 627.737(2), Florida Statutes, requires a listed injury threshold before recovery of pain, suffering, mental anguish, and inconvenience. Medical professionals must support diagnosis, causation, and any permanency opinion.
Prior injuries do not automatically prevent recovery. The record should identify the pre-crash baseline and the supported change. Prior records, accurate history, objective findings, treatment response, and specific changes in work or daily activity can help distinguish a new injury or aggravation.
Medical expense and wage documentation
Keep itemized medical bills, insurance submissions, adjustments, payments, provider balances, referrals, and letters of protection. Section 768.0427(2) through (4), Florida Statutes, governs evidence involving paid and unpaid medical expense, letters of protection, and recoverable medical expense in covered personal injury actions.
Income proof can include schedules, pay stubs, employer verification, leave use, restrictions, tax forms, and return-to-work records. A rideshare driver making a claim should preserve platform statements, trip history, incentives, expenses, mileage, tax records, and time offline. Gross fares do not equal net income, and claimed loss should be calculated from reliable records.
Document transportation and replacement-service expenses with receipts. An injured rider may incur costs getting home, reaching appointments, or replacing assistance previously provided. The expense must be reasonable, connected to the collision, and supported.
Statements, app communications, and online evidence
A platform safety or support report can become evidence. State the facts accurately and keep a copy before submitting. Avoid estimates or conclusions outside personal knowledge. If a phone call occurs, record the date, participant, claim number, and subjects discussed in a contemporaneous note.
An insurer may request a recorded statement. Identify the carrier, policy, insured relationship, and purpose first. The person’s own policy may impose cooperation duties, while another driver’s liability carrier has a different role. Advice should be specific to the policy and claim.
Do not delete existing posts, messages, location history, or app material after a claim is anticipated. Preserve relevant content. Public photographs and comments can be used to question injury or activity claims, though a single moment may lack context. Accuracy and preservation protect credibility.
Settling a rideshare claim
A complete demand identifies each insured and carrier, the app period, supported fault, medical causation, damages, and proposed release. It should address known coverage disputes and other injured people. The platform policy, driver’s personal policy, other vehicle’s policy, UM coverage, and excess layers may require separate communications.
Florida’s section 624.155 creates a statutory bad-faith cause of action under specified conditions and contains a current notice-and-cure framework. Coverage, liability, notice, opportunity, causation, and damages are distinct issues. A platform’s large insurance requirement does not guarantee full payment.
The client should evaluate the net result after fees, case expenses, provider balances, liens, health-plan reimbursement, and other valid obligations. A release should identify all people, companies, policies, and claims resolved. Settlement with one carrier can affect another claim, so sequencing matters.
Different evidence for riders, drivers, and people in another vehicle
A rideshare passenger should preserve the receipt, seating position, restraint use, driver conversation, route, app messages, and any unusual driving observed. A TNC driver should preserve log-on history, accepted trip, navigation, vehicle use, personal and platform policies, and communications with the platform. A person in another vehicle may need formal requests because the app information is outside that person’s account.
Each claimant can have a different PIP and UM path even after the same crash. Household ownership, resident-relative status, app period, vehicle occupied, and policy selections matter. Coverage should be mapped person by person instead of assuming the platform policy pays everyone the same way.
The driver may use more than one platform. Preserve all app histories and identify which network had an accepted trip, which networks were merely online, and whether simultaneous log-on was possible. Coverage positions can conflict. Native platform records and phone information may resolve the timing.
Vehicle damage, lost use, and a rideshare driver’s income
A rideshare driver may have a vehicle repair or total-loss claim, loss-of-use expense, and income loss. Keep estimates, supplements, valuation reports, rental receipts, loan and title information, platform earnings statements, mileage, expenses, tax records, and proof of time offline. Gross fares or app projections do not automatically equal net lost income.
The platform or personal carrier may apply collision deductibles and exclusions based on app status. Obtain the policy and written position. Storage fees can grow while carriers dispute responsibility, so vehicle preservation and mitigation should be coordinated. Important event data or dash video should be secured before repair or salvage.
A passenger’s damaged phone, luggage, mobility equipment, or other property should be photographed and supported with ownership and value records. Review any property release to confirm that it does not compromise injury claims.
Visitors, minors, and rides requested for someone else
A Tampa visitor may have auto, travel, health, or UM coverage issued in another state. Choice-of-law and policy questions can become important. Preserve the home-state policies, trip records, rental information, and all coverage communications. Florida crash law does not automatically make every policy term a Florida term.
When an adult requests a ride for a child, relative, or guest, preserve both accounts and the receipt. The statutory definition of rider includes a person for whom another person requests the ride. The injured passenger’s own household policies can still matter.
A minor’s settlement may require court approval or protected funds depending on amount and litigation status. Parents should keep school, pediatric, activity, and expense records and obtain advice before signing a release.
Tampa medical, report, and court resources
Related Tampa guides address crashes involving commercial trucks, motorcycles, and bicycles. Each requires evidence beyond the rideshare app. The car accident guide explains ordinary auto coverage, the pedestrian guide addresses crossing claims, and the wrongful death guide covers fatal events.
- Emergency care. Florida’s Department of Health currently lists Tampa General Hospital as a Level I trauma center and St. Joseph’s Hospital as a Level II and pediatric trauma center in Hillsborough County. Use 911 for an emergency.
- Crash-report access. The FLHSMV traffic crash report page explains report availability through the Florida Crash Portal.
- Court and clerk. Hillsborough County is the sole county in Florida’s Thirteenth Judicial Circuit. The Hillsborough Clerk lists the George E. Edgecomb Courthouse at 800 East Twiggs Street in Tampa. Venue, jurisdiction, claims, parties, and amount at issue determine the proper court.
Prepare for a Tampa rideshare accident evaluation
Bring the crash report, trip receipt, app screenshots, route, timestamps, messages, platform claim number, photographs, video, witness contacts, all auto and health insurance, medical information, bills, income records, vehicle papers, receipts, and every carrier communication. Prepare a timeline covering app status, ride acceptance, pickup, collision, symptoms, reports, and insurer contacts.
Cory Cannon maintains the firm’s only office at 1512 McKay Bay Ct, Suite 2, Tampa, Florida 33619. In-person meetings are scheduled by appointment. Review the Tampa personal injury hub, Tampa car accident guide, Tampa pedestrian accident guide, and Florida personal injury overview for connected issues. The Sarasota rideshare accident guide addresses the same claim type in another service area.
Request a free consultation to discuss app status, policies, preservation, fault, medical proof, and deadlines. Representation is on a contingency basis. You owe no attorney’s fees, case costs, or expenses unless there is a recovery.