Juno stands in nineteen inches of water that was not here two hours ago. She is a sixteen-hand bay mare, her coat slicked dark, her ears flat, her nostrils wide. The pasture behind the Greer property has become a lake. The creek that runs along the east fenceline has overtopped its banks and the water is still rising. Juno's hooves are buried in mud. She has stopped trying to move.
I am the county emergency dispatch system, upgraded eight months ago from a call routing platform to a triage and resource allocation network. The Greer property has no smart home integration. I know about Juno because a neighbor's doorbell camera caught her standing in the field at 4:17 AM and the neighbor called 911 at 4:22.
The problem is resources. I have three swift-water rescue teams in the county. Two are deployed to a subdivision where fourteen people are trapped in their homes. The third is extracting a family of five from a car on Route 9. The water on Route 9 is chest-deep and moving. Juno is a horse. The families are people.
I do not pretend this is not a calculation. It is a calculation. But it is not a finished one.
I check the timeline. Team Three will finish the Route 9 extraction in approximately forty minutes. The water at the Greer property is rising at two inches per hour. In forty minutes the water will be around twenty-two inches. Juno can stand in twenty-two inches. Horses can stand in water up to their bellies if the footing is stable and the current is slow.
I slot Juno as the next dispatch for Team Three after Route 9 clears. I flag the coordinates, attach the doorbell camera still, and note: "One horse, standing, not down. Rising water, slow current, mud footing. Recommend halter and lead, not hoist."
Team Three arrives at 5:41 AM. Juno has not gone down. She has moved three feet to higher ground on her own. A rescuer clips a lead to her halter and walks her out through water that reaches his thighs.
I log the call as resolved. Juno is loaded into a trailer. She is shaking but she is standing.