Olympic Pipeline Explosion — Whatcom Creek, Bellingham

The first 911 calls at 3:30 PM reported a petroleum odor near Whatcom Creek. This is ambiguous in isolation. Callers near waterways sometimes report fuel smells from boat traffic, spills, or stormwater. Without pipeline awareness, a dispatcher has no framework to evaluate whether this is an isolated nuisance or the beginning of a catastrophic industrial event.

The question this raises for your center: What is your protocol when you receive multiple calls about an unexplained odor near a waterway or green space? At what call volume or geographic concentration does it trigger something beyond a standard hazmat investigation? Is there a query built into your CAD that prompts the dispatcher to check whether a pipeline corridor runs through that area?

In Bellingham, the accumulation of calls over 90 minutes eventually triggered a hazmat response — but the response came from call volume, not from any framework that recognized what was likely happening. The difference between those two paths is the 90 minutes.

At approximately 4:15 PM, Olympic Pipeline controllers in Renton made the decision to restart the pumps — adding thousands of additional gallons to the creek — while Whatcom County dispatchers were actively receiving calls from the public about gasoline smells near that same creek. These two facts existed in parallel, completely disconnected from each other.

This is the structural failure the Bellingham incident exposed. The PSAP is the community's emergency hub. But the information stream from a private-sector pipeline operator's SCADA system in a remote control center runs on a completely different track. The EAP is supposed to be the bridge. When the EAP notification chain doesn't function — when the operator doesn't call — the PSAP is the last to know about an event they are simultaneously responding to from the public side.

The question for your center: if a pipeline operator in your jurisdiction detected a release right now, do you have any reason to believe they would call you before you received the first public 911 call? Do you know who they would call? Is that contact verified in the NENA PIPE database?

When Bellingham Fire's Hazmat Team was dispatched at approximately 4:34 PM, they were responding to an odor complaint — not a known gasoline pipeline rupture. The responders who arrived at Whatcom Creek at 4:45 PM encountered overwhelming fumes and gasoline flowing in the creek. A firefighter on the footbridge near the water treatment plant was near the explosion site when ignition occurred ten minutes later.

Dispatchers can only brief responders on what they know. At 4:34 PM, the known facts were: multiple callers reporting gasoline smell near Whatcom Creek, one caller reporting creek discoloration. A hazmat team was the appropriate response. What dispatchers could not tell those units was that they were walking into a situation where 277,000 gallons of gasoline had been accumulating for over an hour and the vapor cloud had reached explosive concentration.

The training point is not that dispatchers failed — it is that the EAP notification failure left dispatchers without the information they needed to give responders a meaningful safety briefing. An effective EAP would have had Olympic Pipeline calling the PSAP at 3:25 PM, giving dispatchers the information to brief units: confirmed pipeline release, product type, approximate volume, hazard zone, and operator contact on scene.

At 4:57 PM, Olympic Pipeline operators called the fire department dispatcher to report a "possible release of product into Whatcom Creek." At that moment, the dispatcher was managing an active mass casualty event — units on scene, two critically burned victims being transported, evacuation underway, Interstate 5 closed, and the creek on fire. The pipeline operator was calling to report something the PSAP had been managing, from the public side, for the past 90 minutes.

This call — arriving after the event — still has value. The operator can tell dispatchers: the product type (gasoline), the approximate volume released, where the upstream valve closure is, what the pipeline runs, and who the on-scene technical contact is. All of that is operationally useful for an ongoing hazmat response even after ignition. The dispatcher should take that call, extract the technical information, and route it immediately to the incident commander.

The lesson is not that the operator's late call was useless. It is that a timely call — at 3:25, when the SCADA alarm activated — would have meant a fundamentally different response. The 4:57 call is what you get when there's no functioning EAP notification. The 3:25 call is what the EAP is supposed to produce.

Once the fire was underway, the PSAP was managing a cascading infrastructure event. Gasoline vapor at explosive concentrations had entered the municipal sewer system — meaning any ignition source in a storm drain or manhole anywhere downstream could produce a secondary explosion. The fire was moving down a living creek toward downtown Bellingham and Bellingham Bay. The Coast Guard closed the bay. Interstate 5 was closed. The water treatment plant was severely damaged.

This is the multi-agency coordination challenge that follows a pipeline event: it is not contained to the initial rupture site. Dispatch coordination has to account for the downstream geography of the product — where is the creek going, what infrastructure is in the path, which agencies own what piece of the response, and who is running the unified command?

For training coordinators: this is the scenario design question for a tabletop exercise. Where does your nearest major pipeline run? If it ruptured into a waterway, where does that waterway go, what is downstream, and who handles what?