What records should operators keep for an LDAR inspection?

Learn exactly which LDAR inspection records operators must keep, from leak logs to repair timelines and no-leak results.

October 29, 2026

Operators must keep a defined set of LDAR inspection records that document every stage of the leak detection and repair process, from initial survey results to confirmed repairs and follow-up checks. The exact requirements vary by jurisdiction and applicable regulation, but most frameworks, including those aligned with EU methane regulation standards, require records to be detailed, traceable, and retained for a minimum number of years. The sections below walk through the most common questions operators have about LDAR documentation requirements.

How long do operators need to retain LDAR inspection records?

Operators are generally required to retain LDAR inspection records for a minimum of five years, though some regulatory frameworks mandate longer retention periods of up to ten years. The retention period typically begins from the date the record was created, not the date of the inspection itself. Operators subject to the EU Methane Regulation should verify the specific retention requirements in their national implementing rules, as member states may apply stricter timelines than the baseline.

Keeping records well beyond the minimum required period is considered good practice, particularly for operators managing aging infrastructure. Historical inspection data helps demonstrate a consistent compliance record and can support asset management decisions when regulators request trend analysis. If your organization is transitioning to a new data management system, make sure legacy records are migrated and remain accessible, not just archived in formats that may become unreadable over time.

What information must an LDAR leak detection log contain?

An LDAR leak detection log must contain the date and location of the inspection, the method and equipment used, the identity of the inspector or survey operator, the components inspected, and the results of each measurement. For airborne or remote sensing surveys, the log should also record the survey altitude, speed, atmospheric conditions, and instrument calibration status at the time of the inspection.

Regulators reviewing LDAR documentation requirements expect records to be specific enough to reconstruct the survey conditions independently. This means vague entries like “no issues found” are insufficient. Each component or pipeline segment should have a corresponding measurement value or a clear notation explaining why a reading was not obtained. For surveys conducted under the EU Methane Regulation Type 2 requirements for underground equipment, sensitivity thresholds must also be documented to demonstrate that the detection method was capable of identifying leaks at or below the regulatory limit.

A well-structured leak detection log typically includes:

A unique identifier for each inspected component or segment
GPS coordinates or pipeline chainage reference
Date, time, and duration of the inspection
Detection method and instrument model
Calibration records and detection sensitivity
Measurement results or confirmed absence of leakage
Name and qualification of the inspector
Weather and environmental conditions at the time of the survey

What repair and follow-up records are required after a leak is found?

When a leak is identified, operators must document the date the leak was discovered, the leak location and component type, the estimated emission rate where applicable, the repair action taken, the date the repair was completed, and the result of any post-repair verification inspection. These pipeline inspection records form the evidence trail that demonstrates a leak was addressed within the regulatory timeframe.

Most frameworks distinguish between leaks that can be repaired immediately and those that require a planned repair window due to operational constraints. In both cases, the record must reflect the reason for any delay and confirm that interim mitigation measures were applied where required. After the repair is completed, a follow-up measurement must be conducted and its result logged to confirm that the leak has been resolved. If the first repair attempt is unsuccessful, each subsequent attempt must be recorded separately.

For operators working under the EU Methane Regulation, repair timelines are tied to the severity of the leak. Keeping accurate timestamps at every stage, from detection to verified repair, is essential to demonstrating compliance and avoiding penalties during audits.

Do operators need to keep records of equipment that was inspected but showed no leaks?

Yes, operators must keep records of all inspected equipment, including components and pipeline segments where no leaks were detected. A complete LDAR compliance record covers the entire scope of the survey, not just the findings. Regulators use no-leak records to verify that the required inspection frequency was met and that all components within the regulatory scope were covered.

Omitting no-leak results from the documentation creates gaps that regulators may interpret as uninspected components rather than clean results. This can trigger additional scrutiny or require operators to repeat portions of the survey at their own cost. In practice, a thorough pipeline inspection record that documents every inspected segment, whether a leak was found or not, is far easier to defend during a compliance review than a record that only captures positive findings.

How should LDAR records be stored and submitted to regulators?

LDAR records should be stored in a secure, structured format that allows for efficient retrieval and audit. Most regulators now accept or require digital submissions, and many operators use web-based GIS platforms or environmental data management systems that link inspection results directly to asset maps. Records must be protected against unauthorized modification, and any changes to existing entries should be logged with a timestamp and the identity of the person who made the change.

Submission requirements vary by country and regulatory body. In some jurisdictions, operators must submit annual LDAR compliance reports that summarize inspection activity, leak findings, and repair outcomes. In others, records are retained by the operator and made available on request during inspections or audits. Regardless of the submission model, the underlying records must be complete and consistent with what was reported.

Key considerations for storing and submitting LDAR documentation include:

Use a system that supports geospatial data so results can be mapped to specific assets
Ensure records are exportable in standard formats for regulator submissions
Maintain a clear audit trail for any edits or corrections to existing records
Back up records regularly and store copies in at least one off-site or cloud location
Confirm submission deadlines and preferred file formats with your national regulator in advance

How ADLARES supports your LDAR documentation and compliance

We provide end-to-end airborne leak detection services that generate the structured, audit-ready data operators need to meet their LDAR documentation requirements. Our CHARM® technology, the world’s only DVGW-approved gas remote detection system, delivers high-sensitivity measurements at survey speeds of up to 180 km/h, covering large pipeline networks efficiently while capturing every data point regulators expect to see in a compliant record.

Here is what working with us looks like in practice:

Complete inspection logs: Every survey produces georeferenced measurement data for all inspected segments, including both positive findings and no-leak results, so your records cover the full regulatory scope.
Regulator-ready output: Survey results are delivered through a secure Web GIS platform accessible on desktop and mobile, making it straightforward to retrieve, review, and export records for submission or audit.
EU Methane Regulation compliance: Our CHARM® system meets the sensitivity thresholds required for Type 2 inspections of underground equipment, and our documentation reflects the calibration and detection parameters regulators need to see.
Experienced team: Our specialists have surveyed over 250,000 km of gas pipelines across Europe and understand the documentation standards applied by grid operators and national regulators in different jurisdictions.

If you want to make sure your next inspection produces records that hold up to regulatory scrutiny, get in touch with our team to discuss your pipeline network and compliance timeline.

This content was generated with the help of AI and it may contain mistakes