Read the estimate without mistaking it for an incident report
What does a distance–speed–delay exercise tell you, and what must be verified elsewhere?
This fixed, hypothetical aircraft-response scenario lets you compare travel-time assumptions. The location, aircraft, agency names, coordinates, engagement counts, restriction labels and timeline are authored fixtures. This page has no live news, NOTAM, dispatch or agency connection and does not establish that the depicted incident occurred.
The time estimate is arithmetic, not a response commitment or routing result. The radius is a scenario display input, not a safe separation distance, hazard assessment or authorized airspace boundary. This exercise cannot dispatch resources, determine flight permission or guide an actual emergency.
Try a worked example
The baseline uses 4.2 miles at 48 mph plus 3.25 minutes of delay: (4.2 ÷ 48) × 60 + 3.25 = 8.5 minutes. The longer-route preset uses 10.5 miles at 55 mph plus 2 minutes: 13.4545… rounds to 13.5 minutes. Changing only the radius does not change this formula.
Separate travel arithmetic from operational evidence
The calculator rounds distance ÷ speed × 60 + delay to one decimal place. It assumes a constant speed over the entered distance and adds one delay. It has no road network, traffic, vehicle availability, turnout history, terrain model or uncertainty interval. Doubling distance doubles only the travel component; it does not double the separately entered delay.
USFA describes command and coordination as including on-scene tactical work, incident support, policy decisions and public communication. Local authorities commonly manage incidents through their communications and dispatch systems. These functions cannot be inferred from a travel-time score or a button labeled as a support preset. USFA: NIMS command and coordination
Verify airspace restrictions through the responsible source
FAA explains that TFRs temporarily restrict aircraft, including drones, and are communicated through NOTAMs. Its official TFR list supplies active restrictions and links to their NOTAM details. A real restriction needs its applicable area, altitude, effective time and conditions; a fixed circle or invented notice number cannot establish those details. FAA: Temporary Flight Restrictions
This app does not retrieve FAA data. Its original restriction status, 8,000-foot claim and notice number were unsupported scenario text. The selectable radius is measured in miles and is drawn on the optional map, but its shape does not demonstrate a current TFR or a safe hazardous-materials perimeter.
Understand the map and export boundaries
The optional Leaflet view draws fixed scenario and staging markers. The coordinate separation is not used to calculate the entered route distance. Radius-slider input resizes the Leaflet circle; the offline fallback is a static, unscaled illustration. Reset restores the numeric inputs and the Leaflet circle radius together.
The scenario JSON records inputs, the current rounded estimate and fixed sample engagement counts. Its timestamp is the export-generation time, not an incident observation or publication time. Copy and Download create a local record; they do not send a dispatch, verify a source or save a reloadable plan. The agency and incident identifiers remain legacy fixture strings and are explicitly marked hypothetical.
Keep a practice scenario separate from deployment
FEMA’s resource-management training says responders should await official deployment notification rather than self-deploy. The support preset here only changes local assumptions and a fixture unit label. For a real incident, use the responsible authorities’ instructions and their incident communication channels; the page’s sample feed is not a substitute. FEMA IS-700.b: resource management
Sources and further reading