Blog

Field notes: the night shift that waited for the sky to clear

Night sky with wispy clouds parting to reveal stars.

It's 2:40 a.m. and the gauge at the north bridge has already logged eleven inches since the front stalled over the ridge. You've been in the EOC since the call came in at ten, running the watch log, fielding radio traffic from two volunteer companies wading through somebody's living room. The river crested an hour ago. What you don't have, and won't have for a while yet, is a clean look at how far the water actually went.

This is the part of flood response nobody puts in the training slides. Not the search-and-rescue, not the shelter intake numbers, not the sandbag logistics. The wait. The sky wait.

Satellites don't care that your county has declared a state of emergency. They run their orbit on their own clock, and a stalled frontal system sitting on top of your flood doesn't hurry up just because incident command needs a boundary. You can request the earliest tasking in the world and still get handed a scene full of cloud. So the duty officer's real skill, the one that never shows up on a resume, is knowing how to wait productively.

You check the overpass schedule. You check it again two hours later because the forecast model just nudged the frontal boundary east. You tell the shift coming in at six what to expect, and what not to expect, because the last thing anyone needs at a 7 a.m. briefing is a commander assuming there's a map when the parcel that matters is still sitting under a sky full of cumulus.

Somewhere around four, one of the GIS volunteers mentions that a pass is scheduled for late morning and the cloud forecast looks "maybe okay." Maybe okay is not a phrase you can put in a situation report, so you keep logging field reports instead: water over the county road at mile marker 12, a mobile home park partially surrounded, a retention pond that's clearly overtopped behind the strip mall. These become the stand-in for a map. They're honest, they're useful, and they're also slow and incomplete in a way that starts to matter by hour eight, when the question stops being "where is the water" and starts being "where is the water compared to yesterday, and is it moving toward the elementary school."

The old hands have a rhythm for this. They don't panic about the gap. They know flood response has always had a lag between event and extent, because optical satellites need a cloud-free look the same way a search team needs daylight. What's changed, gradually and without anyone announcing it, is how much gets done in that gap now.

Field reports still matter. Social posts geotagged from someone's porch still matter. But once that first usable pass comes through, the time it takes to turn it into something a coordination meeting can use is the part that's shrunk. A GIS tech used to pull the scene, delineate standing water by eye, check it against road networks, format it, and hand it over three or four hours after the pixels existed. That gap, the one between "we finally have a picture" and "the room finally has a map," is the one worth shrinking.

That's the whole premise behind a standing-water extent map built to be ready the moment the sky cooperates, delivered as a numbered brief instead of a raw scene somebody still has to read by hand. The wait for cloud-free imagery stays exactly as long as the weather makes it. What gets shorter is everything that happens after the pixels land.

Somewhere out there tonight, another duty officer is checking the same overpass schedule, nudging the same forecast, telling the same incoming shift that the picture is close. If you're the one holding that watch log, it's worth having something ready for the moment the sky finally clears.

Back to the blog