How Satellite Monitoring Addresses PHMSA Geohazard Requirements
PHMSA expects operators to identify earth movement hazards, evaluate changing conditions, and document what was reviewed, what was found, and what action followed. Satellite-based movement monitoring gives integrity teams a practical way to do that at corridor scale.
For most operators, the hard part of geohazard compliance is not understanding that landslides, subsidence, washout, and slope instability matter. The hard part is maintaining a repeatable program that can detect movement before strain damage, expose change across thousands of miles of right-of-way, and stand up to review after an incident or audit. That is where satellite monitoring has become relevant. Used correctly, it is not a science experiment and it is not a replacement for engineering judgment. It is an operating layer that helps integrity teams see movement where they do not have instruments on the ground.
This matters because the PHMSA Mega Rule raised the bar on geohazard analysis under 49 CFR Part 192. Operators now need a more disciplined view of threats that can affect line segments, especially where earth movement can change loading conditions over time. Satellite monitoring, including InSAR-based movement measurement, fits that need because it can show whether a corridor is stable, whether movement rates are increasing, and where follow-up should be concentrated. For operators building a modern InSAR integrity management workflow, the value is straightforward: better detection, better records, and better prioritization.
What the PHMSA Mega Rule changed for geohazard analysis
The Mega Rule did not create geohazards as a new integrity concern. It made the expectation more explicit that operators must identify and evaluate threats from changing physical conditions, including earth movement, and tie those findings into integrity assessments, remediation, preventive actions, and records. In practice, that means geohazard review cannot be a static desktop study that is updated only when a project team remembers it exists.
Under the transmission pipeline safety framework in 49 CFR 192, geohazards show up across several operator obligations:
- Threat identification and risk evaluation for integrity management segments.
- Patrols, leakage surveys, and other surveillance activities intended to identify conditions that could affect safe operation.
- Change management for route conditions such as slope movement, scour, subsidence, erosion, or construction impacts near the line.
- Records that demonstrate what conditions were reviewed and how anomalies were addressed.
For engineering teams, the operational translation is simple. You need a defensible method to answer four questions: where could earth movement affect the pipe, whether movement is actually occurring, whether the condition is changing, and whether the response matched the level of risk. That is the real compliance burden behind the rule text.
Why traditional geohazard programs still leave blind spots
Most operators already use a mix of field observations, aerial patrols, geotechnical review, strain-based design inputs, and site-specific instrumentation. Those methods remain necessary. The problem is coverage. Ground sensors are excellent where you already know the problem location, but they are expensive to install and maintain across long corridors. Aerial surveys can reveal washouts, exposed pipe, or obvious slope distress, but they do not directly measure slow ground movement between flights. Foot patrols and visual ROW checks are essential for confirmation, yet they are intermittent and resource-intensive.
That leaves the classic geohazard gap: slow or distributed movement can progress between inspections, outside instrumented sites, and below the threshold of visible surface damage. By the time the condition becomes obvious in the field, the loading history on the pipe may already be significant. That is why operators are increasingly evaluating pipeline displacement monitoring software as part of the integrity stack. The objective is not to replace field work. It is to give field work a better target list.
How InSAR directly addresses earth movement detection
InSAR is useful to pipeline operators because it measures surface movement over time across broad areas without installing equipment on the ROW. In integrity terms, that means repeated observation of whether the ground over and around a segment is stable, creeping, settling, or accelerating. The most important output is not a radar product. It is a movement history you can review by segment, crossing, slope, valve site, or geohazard polygon.
That directly supports PHMSA expectations in three ways:
- Detection: It highlights segments where earth movement is occurring even when no recent field report exists.
- Trend monitoring: It shows whether movement is steady, seasonal, or worsening, which matters for response timing and prioritization.
- Documentation: It creates a record of recurring review, measured change, and engineering follow-up.
For a geohazard engineer, the value is corridor-wide screening. Instead of asking only whether a known landslide is still active, the team can ask where else movement is emerging along the system. That changes the program from site-by-site reaction to network-level surveillance.
There are practical limits. Tree cover, steep terrain geometry, construction disturbance, and other local conditions can reduce data quality. Satellite monitoring also measures ground behavior, not pipe strain directly. A finding still needs engineering interpretation in the context of pipe properties, depth of cover, geology, hydrology, and recent field conditions. But none of those limitations undermine its role. They define where satellite monitoring belongs in the workflow: early detection, trend tracking, and targeted escalation.
Where satellite monitoring fits in an integrity workflow
A useful program does not send raw maps to integrity staff and ask them to become remote sensing specialists. It converts movement observations into engineering actions. That means organizing results around line segments and known hazard features, flagging movement rate thresholds, comparing current conditions to prior review periods, and attaching the output to inspection and remediation records.
For example, a modern review cycle can look like this: the system screens the full corridor every update period, highlights segments with measurable movement, ranks them by change from baseline, and produces a short list for geohazard engineering review. The engineer then decides whether the condition needs desktop investigation, aerial imagery review, site visit, strain analysis, instrument deployment, or immediate response. That is how satellite monitoring becomes actionable PHMSA pipeline geohazard monitoring, not just another dashboard.
| Method | Best Use | Strengths | Limits |
|---|---|---|---|
| Ground sensors | Known high-risk sites, strain confirmation, active remediation areas | High precision at a point, continuous data, direct support for site-specific engineering | Sparse coverage, high install and maintenance cost, poor fit for full-corridor screening |
| Aerial survey | Surface condition review, washouts, exposed pipe, access impacts, drainage change | Fast visual review across long mileage, useful post-storm and post-construction | Does not directly measure slow movement, dependent on flight cadence and visibility |
| Satellite InSAR | Recurring corridor-scale movement screening and trend tracking | Broad coverage, repeatable historical baseline, identifies movement between patrol cycles | Indirect measure of geohazard impact, variable data quality by terrain and surface conditions, still needs field validation where risk is elevated |
How to think about PHMSA's 2025 remote sensing ROW patrol rulemaking
Operators should treat PHMSA's 2025 remote sensing rulemaking as directional, not settled law. In July 2025, PHMSA issued a direct final rule addressing remote sensing use in right-of-way patrols. In October 2025, that direct final rule was withdrawn after adverse comment. That sequence matters. It means the specific regulatory text did not become final through that action, but it also shows that PHMSA is actively engaging the question of how remote sensing should fit into patrol and surveillance obligations.
The practical takeaway is not to wait for perfect regulatory certainty before modernizing surveillance methods. Agencies do not spend time proposing remote sensing pathways unless they see an operational role for them. Even with the withdrawal, the direction is clear: documented, technology-enabled observation of the ROW is moving closer to mainstream regulatory acceptance, especially where operators can show that the method improves detection, repeatability, and records.
That is why the right framing for satellite monitoring is not "PHMSA already requires this" and not "PHMSA has fully approved this for every patrol obligation." The accurate framing is that satellite movement monitoring aligns with where the regulatory conversation is going and strengthens the operator's ability to show a systematic geohazard program today.
What operators should do now
Operators do not need to rewrite the entire integrity program to start getting value. They need to build a disciplined use case, define decision points, and make sure the output lands in the records system rather than in a disconnected pilot folder.
1. Start with corridors where earth movement is already a known threat
Focus first on mountainous terrain, subsidence-prone areas, river crossings, slope instability zones, and segments with prior geohazard repairs or active watch lists. These are the places where satellite movement monitoring is easiest to justify and easiest to compare against field history.
2. Define engineering thresholds before you deploy
Do not start with a generic "alert on movement" rule. Set segment review thresholds tied to your threat model, asset class, and response process. A useful program distinguishes between minor background movement, watch conditions, and movement that triggers field confirmation or strain review.
3. Connect satellite findings to existing patrol and integrity workflows
The right model is layered surveillance. Satellite monitoring identifies where conditions may be changing. Aerial review, site visits, and sensors confirm mechanism and consequence. Integrity engineering then decides whether the condition affects immediate safety, remediation planning, or ongoing observation. That sequence is far more defensible than treating each method as a standalone compliance box.
4. Build report-ready records now
PHMSA reviews are easier when the program can show a recurring review cadence, segment-level findings, thresholds used, exceptions handled, and actions taken. If your current geohazard files rely on slide decks and screenshots, fix that first. The best pipeline displacement monitoring software should produce segment summaries, movement histories, maps, and disposition notes that can be dropped directly into integrity files.
5. Use satellite monitoring to prioritize field dollars, not replace them
Field resources are limited. Satellite screening helps put them where the risk is moving, where the movement rate is changing, or where a known hazard zone has reactivated. That improves both compliance posture and operating efficiency.
What a PHMSA-ready monitoring program looks like
A strong program is not built around a single dataset. It is built around traceability. For each review cycle, the operator should be able to show the segments examined, the movement observed, the thresholds applied, the engineering interpretation, and the resulting action. If a regulator or internal reviewer asks why one slope received a site visit and another stayed on watch status, the answer should be in the record.
Satellite monitoring improves that traceability because it creates consistent, repeatable review intervals across the corridor. Instead of relying only on scattered field narratives, the operator can show measured change over time and demonstrate that the geohazard program is actively looking for conditions that may affect pipeline safety. That is the real compliance value.
For integrity teams, the strategic point is this: geohazard management is moving toward more measurable, more frequent, and more documented surveillance. Satellite movement monitoring supports that direction now. It gives operators a practical method to identify changing earth movement conditions, backstop patrol programs, and target field inspections where they matter most. In that sense, it is not just a better view of the corridor. It is a better operating model for geohazard risk.
See how GroundPulse generates PHMSA-ready reports
GroundPulse turns recurring satellite movement review into segment-level findings, exception tracking, and regulator-ready reporting for pipeline integrity teams.
See how GroundPulse generates PHMSA-ready reports