What is an oil and gas regulatory incident?

A regulatory incident record describes an event reported or published within a regulator's program. The covered events, reporting fields, and review stages vary. Keep the source's event type instead of assigning every incident the same description.

New Mexico's New Mexico OCD · Forms and report purposes identifies C-141 as a release notification and corrective-action form. That is a concrete example of an incident-related record. It does not mean every state uses that form or that every record labeled an incident represents the same type of event.

An incident must not be automatically treated as a violation, enforcement action, or severity ranking.

Read the event date, report date, location, regulated entity, event type, and reported details. When quantities appear, preserve the units and labels used by the source. A revision may update an initial report rather than describe a second event.

The New Mexico OCD · Digital C-141 and incident statuses explains digital C-141 submissions and incident statuses. A submission, review step, corrective-action update, and closure-related status can belong to the same incident history. Treat them as related stages when the source establishes that relationship.

Begin with the incident identifier and confirm the location or facility. Read the initial report, then follow the associated updates and attachments. Identify which facts were reported by a party and which conclusions the regulator actually recorded.

Keep the event date separate from a later corrective-action date. When a summary is incomplete, the linked documents may explain the status. If the source does not establish an outcome, retain that gap instead of substituting an assumed cleanup result.

An incident describes an event in a reporting program. A violation records a regulator's finding under a requirement. An enforcement action records a regulatory step addressing a compliance matter. One event can have related records, but those relationships need evidence.

Do not automatically turn an incident count into a violation count or a severity ranking. Compare the source classifications and documented impacts rather than creating a uniform score across unlike reporting systems.

An incident entry alone does not establish fault, a final penalty, current site conditions, or the total effect on a property. A closure-related status should be interpreted within the process and scope described by the regulator.

For a property review, use the incident history to identify documents and questions that need attention. Match those questions to the actual site and period. An event associated with one location should not be attributed to an entire operator portfolio without supporting evidence.

• Confirm the incident identifier and location.
• Separate event, report, and update dates.
• Follow linked corrective-action and review records.
• Do not infer a violation, penalty, or severity score from an incident label.