API RP 1187: Getting Your Pipeline Geohazards on Solid Ground

May 1, 2025
Insights

Landslides don’t check your pipeline schedule before they move—and that’s exactly why API RP 1187 exists. Released in 2024, this recommended practice gives operators a shared playbook for managing geohazard risks. As Alex Baumgard, Principal Geotechnical Engineer at BGC Engineering, puts it: “It’s recommended—but it’s also a practice you’re probably already doing.” 

The RP was a collaborative effort, but a few names stand out. Mark Piazza [a Senior Policy Advisor at API] and Andy Duncan [Pipeline Integrity Engineering Manager at Enbridge] were key contributors and voices in developing RP 1187. In this article, we break down what RP 1187 is, who it’s for, why it matters, and how Cambio users [and non-users] can align with it—without the headaches.

What is API RP 1187, and Why Was It Created?

RP 1187 is a recommended practice [not a regulation] developed by the American Petroleum Institute. It provides a structured approach for managing landslide hazards on onshore welded steel pipelines. Think of it as a field-tested guide for identifying, assessing, and mitigating geohazard threats.

According to Alex, the RP “isn’t state-of-the-art—but it’s more advanced than standard practice,” and it reflects real-world workflows used by operators and consultants alike. Think of it as a toolkit of best practices that you can show your management or regulators to say, “Look, we’re following industry-recommended approaches here.” It can even serve as an audit reference – e.g. if someone asks “Are we doing what RP 1187 recommends?”, you should be able to pull up your program documents and say “Yes, and here’s how.”

The RP emerged as a response to growing awareness around terrain threats—particularly after several pipeline incidents tied to ground movement. And while the U.S. pipeline regulator [PHMSA] hasn’t mandated it, Alex suggests it’s already being referenced in audits and by Canadian regulators like the CER.

Who Should Pay Attention?

RP 1187 is written with pipeline operators in mind—especially those in hilly or unstable terrain. It’s specific to onshore steel pipelines, but Alex was clear: “There’s no magic wall when you cross into Canada. The concepts still apply.”

And if you’re operating elsewhere—South America, Southeast Asia, the Alps? The same geomorphic principles apply whether you’re dealing with mudslides in Colombia, permafrost heave in Alaska, or coastal bluffs in California, the framework gives you a common language and approach for managing those terrain challenges. You’ll just need to adapt the RP to your local regulatory context.

What’s Actually in It?

Alex described the RP as “about 150 pages, but the meat is in the appendices.” Here’s the core framework:

  • Screening: Start wide. Use geomorphic screening, LiDAR, IMU, and field observations to flag potential issues. Alex noted Cambio supports “line-wide screening for some groups… prioritizing hazards based on geomorphic processes.”
  • Assessment Tiers: RP 1187 promotes a three-tiered approach—from coarse screening to detailed site investigations [think boreholes, DEMs, instrumentation].
  • Risk Ranking: One standout is the “R-matrix” concept as an example of how risk ranking can be implemented —combining landslide characteristics with pipeline strain to rank threats. Alex showed how Cambio users can auto-calculate R-levels and customize them. “What you decide to do with those R-levels is up to you—but the framework helps guide response.”
  • Data Management: The RP outlines what to track—from site geometry to strain, instrumentation, and inspection records. Alex highlighted that Cambio captures “all the same information,” down to tool run metadata and inspection history.
  • Monitoring vs. Mitigation: The RP offers guidance on when to monitor and when to act. It also details instrumentation types and expected monitoring frequency. One area it misses? Alarming and forecasting. 

For Cambio Users: You’re Already Aligned

The good news? If you're using Cambio, you’re already on solid footing. As Alex Baumgard highlighted in his API RP 1187 presentation, “We’re hitting all of the boxes. That data’s already in Cambio.” In other words, the platform is built around the same workflows and data structures the RP recommends—because many of those practices were shaped by engineers like Alex who helped contribute to both the RP and Cambio.

Here’s how that plays out:

  • Hazard Inventories: Cambio’s geospatial hazard database supports all the core attributes the RP calls for—geometry, threat type, proximity, velocity, inspection notes, strain data, and more. Everything is GIS-integrated and traceable.
  • Screening & Assessment: Cambio supports line-wide screening using LiDAR, IMU, and geomorphic criteria—something Alex flagged as a key strength. Users can then escalate sites through the RP’s three-tiered assessment model, from desktop reviews to detailed geotechnical investigations.
  • Risk Ranking: The RP’s “R-matrix” concept or going with Probability of Failure (PoF)? It’s already baked in. Cambio users can calculate proximity and strain-based risk levels, customize the classification matrix, and track changes over time.
  • Monitoring & Instrumentation: All instruments—like inclinometers, piezometers, strain gauges—can be logged and tracked. Cambio handles installation dates, last readings, activity status, and alert thresholds, giving you a live view of what’s happening underground.
  • Action Tracking: This is where Cambio goes a step beyond the RP. Users can assign, track, and close out mitigation actions with full audit trails—something the RP recommends in spirit but doesn’t prescribe in detail.

Put simply: if your team is actively using Cambio, you’re not just RP 1187-ready—you’re RP 1187-practicing. And if your Executive or Regulator asks, “How do we stack up?”, you’ll be able to pull up your dashboard and show them. 

Not Using Cambio? Here’s What to Do

You don’t need Cambio to align with RP 1187—you just need a structured, documented program. Here’s your checklist:

  1. Inventory geohazards in a GIS or spreadsheet.
  2. Screen and prioritize threats using geomorphic data and ILI strain where available.
  3. Inspect regularly and log findings.
  4. Monitor with instruments where needed—and track the data.
  5. Mitigate when risk warrants it, and track actions.
  6. Review your program yearly and update as new threats emerge.

Alex’s advice? “You’re free to do anything—as long as you can demonstrate you’re doing it logically.”

Learn More

Final Thought

Alex summed it up best: “It’s recommended, not required. But if you’re managing geohazards, you should be thinking through this framework.”

It’s also worth noting the timing: with climate change causing more intense rainfall in many regions, slopes that were once stable might start moving. The industry is seeing more frequent heavy rain-induced slides and unprecedented flood events. So having a robust geohazard management program isn’t just a niche “nice-to-have” – it’s becoming a core part of pipeline safety management. Landslides might not be as predictable as metal loss, but with a proactive approach, we can avoid being caught off guard.

API RP 1187 is about getting ahead of Mother Nature’s curveballs. It pushes us to be proactive, data-driven, and systematic in addressing ground movement threats. Whether you’re deep into DEM modeling or just flagging slopes from a helicopter, RP 1187 gives you a solid foundation to manage risk—and keep your pipelines [and teams] out of trouble when the ground starts shifting.