Coverage & Response Reach
Coverage Stats FDID TX-48F77
Average Response Time 0.0 min
90th Percentile 0.0 min
% within 8 minutes 0%
Beyond Reach (Incidents) 0
Mappable — 991 of 1,389 0%
Map Layers
4 min 8 min 12 min
Straight-line radius at ~0.6 km/min. Road networks aren't circular — actual reach varies. Not measured coverage; a routing engine (Valhalla) would replace these with real isochrone polygons.
Map Design
Dispatch Pulse — 24-Hour Rhythm
🌙 Overnight
00:00
Weekly Call Pattern
Weekly Call Pattern Day × Hour activity density
00
03
06
09
12
15
18
21
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Lower Higher call volume
Co-response Resource Patterns
Prototype aggregate across 851 mock incidents for FDID TX-48F77.
Common responding-unit pairings
Engine 1 + Ladder 1 208 incidents · 24%
Avg arrival order 1.2 / 2.1
Engine 2 + Medic 2 172 incidents · 18%
Avg arrival order 1.5 / 1.8
Rescue 1 + Engine 3 126 incidents · 12%
Avg arrival order 1.7 / 2.4
Engine 1 + Mutual Aid Engine 4 108 incidents · 8%
Avg arrival order 1.4 / 3.2
Mutual-aid frequency
15%
132 incidents include an outside company, averaging 1.9 outside companies when mutual aid appears.
County Engine 4Township Ladder 5Medic 7
Incident categories with multiple companies
Structure / outside fires 3.4 avg companies
68%Gas leaks & hazardous conditions 2.7 avg companies
52%EMS with lift/rescue assist 2.1 avg companies
31%Commercial alarms 2.0 avg companies
28%Detailed apparatus/company participation is often incomplete in NFIRS. Treat these resource patterns as a planning prototype; authoritative unit-level co-response analysis may require NERIS or supplemental local dispatch/CAD data.