Thermal Drone Inspection for Aramco Pipelines — A Field Playbook

Why thermal drones beat ground crews on KSA pipelines

Three numbers explain the shift. A ground crew covers 8–12 km of buried pipeline per day; a Matrice 30T or Matrice 400 with Zenmuse H30T covers 80–140 km per flight day [VERIFY-SME]. Thermal anomaly detection at altitude catches insulation faults the ground crew cannot see. And the BVLOS workflow lets a single operator cover a multi-region network from a regional GACA-approved base.

The catch is that the unit economics only work when the programme is monthly and integrated into the existing inspection register. One-off thermal flights are a science project.

Sensor selection — H30T, H20T or third-party

Three sensor classes dominate KSA work in 2026:

Sensor	Resolution	Best for
Zenmuse H30T	1280×1024 thermal	New deployments; standard 2026 baseline
Zenmuse H20T	640×512 thermal	Existing M300 fleets; cheaper retrofit
Third-party radiometric (FLIR Vue TZ20)	640×512 each lens	Specialist FLIR-required workflows

H30T is the default 2026 choice. The radiometric channel must be calibrated and the model card version logged for every sortie.

The GACA BVLOS chain

Aramco pipeline corridors are by definition beyond visual line-of-sight. The permit chain in 2026 typically requires:

1. A standing Class 1 GACA permit for the corridor.
2. A BVLOS application that names the operating organisation and the safety case.
3. Coordination with NCM for weather windows and with MoI for security clearance.
4. NOTAM issuance for each flight day.

Lead time end-to-end is 4–8 weeks for first authorisation, 5–10 working days for renewals. See the GACA drone permits guide and the dedicated BVLOS piece. Glossary anchor: GACA.

The three anomaly classes that matter

Most pipeline thermal programmes can ignore the noise and focus on three anomaly classes:

1. Leak signature — a localised cold or hot patch with a vapour plume signature. High urgency, immediate notification.
2. Hot spot — a sustained surface temperature above ambient + threshold (typically +15°C against the corridor mean) that suggests insulation breach or coating failure.
3. Insulation fault — a longitudinal pattern of warm sections separated by cold sections, characteristic of broken pipe insulation cladding.

Each class maps to a different priority in the pipeline inspection solution and to a different SAP-PM notification type [VERIFY-SME — confirm with operating organisation].

Anomaly thresholds and false positive control

Naive thresholds produce hundreds of false positives per flight km. Two engineering controls that earn their keep:

1. Adaptive baseline. The threshold for a hot-spot is not absolute; it is computed against the local 200-m moving average of the corridor temperature. This kills sun-exposure false positives.
2. Multi-frame persistence. An anomaly only fires if it is visible across at least three frames in flight (typical overlap 70%+).

Combined, these reduce false positives to roughly 0.3–0.8 per flight km on a typical Eastern Province corridor [VERIFY-SME].

Integration into SAP-PM and the corrosion register

The deliverable that wins the engineering team is not a thermal mosaic, it is an SAP-PM notification per anomaly. The recommended hand-off mirrors the Aramco EHS compliance guide:

1. Each anomaly produces a JSON record with anomaly_id, lat, lng, chainage_m, class, delta_t_k, confidence, clip_hash, flight_id, permit_id.
2. The middleware adapter calls SAP-PM BAPI_ALM_NOTIF_CREATE with the appropriate notification type for the operating organisation.
3. The clip vault stores the radiometric TIFF in WORM with daily SHA-256 signing.
4. The corrosion register joins the SAP record to its existing inspection cycles.

For deeper integration patterns see the AI analytics platform and API access.

Programme cycle — monthly, not ad-hoc

The cycle that delivers value:

1. Day 1: flight plan generated against last month’s anomaly list and any new permit changes.
2. Day 2–4: BVLOS flights executed across the assigned corridors.
3. Day 5: anomaly inference and review by the engineering analyst.
4. Day 6: SAP-PM notifications raised, prioritised, dispatched.
5. Day 7–28: ground verification on prioritised anomalies, closure cycle.

Monthly cadence balances detection latency (a leak that takes 3 weeks to find is too long) against operational cost.

Cost envelope

Indicative 2026 SAR costs for a monthly thermal programme:

Corridor length	SAR per month
50 km	35,000–55,000
200 km	95,000–160,000
800 km	280,000–450,000

Costs include flight, anomaly inference, SAP-PM hand-off, but exclude ground verification crews [VERIFY-SME]. See the drone mapping cost piece for the broader pricing context.

Common pipeline programme mistakes

1. Treating thermal as a one-off. The first flight always finds anomalies; the value is in tracking which ones grow.
2. No baseline. Without a corridor-mean baseline, every sun-exposed flange becomes an alert.
3. Skipping the DPO — pipeline footage often contains people; PDPL still applies.
4. No SAP-PM integration. Anomaly data that lives in a vendor portal is invisible to the engineering team.

Field deployment checklist

1. BVLOS permit live, with 14 days of headroom.
2. Radiometric calibration recorded and signed.
3. Anomaly thresholds tied to corridor mean baseline.
4. SAP-PM notification type confirmed with operating organisation.
5. Two-week shadow run at programme start.
6. Monthly cadence locked into the engineering calendar.

Next steps

If you are scoping a pipeline thermal programme, start with the pipeline inspection solution, the oil & gas drone inspection guide and the thermal inspection solution. Cross-reference the GACA BVLOS permits piece for the permit chain.

Book a thermal pipeline scoping session and we will produce a corridor-specific programme design within 15 working days.

React to this article

🔥...💡...🤔...👏...❤️...