Date
June 10, 1999
Location
United States
Industry
Oil & Gas
Access vector
Not applicable
OT targeting
None
Primary peril
Loss of Containment
Impact duration
608 days

Olympic Pipeline rupture and fire, Bellingham, 1999

DeNexusIncident analysis
Cover image for the incident analysis: Olympic Pipeline rupture and fire, Bellingham, 1999

The incident path, stage by stage

Each stage of the attack, from intent to financial loss, with this incident’s path highlighted. Solid cells are confirmed, dashed cells are reported by a source but not confirmed, dotted cells are implied by the facts, and Unknown marks what is not publicly known. Click a stage title or a highlighted cell to read that part of the analysis.

Scroll sideways to see every stage.

    IT stagesOT stagesConfirmedPerilReportedImpliedUnknownNot in pathLink not established DeNexus analysis of public sources, as of October 22, 2026
    On this page

      Highlights

        What happened. On June 10, 1999, a gasoline pipeline operated by the Olympic Pipe Line Company ruptured in Bellingham, Washington, and released about 237,000 gallons of gasoline into two creeks[1]. About an hour and a half later the gasoline ignited and burned along about 1 1/2 miles of creek; three people died and eight more were injured[1].

        Why it matters. No attacker was involved, but the control system was part of the failure: it was unresponsive at the critical moment because of database work done on the live system[1]. It shows how a stalled control system and an untested safety device can turn a damaged pipe into a fatal fire.

        About this analysis. This analysis sets out what is known, stage by stage, for an accidental event. It reflects the best available information as of October 22, 2026; new information could confirm, change or discredit parts of it.

        Highlights

        • The National Transportation Safety Board (NTSB) found five probable causes, from pipe damage done by a contractor in 1994 to an untested pressure relief valve and a control system left unresponsive by database work on the live system[1].
        • The release and fire killed an 18-year-old and two 10-year-old boys, injured eight more people, damaged a water treatment plant and destroyed a house[1].
        • The 37-mile segment stayed shut until February 2001[2]. Amounts stated by the parties come to about $236.5 million, including a $75 million settlement with two families and $36 million in fines and penalties[3][4].
        • NTSB found no evidence of unauthorized access, but documented a dial-in route and an unprotected bridge to the business network as a latent weakness[1].

        Attack flow

        • Updated: 2026-10-22
        • Intent: Accidental [confirmed]
        • Threat actors: Not applicable [not in path | Accidental event, no attacker]
        • Access vector: Not applicable [not in path | No attacker]
        • IT impact: Not in path [not in path | No attacker; the stall came from the operator’s own work]
        • OT targeting: Not applicable [not in path | No attacker]
        • OT sophistication: Not applicable [not in path | No attacker]
        • OT impact: Loss / Denial of View [confirmed | SCADA unresponsive, per NTSB]; Loss / Denial of Control [confirmed | commands not executed]; Loss of Protection [confirmed | untested relief valve]
        • Perils: Loss of Containment [primary]; Fire [secondary]; Explosion [reported]
        • Financial losses: Health, Safety, Casualty [confirmed | $75M settlement; $21M fines]; Cyber Incident Response [confirmed | $77M programs]; Assets & Equipment [confirmed | $45M]; Environment [confirmed | $15M; $3.5M]; Business Interruption [confirmed]; Cyber-Physical Incident Response [implied]; Reputation Damage [implied]

        What happened

        The chain began five years earlier. In 1994 a construction crew damaged the 16-inch pipe during a project to modify the Dakin-Yew water treatment plant, and Olympic’s inspection of that work was inadequate. Olympic later misread its own in-line inspection results and did not dig up the damaged section[1].

        On the afternoon of June 10, 1999, the pipeline’s SCADA system was slow or unresponsive from about 3:10 to 3:48 p.m. and did not carry out the controller’s commands. The inlet block valve at Olympic’s Bayview products facility closed, pressure upstream rose sharply, and at about 3:28 p.m. the pipe failed at the damaged section near Whatcom Falls Park; NTSB modeled about 1,433 psig at the rupture site[1]. NTSB puts the release at about 237,000 gallons into Hannah Creek and Whatcom Creek; Washington’s Department of Ecology says more than 277,000[1][5].

        About 1 1/2 hours later the gasoline ignited. An 18-year-old, most likely overcome by the fumes, drowned in the creek, and two 10-year-old boys died of burns the next day. Eight other people were injured, and the water treatment plant was damaged and a single-family house destroyed[1].

        The DOT Office of Pipeline Safety approved the segment’s restart at 70% of normal pressure in February 2001[2]. In December 2002 the two companies and three employees entered pleas in the first criminal case ever brought under the Hazardous Liquid Pipeline Safety Act[6]. A $92 million civil settlement followed in January 2003, and in June 2003 two former Olympic employees were jailed[4][7].

        Intent: accidental

        No attacker, cyberattack or malicious act is documented in any source. NTSB reviewed the SCADA system’s security log and found no evidence of an unauthorized attempt to access it[1]. The control-system failure came from Olympic’s own practice of doing database development work on the system while it was being used to run the pipeline, which NTSB lists as its fifth probable cause[1]. The path on the map starts at Accidental.

        Threat actors: none

        There was no threat actor. The parties held responsible were the operator and its owner. Equilon Pipeline Company, Olympic’s owner at the time and now Shell Pipeline Company, Olympic itself and three employees entered pleas in the criminal case[6][4]. The stage is marked not applicable, and no actor is highlighted on the map.

        Access vector: none used, one left open

        No access vector was used. NTSB did document how the SCADA system could be reached. Direct dial-in access was available to anyone with the number and an authorized dial-up account and password. A bridge joined the control-room network to the company’s administrative network and did not offer protection equivalent to a full-featured intrusion firewall, and no virus protection or access monitoring was built into the system[1].

        That weakness did not cause the rupture; the causal chain runs through NTSB’s five probable causes. It is recorded here because the same investigation found it.

        IT impact: not in this event’s path

        No IT system was attacked, encrypted or wiped. The control system’s failure was an availability problem caused by Olympic’s own change practice, not by malicious code, and no source describes any server, workstation or network device being rebuilt or replaced afterward[1]. Exactly why the system stalled is not established here: this review did not reach NTSB’s full analysis of SCADA performance and rests on the report’s summary findings.

        OT targeting: not applicable

        With no attacker, nothing was targeted. The control system was involved in the event, but as a failing tool in the operator’s hands, not as an object of attack. The OT targeting and OT sophistication stages are both marked not applicable, and the flow on the map goes from Accidental straight to the effects on the pipeline.

        OT sophistication: not applicable

        There is no attacker whose technique could be rated crude or sophisticated. What NTSB describes instead is a set of engineering and operating failures: an inspection misread, a valve fault never investigated, a safety device never tested under approximate operating conditions, and development work done on a live system[1].

        OT impact: lost view and control, and a protection that failed

        NTSB found that the SCADA system was slow or unresponsive from about 3:10 to 3:48 p.m. and did not execute the controller’s commands, leaving it unresponsive at a critical time[1]. In attack terms that is a loss of view and a loss of control, both confirmed, though no one caused them deliberately.

        The physical protection did not hold either. Olympic had not tested all safety devices at the Bayview facility, including the pressure relief valve, under approximate operating conditions before activating it, and the pressure rise ruptured the already damaged pipe[1]. Olympic also had not investigated repeated unintended closings of the Bayview inlet block valve, which closed again that day[1].

        Perils: loss of containment, then fire

        The primary peril is loss of containment: the pipe ruptured and released gasoline into the creeks[1]. Fire is secondary. The gasoline ignited about 1 1/2 hours later and burned about 1 1/2 miles along the creek, and the fire is what killed and burned[1]. NOAA says about 26 acres of habitat burned[8].

        Explosion is reported, not established. HistoryLink says explosions broke windows[9], but NTSB describes ignition and fire, not a separate explosion.

        The pipe failed where a contractor had damaged it five years earlier, at the moment the control system stopped responding.

        Financial losses: what it cost

        This is one of the best documented loss records of its kind. The amounts below were stated by a party, do not overlap, and come to about $236.5 million; the separate settlement with the third family is undisclosed and not included[9]. The Pipeline Safety Trust’s figure of $187 million is that organization’s own tally, not an official total[10].

        Loss evidence

        • Confirmed: Direct business interruption (segment shut for about 20 months); First-party property damage; Third-party property damage liability; Bodily injury; Loss of life; Medical liability; Safety regulation liability; Spills and cleanup; Environmental regulation liability; Legally mandated improvements
        • Reported amounts: $77M Spill-prevention programs under the 2003 civil settlement, Shell $62M and Olympic $15M, DOJ’s estimate of spending[4]; $75M Settlement with the families of the two 10-year-old boys, as reported by The Seattle Times[3]; $45M Total property damages as of January 2002, Olympic’s own estimate, via NTSB[1]; $21M Federal criminal fines, Shell (Equilon) $15M and Olympic $6M, according to DOJ[4]; $15M Civil penalties, Shell $10M and Olympic $5M, split between EPA and Washington Ecology, according to DOJ[4]; $3,544,000 Natural resource damages paid by Olympic’s insurers under a 2004 consent decree[11]
        • Implied: Cyber-physical event response (emergency response, temporary water facilities for about 30,000 customers); Equipment repair and replacement; Startup and return-to-service validation; Public relations response
        • Not supported: Ransom extortion; Network device replacement; Server replacement; Computer and laptop replacement; Embedded device replacement; Industry regulation liability

        The court suspended $5 million of Equilon’s criminal fine so the money could fund community service projects in Bellingham[12]. EPA said $40 million to $55 million of Shell’s program and about $5 million of Olympic’s went beyond legal requirements[13]. No source gives a lost-revenue figure for the shutdown or a cost for the cleanup.

        What this incident shows

        NTSB’s causes are not one failure but a chain, and two links in it are control lessons that apply whether or not an attacker is present. Database development work on a live SCADA system left the operators without a working control system at the critical moment, and a pressure relief valve that had never been tested under approximate operating conditions did not prevent the rupture[1].

        The same investigation found a route into the control system that no one used: dial-in access and a bridge to the business network without full firewall protection or access monitoring[1]. For risk assessment, accidental records like this one calibrate what a pipeline failure can cost, with no attacker involved: three deaths, a 20-month shutdown and about $236.5 million in stated amounts.

        References

        1. National Transportation Safety Board. “Pipeline Rupture and Subsequent Fire in Bellingham, Washington, June 10, 1999.” Pipeline Accident Report NTSB/PAR-02/02, 8 Oct. 2002. ntsb.gov/investigations/AccidentReports/Reports/PAR0202.pdf
        2. “Olympic to Restart Washington State Line.” Oil & Gas Journal, 7 Feb. 2001. ogj.com/pipelines-transportation/article/17264076/olympic-to-restart-washington-state-line
        3. Pfleger, Katherine. “NTSB Faults Pipeline Firm in Deadly 1999 Explosion.” The Seattle Times, 9 Oct. 2002. archive.seattletimes.com/archive/20021009/pipeline09m/ntsb-faults-pipeline-firm-in-deadly-1999-explosion
        4. U.S. Department of Justice. “Olympic/Shell Settle with U.S. and State of Washington for $92 Million in Connection with Fatal Pipeline Rupture.” Press release 03-028, 17 Jan. 2003. justice.gov/archive/opa/pr/2003/January/03_enrd_028.htm
        5. Washington State Department of Ecology. “Bellingham Olympic Pipe Line Explosion - 10 Years Later.” Ecology, 2009. ecology.wa.gov/spills-cleanup/spills/spill-preparedness-response/responding-to-spill-incidents/spill-incidents/bellingham-olympic-pipe-line-explosion
        6. U.S. Department of Transportation, Office of Inspector General. “Two Pipeline Companies and Three Employees Enter Pleas in Criminal Case Arising from June 1999 Gasoline Pipeline Rupture in Bellingham, WA.” 11 Dec. 2002. oig.dot.gov/library-item/30256
        7. U.S. Department of Transportation, Office of Inspector General. “Two Olympic Pipeline Executives Jailed in First-Ever Jail Terms in Pipeline Rupture Case.” 19 June 2003. oig.dot.gov/library-item/31575
        8. National Oceanic and Atmospheric Administration. “Whatcom Creek.” Damage Assessment, Remediation, and Restoration Program. darrp.noaa.gov/node/143
        9. McClary, Daryl C. “Olympic Pipe Line Accident in Bellingham Kills Three Youths on June 10, 1999.” HistoryLink.org, Essay 5468, 11 June 2003. historylink.org/File/5468
        10. Pipeline Safety Trust. “The Tragedy.” Pipeline Safety Trust. pstrust.org/olympic-pipeline-disaster/the-tragedy/
        11. United States Bankruptcy Court, Western District of Washington. “Consent Decree and Settlement Agreement, In re The Olympic Pipe Line Company.” Case No. 03-14059, Nov. 2004, via Pillsbury Winthrop Shaw Pittman. pillsburylaw.com/a/web/gr4W1W8xoyRwFvtR44csZ2/20041112-the-olympic-pipe-line-company-cd.pdf
        12. U.S. Environmental Protection Agency. “Two Companies; Three Former Employees Sentenced in Fatal Washington State Gasoline Pipeline [Explosion].” News release, 27 June 2003. epa.gov/archive/epapages/newsroom_archive/newsreleases/112d8491584a86e28525704b00725bac.html
        13. U.S. Environmental Protection Agency. “EPA Reaches $100 Million Agreement in Olympic - Shell Pipeline Case.” News release 02-43, 11 Dec. 2002. epa.gov/archive/epapages/newsroom_archive/newsreleases/ea057914f8e03450852570cb0075e23a.html