Source Report: “A mother and her 5-year-old were shot and wounded in their car when a gunman followed the family on the way home, authorities in Florida said.” —
@ABC on X | Reported Sept 15-16, 2026.
Step Inspection:Phase 3 of 4
21:20 EST • Apartment Complex Origin
Disturbance Escalation
Disturbance involving juveniles and adults occurs. Family departs scene in personal vehicle unaware an armed subject has targeted their movement.
21:35 EST • Arterial Transit Corridor
Targeted Tailgating & Stalking
Suspect vehicle trails victim car along unlit transit corridors. Limited route variance and residential choke points impede evasion.
21:45 EST • SE 11th Avenue, Ocala FL
Vehicle Pursuit & Gunfire Opened
Suspect vehicle overtakes and discharges weapon into family vehicle. Mother sustains hand wound, 5-year-old child wounded in chest; uninjured father halts and summons 911.
21:52 EST • Emergency Trauma Ingress
Dispatch Arrival & Canvass Alert
Marion County / Ocala Police triage victims to regional trauma center. Doorbell camera canvass launched across SE 11th Avenue perimeter.
Verified Source Details:
• Victims: Mother (wounded hand), 5-year-old child (wounded chest, stabilized), Father (uninjured driver).
• Location: Near Southeast 11th Avenue, Ocala, Florida.
• Suspect: Fled scene; active community surveillance and camera review requested by investigators.
Tactical Assessment:Critical pursuit threat detected. Suspect followed vehicle from prior altercation into residential zone with restricted egress. Gunfire initiated prior to vehicle arrival at destination.
Primary Safety Countermeasure: Divert immediately toward lighted public service hubs (Fire/Police Station or 24hr commercial plaza) rather than private driveway; contact 911 dispatch while mobile.
Simulated Marion County Dispatch Window4.8 - 6.5 Minutes
• Call Triage: ~45 seconds
• Unit In-Route: ~3.5 minutes
• Trauma Medic Dispatch: Concurrent Code 3
• Perimeter Canvass: Active on SE 11th Ave
Successfully generated and exported abc-news-incident-analysis-80.json
Understanding the Route Risk Score & Dispatch Simulation
How does the route safety analyzer calculate threat scores and dispatch response tiers?
This interactive tool combines an illustrative four-step timeline of an Ocala, Florida shooting incident with a heuristic route risk calculator. The calculator starts from an arbitrary base score of 50, then adds or subtracts predefined integer weights depending on time of day, escape options, pursuit distance, and surveillance levels. A score of 75 or above assigns the 'Urgent Law Enforcement Dispatch' tier, 50 to 74 assigns 'Elevated Stalking Threat', and lower scores designate 'Monitoring & Precautionary'.
The risk scoring engine and estimated dispatch windows (e.g., 4.0–5.5 minutes) are illustrative educational fixtures implemented entirely in local client-side JavaScript. They do not reflect official Marion County Sheriff's Office or Ocala Police Department dispatch algorithms, real-time CAD telemetry, or validated criminological risk assessments.
Try a worked example
At initial load, the controls show Night (+15), Low escape route (+18), 3.2 miles (+3), and Moderate surveillance (-2), totaling 84 (Urgent Dispatch tier). Change 'Escape Route Options' to 'High (Multiple highway outlets)' and the score subtracts 5 instead of adding 18, dropping the Composite Risk Score by 23 points to 61 and updating the tier to 'Elevated Stalking Threat'.
Risk Formula Breakdown
The script calculates score = 50 + time_adjustment + escape_adjustment + distance_adjustment + surveillance_adjustment, bounded between 15 and 99. Night adds 15 points (dusk adds 8, daylight 0). Low escape adds 18 points (moderate adds 8, high subtracts 5). Pursuit distance contributes Math.round((distance / 8.0) * 8). Surveillance adjusts score by +6 for low, -2 for moderate, and -10 for high.
Incident Timeline Context
The four timeline phases reconstruct details from initial public reporting by ABC News regarding a shooting on Southeast 11th Avenue in Ocala, Florida. The exact chronological minute markers and step transitions are pedagogical representations constructed to demonstrate how escalating transit stalking scenarios unfold.
Reading the saved score and timeline state honestly
Read the explanation
This saved timeline is an unverified news fixture. Its score and dispatch labels are an unvalidated heuristic, not an estimate of actual danger or emergency response. The arithmetic starts at fifty. The default night selection adds fifteen, low escape planning adds eighteen, three point two miles contributes three after rounding, and moderate surveillance subtracts two. The total is eighty four. The growing bar shows fifty, sixty five, eighty three, eighty six, and finally eighty four on a shared scale. Read the implemented numbers carefully: the option labels say plus twenty two and plus twenty eight, but the source actually adds fifteen and eighteen. The video explains the saved implementation rather than endorsing those labels. The distance contribution simplifies to rounding miles to the nearest integer, because dividing by eight and multiplying by eight cancels. With day, high escape planning, and moderate surveillance selected, the fixed contribution is fifty minus five minus two, or forty three. At six point four miles, the rounded contribution is six and the score is forty nine. At six point five miles, it becomes seven and the score is fifty. The saved category changes at fifty, and changes again at seventy five. These are code thresholds, not measured risk boundaries. The clamp is fifteen through ninety nine, but the actual native controls can only reach thirty six through ninety seven, so neither clamp limit is reached by valid visitor selections. Timeline selection is separate from scoring. The page initializes phase three of four. Previous moves to phase two and phase one, where another previous action leaves it at one. Next and direct timeline clicks select the other phases, with the same one through four bounds. Changing phase alone does not change the score. The JSON export records the current phase, chosen factors, score and category, plus an actual export timestamp. Reset returns phase three and the default eighty four points, and hides the export feedback. A label saying verified analysis does not prove the underlying incident or the heuristic has been verified. This local draft preserves the existing tool while explaining those limits.