WHYAMERICASUCKS.COM
PUBLIC SITE MAPLatest Stories
menuMenu
Editorial cover for a Port Westward story about emergency access, shared responders, and transport burden
Emergency Story

The Port Westward Emergency Story Runs Through Narrow Roads And Shared Responders

The emergency-response side of the NEXT refinery fight is not hypothetical paperwork. The Port says the site is still served by narrow county roads not built to typical heavy-truck standards, the Corps says the project would add rail, truck, and vessel movements, and DEQ's spill-response story leans heavily on existing terminal crews, boom, vessels, and shared responder networks.

Published
April 8, 2026

Records Research Desk

Updated
April 8, 2026

Standards Review

Investigation
Environment

USACE + DEQ + Port response record

SeriesPort Westward File16 linked stories

A linked reporting file on the NEXT Renewable Fuels proposal, Port Westward infrastructure, wetlands, levees, fisheries, public finance, and lower Columbia risk.

Byline

Records Research Desk

Reviewed By

Standards Review

Port WestwardEmergency ResponseRoadsSpill RiskFire District
EnvironmentRecords Research DeskStandards Review6 min read

The access story is already part of the Port's own planning record

The Port's 2024 strategic business plan says the main route into Port Westward is Kallunki Road connecting to Quincy Mayger Road, both described as narrow county roads with about 24 feet of pavement and not built to typical standards for large truck traffic.

That matters because this is not a future activist talking point. It is the Port's own description of the access system serving an industrial park where NEXT is expected to operate.

The federal review makes the transport burden concrete

The Corps says the project could require up to 208 trains a year, 720 trucks a year, and 171 ocean-going vessel movements a year. Once you put those numbers next to the Port's road description, the emergency-response question becomes more than a simple on-site refinery question.

It becomes a corridor question: how responders, roads, rail crossings, and dock operations all behave when the industrial tempo rises.

DEQ's spill-response story relies on existing terminal infrastructure and shared responders

DEQ says Columbia Pacific Bio-Refinery, the existing terminal operator at Port Westward, stages more than 6,500 feet of containment boom, two deployment vessels, and works with Clean Rivers Cooperative, the U.S. Coast Guard, and other responder agencies on regular spill drills. DEQ also says Maritime Fire and Safety Association becomes an additional oil-spill response organization once an ocean-going vessel enters the Columbia.

That is useful capability, but it also means the response plan is not a self-contained NEXT-only system. It is built around a shared industrial-response network already operating at the Port.

Even the Port itself treated fire coordination as a governance issue

In June 2025, the Port adopted Resolution 2025-19 authorizing an intergovernmental agreement with Clatskanie Fire District. The Port's public page does not spell out every operational term on its own, but the existence of the agreement is still telling.

It shows emergency capacity at Port Westward is not assumed to be automatic. It is something public institutions are actively arranging and formalizing.

What this story does and does not claim

I am not claiming I have proved local responders cannot handle the project, or that the presence of shared spill-response assets means the system will fail. Those stronger claims would need more than the current public record gives us.

What I am claiming is narrower and source-backed: the emergency story around Port Westward runs through narrow county roads, rising transport volumes, existing terminal spill crews, state reporting rules, and formal public-fire coordination, which means emergency readiness belongs squarely in the project's public-interest debate.

More Stories

Keep Reading

These related pieces come from the same public-records layer, but follow different investigations and reporting paths.