COMMUNITY RESEARCH NOTES - HISTORICAL WORKING COPY
Published September 29, 2026. This is community analysis, not an agency finding. Later updates supersede earlier pending/download notes: the county ZIPs have been reviewed; 13 new requests were sent September 29; Talavera written records have been received and published. See documents.html for the current tracker. Internal local filenames referenced below are research references, not additional public download links.

# Kent Grove Drive / SR 52: five-year crash-records request

Prepared September 28, 2026. Draft only; nothing sent or purchased.

## Where to start

For a location-based crash history, use [FDOT's official crash-data request page](https://fdot.gov/Safety/safetyengineering/crash-data.shtm), which supplies an email link and the State Safety Office Crash Records phone number **850-414-4007**. FDOT provides location-based listings and mapping; FLHSMV is the official crash-report custodian. For underlying reports or bulk data, FLHSMV's published contact number is **850-617-3416, option 1**; individual reports are available through the [Florida Crash Portal](https://services.flhsmv.gov/crashreportpurchasing/). Ask about fees before ordering.

Recent reports containing personal information have a 60-day confidentiality period measured from filing. Request releasable/redacted information and ask the custodian to identify withheld or pending records and the dataset's latest complete date. Do not assume an online map includes every reported incident.

## Draft request to FDOT

Subject: Five-year crash history ;  SR 52 at Kent Grove Drive, Pasco County

Please provide existing crash records/data for the intersection of State Road 52 and Kent Grove Drive (also potentially recorded as Kent Grove Road or Kent Grove Dr.), Pasco County, for September 28, 2021 through September 28, 2026, inclusive, to the latest available reporting date.

For an initial search area, please include the intersection and roadway approaches within 1,000 feet, including turn lanes and median openings. Please identify the boundary used and distinguish intersection-related crashes from other crashes within that area. Where recorded, please include crashes associated with queues or turning movements at the intersection even if coded outside that boundary. The 1,000-foot area is a proposed search boundary, not a claim that every crash inside it was caused by this intersection.

Please provide available electronic records, preferably CSV or Excel, containing crash/report number, date/time, location/coordinates or milepost, reporting agency, severity, collision type, vehicle travel directions and maneuvers, intersection-related indicator, lighting, weather, road-surface condition and work-zone status. Please include available collision diagrams, existing intersection safety studies, signal-warrant studies, turning-movement counts and turn-lane/queue analyses.

Please identify the data source, extraction date, latest complete date, and whether the dataset excludes short-form, driver self-reports or other categories. Please distinguish unique crashes from supplemental records to avoid double counting. Personal identifiers of crash participants are not requested.

Please provide any existing before/after comparisons for the SR 52 widening; otherwise dated individual records will allow that comparison. Please identify other custodians for records not held by your office.

Please provide a fee estimate before incurring charges and release readily available, nonexempt electronic records first. This request seeks existing records; it does not require creation of a new engineering study.

## Follow-up to FLHSMV

Using the crash numbers received, request the corresponding releasable crash reports, diagrams, narratives and supplements. Ask for bulk-request instructions and a cost estimate. If completeness is important, also request an index of all report categories held for the same location/date range and reconcile it with the FDOT list.

The [Pasco Sheriff's Office records page](https://pascosheriff.com/public-records-crime-statistics-2/) says FHP investigates most Pasco traffic crashes. PSO can check reports it generated; its records number is **813-235-6118**, and its page links the current JustFOIA portal. It directs 911/CAD requests to Pasco Emergency Communications. Dispatch calls are a separate source: a call does not necessarily produce a crash report, and multiple calls may concern one crash.

## How to use the results

Separate left-turn, angle and rear-end crashes; AM and PM peaks; injury severity; and intersection-related events from nearby unrelated events. Compare periods before and after the widening, accepted January 29, 2025 according to [FDOT's project page](https://www.fdottampabay.com/project/266/256323-1-52-01). A raw crash total alone does not establish how the proposed subdivision would change risk, and different period lengths or traffic exposure should not be compared as if equivalent.