Landslides are present in every state of the USA and every province in Canada, and the extensive transmission, distribution, and gathering pipeline network is vulnerable to impacts from landslides, including pipeline rupture. Based on PHMSA statistics, landslides are one of the most expensive causes of pipeline rupture and result in more onshore pipeline ruptures than all other natural force incidents combined. For these reasons, considerable focus has been put on managing landslide hazards, such as PHMSA advisories ADB-2019-02 and ADB-2022-01, and the recently released API RP 1187. The traditional framework to address landslide hazards, as summarized in API RP 1187, starts with a system-wide desktop screening of geohazards (Level 1) and ends with site-specific detailed investigations (Level 3).
To enhance the desktop Level 1 Assessment process, Geosyntec has partnered with several North American pipeline operators to develop three novel methods to produce landslide susceptibility maps and inform decision-makers about the exposure to this geohazard. These landslide susceptibility methods not only map existing landslide hazards as is traditionally performed at Level 1 as described in API RP 1187, but they also predict areas that may be more likely to experience future landslide activity in response to forcing events, such as significant precipitation (e.g., rainfall or snowmelt) or topographic change (such as from naturally occurring erosion or construction). These methods use various combinations of high-resolution LiDAR, soils, and geologic mapping produced by public agencies and subject matter expert (SME) input. This paper discusses these three methods, which combined to date, have been implemented along more than 18,000 miles of pipelines in the United States and Canada. Additionally, this paper discusses how the resultant landslide susceptibility maps are and can be used to design or refine pipeline management practices, such as pipeline integrity assessment, budgeting, risk modeling, and construction planning.
Available after the event



