1998 Esso Longford fire
1998 industrial disaster in Victoria, Australia
On 25 September 1998 a catastrophic fire occurred at the Esso natural gas plant in Longford, Victoria, Australia. A pressure vessel ruptured resulting in a serious jet fire, which escalated to a conflagration extending to a large part of the plant. Fires lasted two days before they were finally extinguished.
Two workers were killed and eight others injured. Natural gas supply to the state of Victoria was severely disrupted and was not fully restored until 14 October. Total estimated property costs amounted to US$443 million (US$987 million in 2021), while financial losses to the companies affected by the gas shortage were estimated at around A$1.3 billion.
The Victorian state government established the Longford Royal Commission to publicly investigate the causes of the accident.
Context
In 1998, the Longford gas plant was owned by a joint partnership between Esso and BHP. Esso was responsible for the operation of the plant. Esso was a wholly owned subsidiary of US-based company Exxon, which has since merged with Mobil, becoming ExxonMobil.
Built in 1969, the plant at Longford is the onshore receiving point for raw natural gas output from the Marlin, Barracouta and Snapper fields in the Bass Strait, as well as crude oil from further offshore oil platforms.
Begin with the source’s own compact description: “1998 Esso Longford fire” is 1998 industrial disaster in Victoria, Australia. The dossier treats that line as a proposition to test through Esso, Longford and fire, not as a finished interpretation.
Why this record matters
The phrase “1998 industrial disaster in Victoria, Australia” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jun 22, 2026. The linked authority identifier is Q5399936. The Library of Congress control number is sh2001003036. Authority coordinates are -38.224, 147.167. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1998, 2021 and 1969.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “1998 Esso Longford fire”, its source revision and the description used here.
- Expand the search: follow 1998 Esso Longford fire primary sources, 1998 Esso Longford fire archive and Esso research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “1998 Esso Longford fire”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “1998 Esso Longford fire” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.