I-80 partly reopened near Parleys Canyon—but no all-clear was confirmed

The crash disrupted access to the canyon in Salt Lake City on October 30, 2026. KUTV, reporting information from the Utah Department of Transportation, said the stretch between I-215 and Parleys Canyon had reopened while the restriction at milepost 128 remained. The distinction matters: restoring traffic on an approach does not necessarily restore passage through the crash location.⁠1

Whether that remaining restriction has since cleared is not established. No subsequent full-clearance notice or confirmed reopening time was available for this report. The closure described here is the last reported condition, not an independently verified account of the road’s status now.

The reported crash location was eastbound I-80 at milepost 128, near 3200 East and the canyon mouth. That identifies a point on the road. It does not establish two endpoints for the remaining closed section, its length, or which connections drivers could use after each update.⁠1

Earlier restrictions reached several roads feeding the interchange. UDOT’s alert listed southbound Foothill Drive access to eastbound I-80, the connection from westbound I-80 to southbound I-215 East, and the connection from northbound I-215 East to eastbound I-80 among the affected movements. The agency urged drivers to avoid the area.⁠1

A later partial update identified northbound I-215 East access to eastbound I-80 as reopened. That restored one previously blocked connection; it did not establish that the remaining eastbound restriction at milepost 128 had cleared. Nor does it justify carrying every earlier ramp restriction forward as though nothing had changed.

For drivers, these were separate questions: could they enter eastbound I-80 from their approach, and could they continue past the crash? A reopening notice answering the first question was not enough to answer the second. The heavy-delay warning remained consequential even as some access was restored.⁠1

UDOT’s initial clearance estimate was 7:58 p.m. Friday. Its later alert supplied no estimated reopening time, replacing that earlier projection with uncertainty. KUTV’s article explicitly preserved both stages: an earlier expected clearance and a later alert without a reopening estimate.⁠1

The 7:58 p.m. figure therefore cannot be treated as the time traffic resumed. It was a forecast, not a recorded reopening, and there is no confirmed replacement time to offer. Using the old estimate as a deadline would give drivers a confidence the later alert no longer supported.

The report’s date also needs to be read in Utah’s local time. KUTV first published its article at 7:29 p.m. Mountain Daylight Time on October 30. Its metadata records that as October 31 in UTC. Those timestamps describe the same publication moment—not two different crash dates—and neither establishes the precise time of impact.⁠1

Semitrailer involvement is supported, but a confirmed cause, an official injury assessment and an official account of the driver’s condition were not established for this report. That gap should not be read as evidence that nobody was hurt.

The unresolved traffic question is narrower than whether the entire approach was closed or open. It is whether the restriction at milepost 128 subsequently cleared, and which connecting routes became usable. The last reported picture was a partial reopening with a remaining closure—not proof of a continuing full closure, and not proof that the route was fully clear.