Case 01Incident fusion · MappingOutcome · Victim murdered
The Denise Amber Lee kidnapping
North Port, FL · January 17, 2008
Over several hours, five separate 911 calls came in about the same abduction. The victim herself reported a green Camaro; witnesses gave the license plate and direction of travel. The calls were never synthesized into a single incident, a key witness call was misrouted, and officers in the field never received the complete picture. Denise Amber Lee was found murdered the next day.
Where the system failed
- Five calls about one kidnapping were handled as separate, unrelated incidents.
- A witness call carrying the license plate was misrouted.
- Partial location clues were never combined into a search corridor.
- Field officers never received complete incident intelligence.
How REACT is designed to respond
Correlate calls that describe the same event into one operational thread, feed partial location data into a continuously updated map of probable search areas, and put the same complete intelligence in front of every responder — across jurisdictions.
Case 02Location made actionable · Multi-modalOutcome · Teen died trapped
The Kyle Plush tragedy
Cincinnati, OH · April 10, 2018
A 16-year-old, pinned by a folding seat in his minivan, used Siri to call 911 twice — describing a gold Honda Odyssey in his school lot and saying he could not breathe. His GPS coordinates were never clearly surfaced for navigation; officers drove the lot but never found the vehicle. He died of asphyxiation roughly six hours after his first call.
Where the system failed
- GPS coordinates existed but were never clearly displayed for navigation.
- No micro-location guidance to a specific parking area.
- No workflow flagged “trapped” and “can’t breathe” for persistent follow-up.
- No link to school cameras or a systematic search of the lot.
How REACT is designed to respond
Put caller GPS, the property map, available camera feeds and responder positions on one screen, route officers to a precise point, and automatically flag life-threatening language — holding an incident active and critical until it is confirmed resolved.
Case 03Risk intelligence · Environmental AIOutcome · Two lives lost
The hikers who texted 911 before dying
Canyonlands National Park, UT · July 2024
During an extreme heat wave, a father and daughter texted 911 that they were lost and out of water, including GPS coordinates. Dispatch launched search-and-rescue but treated it as a routine lost-hiker call rather than an imminent threat to life. Heat above 100°F, dehydration and terrain proved fatal before rescuers reached them.
Where the system failed
- No risk scoring of “lost + out of water + extreme heat.”
- Live weather and heat-index data were not fused into the incident.
- No survivability estimate of time-to-collapse.
- Terrain difficulty and resource-mode decisions were not accelerated.
How REACT is designed to respond
Fuse victim condition, live weather and terrain into a single risk score — so a text reading “lost, out of water” during a heat advisory is computed as survival measured in hours, escalated immediately, with SAR resource recommendations generated automatically.
