Escalante flood warnings carried the threat into November 2

Nearly 400 cubic feet of water per second was moving through the Escalante River near Escalante, according to a late-night National Weather Service warning. That reported flow was one measure of a flood threat that carried into the early hours of November 2, 2026—not a measurement of water over a road, or proof that a crossing was passable. ¹

The later warnings changed the timetable we reported on November 1. The Escalante Basin warning then had a scheduled 4:30 p.m. Mountain Standard Time expiration. A 4:12 p.m. bulletin moved that deadline to 10:30 p.m.; a new warning issued at 10:33 p.m. ran until 2:30 a.m. on November 2. For drivers, hikers and campers, the documented threat extended well into darkness. Both scheduled deadlines have since passed, and neither establishes present conditions. ^{2 1}

The afternoon bulletin covered central Garfield County and northeastern Kane County in southern Utah. It named Escalante, the area along Hole in the Rock Road and local slot canyons as places that could experience flooding. The overnight warning covered south-central Garfield and northeastern Kane and also named Boulder. Those were warnings for portions of the counties, not statements that every location across both counties faced identical conditions. ^{2 1}

The distinction between successive warnings and uninterrupted coverage matters. Three minutes separate No. 14’s stated 10:30 p.m. end from No. 16’s 10:33 p.m. issuance. The records establish the two periods; they do not establish continuous warning coverage through those minutes or an explicit replacement action. Nor does that interval establish a pause in flooding. All of these product times use MST, seven hours behind UTC. ^{16 30}

The 4:45 p.m. deadline in our earlier report belonged to a different warning area: southwestern Garfield County and central Kane County. It was not the Escalante Basin deadline. Keeping those areas separate is essential to understanding what the later bulletins changed.

At 4:09 p.m. on November 1, Doppler radar and automated rain gauges indicated heavy rain, with 1.5 to 2.5 inches reported to have fallen. Up to another half inch was possible. Forecasters described Escalante Basin flooding as ongoing or imminent, with streams, rivers and slot canyons carrying high flows from recent rainfall. Further rain was expected to maintain those flows before they receded. ²

The overnight bulletin’s 10:31 p.m. radar-and-rain-gauge assessment repeated the same 1.5-to-2.5-inch range and allowed for up to another half inch. That repetition is not evidence that a second 1.5 to 2.5 inches fell between bulletins. It is also not a claim that every point in the warned area received the same amount. The additional half inch was a forecast possibility during this episode, not an observed total or a current forecast. ¹

The late-night warning said flooding was ongoing or expected to begin shortly. Its threatened-location list identified places that could flood; it did not confirm flooding at every named community, road or canyon. The practical instructions were direct: turn around at flooded roads, use particular caution at night, and keep hikers and campers away from streams and creeks. ^{1 2}

The river figure requires similar care. USGS identifies station 09337500 as Escalante River Near Escalante, Utah. The nearly 400-cubic-feet-per-second figure comes from the late-night NWS warning record; independent verification of that individual observation was not available. The warning’s 10:31 p.m. time belongs to its rainfall assessment and has not been established as the river reading’s timestamp. ^{1 21 25}

Discharge describes the volume moving downstream each second. It cannot, by itself, tell a traveler how deep water is at a particular crossing. Nor should this figure be combined with older reported flows to manufacture a verified recession or an improvement in access.

The update answers an important part of our November 1 account: the Escalante threat did receive later warning coverage, first into the evening and then into early November 2. What remains unestablished is whether another warning followed, what subsequent water levels were, and which routes were actually flooded, closed or reopened.

No independently verified, dated closure or reopening for Hole in the Rock Road, local crossings or named canyons has been established in this update. Nor has a verified evacuation order, rescue total, injury report or structural-damage assessment for these Escalante locations. That is a limit on what can be reported—not evidence that no impacts occurred.

Separate questions from our November 2 report on renewed evacuation instructions near Aneth and Bluff also remain unresolved. These Escalante bulletins concern a different area and do not update those instructions.

For Escalante travelers, the distinction is straightforward: the later warnings documented flood risk after the afternoon deadline, but their scheduled expiration did not inspect a road, a crossing or a canyon. An elapsed warning is not an all-clear.