What is an oil and gas regulatory violation?

A regulatory violation record identifies noncompliance recorded under a regulator's program. It should be presented using the source's requirement, description, identifiers, and status rather than a severity label invented by the researcher.

The Texas RRC · Inspection and violation data dictionary distinguishes violation data from inspection data. This matters because a review can produce findings that require separate interpretation. Count and describe the source records actually present; do not infer a violation from an inspection, incident, or unexplained production change.

Wildcatters does not infer violations or assign an unsupported severity score.

Identify the regulated entity, the relevant operator, the cited requirement, the finding date, and the source's status. Read any linked notice for the conduct described and the action requested. Keep a later update date separate from the original finding date.

If the database uses a code, consult its definition before translating it into plain language. A short code may summarize only one part of the matter. Preserve the original identifier so another researcher can find the same record and check subsequent updates.

Research the record forward through any source-linked correction, follow-up inspection, or enforcement matter. A corrected status and a final enforcement outcome answer different questions. Do not assume that one necessarily establishes the other.

The Texas RRC · Oil and gas compliance and enforcement describes the Texas compliance and enforcement program. Use the relevant jurisdiction's published process when interpreting notices and later actions. If the source does not supply a relationship between two records, describe it as unconfirmed instead of joining them by a similar operator name.

A historical violation remains a historical record even when a source later reports correction. Conversely, a retrieved old status may not describe the most recent state of the matter. Report the finding and the latest verified source status with their respective dates.

When comparing properties, examine the nature and scope of the cited requirements. A raw count can mix unrelated requirements and record types. It should not become an unsupported compliance score or a conclusion about an operator's entire portfolio.

The existence of a record does not by itself establish a final penalty, an adjudicated legal outcome, environmental damage, or current operational status. Those claims need their own supporting documents.

A research result should distinguish the regulator's recorded finding from your interpretation. Where the matter is pending, unclear, or missing a linked disposition, keep that uncertainty visible. The absence of retrieved violations is also limited by the dataset and query used.

• Read the cited requirement and finding.
• Confirm the entity and relevant dates.
• Check correction and enforcement status separately.
• Avoid inferred penalties, severity scores, and unsupported record joins.