Responses within 15 minutes
63.3%
SunGuide archive · all available years
361,604
66,388 crashes · year only, all corridors and incident types
Detailed chronology · selected filters
134,382
80,695 usable notification-to-arrival pairs
UrbanSDK · selected traffic coverage
2 months
96 matched month/corridor/hour groups
How service performed over time. Annual summaries use the selected year; combined legacy activities retain their original reporting scope.
| Year | All incidents | Crashes | Median RR response | Response n | Median crash duration | Duration n |
|---|---|---|---|---|---|---|
| 2022 | 72,706 | 14,403 | 10.5 min | 7,983 | 57.3 min | 12,894 |
| 2023 | 76,244 | 15,016 | 10.9 min | 7,907 | 58.0 min | 13,236 |
| 2024 | 78,272 | 14,744 | 11.6 min | 7,952 | 58.0 min | 12,697 |
| 2025 | 78,376 | 13,424 | 14.4 min | 7,680 | Unavailable | 0 |
| 2026 | 56,006 | 8,801 | 15.8 min | 5,631 | Unavailable | 0 |
2022–2024: workbook crash-response summaries. 2025–2026: measured chronology dispatch-to-arrival pairs; duration unavailable. Annual medians are not pooled. 2026 is partial.
Where recorded crashes concentrate. Review corridor demand before interpreting response performance.
361,604 recorded incidents and 66,388 crashes · year selection, annual archive summaries. Further filters use the detailed chronology only.
Counts are not risk per vehicle. 2026 is partial; legacy yearly distributions differ from workbook totals by four records.
When incidents occur. Compare hourly demand and weekday averages within the available filter detail.
The busiest recorded hour starts at 15:00 Eastern (10,822 incidents). Thu has the highest observed weekday average at 250.8 incidents per included day.
Incident time uses the first chronology entry. Daily rates exclude boundary dates, daylight-saving transitions and missing days.
How quickly Road Rangers arrived. Read response coverage, incident-type performance and event records together.
80,695 events have a usable same-unit notification/arrival pair (60.0% coverage). Median interval: 0.0 minutes.
| Incident type | Events | Measured n | Median min | 90th percentile min | Within 15 min |
|---|---|---|---|---|---|
| Disabled Vehicle | 61,747 | 55,065 | 0.0 | 20.8 | 86.5% |
| Crash | 22,225 | 13,311 | 15.1 | 37.5 | 49.9% |
| Congestion | 12,581 | 7 | 0.0 | 4.0 | 100.0% |
| Road Work - Scheduled | 9,219 | 4 | 0.0 | 4.3 | 100.0% |
| Debris on Roadway | 8,929 | 6,196 | 0.0 | 28.8 | 74.5% |
| Wrong Way Driver | 5,958 | 0 | — | — | — |
| Abandoned Vehicle | 5,767 | 5,440 | 0.0 | 0.0 | 94.2% |
| Bridge Up | 2,583 | 0 | — | — | — |
| Visibility | 2,074 | 0 | — | — | — |
| Emergency Vehicles | 1,171 | 221 | 2.7 | 23.9 | 77.8% |
| Vehicle Fire | 435 | 294 | 13.9 | 38.0 | 52.0% |
| Other | 428 | 24 | 0.0 | 15.9 | 87.5% |
| Police Activity | 403 | 82 | 7.0 | 26.8 | 68.3% |
| FDLE Alert | 325 | 2 | 0.5 | 1.1 | 100.0% |
| Special Event | 184 | 14 | 6.4 | 37.4 | 85.7% |
| Interagency Coordination | 89 | 0 | — | — | — |
| PSA | 56 | 1 | 0.0 | 0.0 | 100.0% |
| Road Work - Emergency | 50 | 4 | 0.3 | 27.2 | 75.0% |
| Wildfire | 48 | 15 | 0.0 | 18.4 | 80.0% |
| Weather | 32 | 1 | 0.0 | 0.0 | 100.0% |
| Traffic Signal Flash | 25 | 0 | — | — | — |
| Pedestrian | 18 | 12 | 0.0 | 14.2 | 91.7% |
| Flooding | 14 | 1 | 0.0 | 0.0 | 100.0% |
| Bridge Work | 10 | 1 | 0.0 | 0.0 | 100.0% |
| Traffic Signal Dark | 9 | 0 | — | — | — |
| Bridge Closed | 2 | 0 | — | — | — |
Response = same-unit notification to arrival; unmatched pairs excluded. Zero-minute intervals may reflect self-discovery. Differences do not isolate staffing, distance or incident complexity.
2026 is partial. Historical chronology only; earlier response summaries are in Operations. Rankings are descriptive, not forecasts.
How traffic conditions relate to incident demand. These associations provide context rather than evidence of cause.
Speed versus TTI · Pearson r
-0.86
Incident count versus TTI · Pearson r
-0.01
Matched month/corridor/hour groups
96
UrbanSDK coverage: 2026-08, 2024-05. Historical aggregate correlations; speed and TTI may contain overlapping information.
Traffic profiles use year, month, corridor and hour; incident counts also use event type. County-specific traffic relationships are unavailable. Each month/corridor/hour group contributes one observation. Corridor and time effects may confound correlations; no causal or advance-warning effect is established.
Which evidence is available, which inputs can support modeling, and where the data still has gaps.
| Factor | Available evidence | Prediction use |
|---|---|---|
| Historical location & temporal context | Compare corridor, hour, weekday and seasonal demand. | Included in time-tested count models. |
| Severity | 134,382 known ATIS categories; 24,523 intermediate/major. Severity is assigned after the event. | Descriptive only; not a pre-incident feature. |
| Response performance | Measure observed notification-to-arrival intervals. | Operational outcome; not an incident-risk input. |
| UrbanSDK speed, TTI & Collision Index | Compare historical traffic context where periods overlap. | Not used in current forecasts; short coverage and index provenance limit as-of validation. |
| ActiveVision & live congestion | Analyze API event mix and reported status separately. | No time-aligned pre-incident detector history yet. |
| Weather, geometry & lighting | Current weather and road geometry are available for context. | No matched historical weather, lighting or pavement training table. |
| Secondary crashes & lane blockage | Not reliably labeled in the current processed snapshot. | Cannot estimate secondary-crash probability or reduction yet. |