FLAGS
natural gas pipeline in the North Sea
The FLAGS (Far North Liquids and Associated Gas System) pipeline is a natural gas pipeline in the UK sector of the North Sea which, together with its associated pipelines, is used to transport gas and associated liquids from oil and gas fields in the northern North Sea to the St. Fergus gas terminal.
Pipelines
The FLAGS system gas pipelines are:
Installations
FLAGS provides the gas export route for the following installations.
Cormorant A
North Cormorant
North West Hutton
Ninian Central
Ninian North & South
Brent 'A', 'B', 'C' and 'D'
Tern
Magnus
Thistle
Murchison
Statfjord
Heather
Gjøa
Gas exported from West of Shetland oil fields (Foinaven, Schiehallion/Loyal and Clair)
Knarr
Infrastructure
The FLAGS pipeline is a 36-inch (910 mm) steel pipe to API 5L, X60 specification and is 450.6 kilometres (280.0 mi) long. It starts at Brent 'A' and terminates at St. Fergus near Peterhead in Scotland. Pipe laying was completed in April 1978 and finally commissioned in May 1982. The pipeline was laid by SEMAC 1.
At Brent A, the pipeline is connected with the Northern Leg and Western Leg transmission systems, carrying gas from a number of nearby fields.
The 20-inch Northern Leg Gas Pipeline (NLGP) runs for 80 km from Magnus to Brent A with spurs to Thistle A, Murchison and Statfjord B. It originally served as the gas export route for these installations and delivered gas to Brent A for onward transmission to St Fergus via FLAGS. As some of these installation have become gas deficient it has served as their gas supply route.
This brief starts where responsible research should: with the source description of “FLAGS” as natural gas pipeline in the North Sea. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as natural gas pipeline in the North Sea. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The strongest evidence will usually combine a dated visual record with documents produced by the authority responsible for the place. The source revision retrieved here is dated Sep 6, 2026. The linked authority identifier is Q5426508. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1978 and 1982.
Architectural summaries often privilege surviving fabric and can understate demolished phases, contested use or displaced communities. 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
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “FLAGS”, its source revision and the description used here.
- Expand the search: follow FLAGS primary sources, FLAGS archive and FLAGS 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 “FLAGS”?
- What physical evidence or contemporary plan supports the description?
- Which authority defined the place, boundary or structure at the relevant date?
Search terms from this dossier
This entry incorporates text from “FLAGS” 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.