Production and Drilling Data

New Mexico Well Production Data 2026: 3 Reconciliation Layers

How to reconcile New Mexico well identity, production reporting, and regulatory status without treating one portal as a complete well file.

Landman Business Editorial TeamSources: 10Verified 2026-08-10Reviewed 2026-08-108 minute read
Evidence-led research card for New Mexico Well Production Data 2026: 3 Reconciliation Layers

3 reconciliation layers

API identity kept intact

Verified August 10, 2026

A New Mexico well record may appear in several public contexts, each with its own update schedule. The safest reconciliation begins with the API number and keeps the source label attached to each observation.

New Mexico Well Production Data 2026: Measured findings from the cited authority

New Mexico OCD’s FY 2024 annual report records 39,640 oil-and-gas inspections and 104 abandoned wells plugged during the fiscal year, exceeding the legislative goal of 50 wells. Source: New Mexico EMNRD FY 2024 annual report. These are statewide regulatory findings, not production totals for an individual API; the OCD production report must supply the well-specific oil, gas, water, unit, and month values.

Fields worth preserving

The following fields keep the New Mexico Well Production Data 2026: 3 Reconciliation Layers question narrow enough to audit without hiding the original publisher’s terminology.

Field What to retain
API number state and county identifier
Well name published name and operator label
Production period month and commodity
Status event permit, completion, shut-in, or other label
Source timestamp retrieval or publication context

Reading the evidence

Data sources and methodology

Use the OCD identifier and image or query record as the anchor. Add production observations by period and commodity, then place status events on a separate timeline. Do not collapse an unavailable observation into a zero without a publisher rule supporting that treatment. New Mexico Well Production Data 2026: 3 Reconciliation Layers uses a separate evidence boundary.

Do not replace a missing observation with a guessed value in New Mexico Well Production Data 2026: 3 Reconciliation Layers. For new-mexico-well-production-data-2026, retain the publisher label, identifier, date, and unit beside every normalized value. For new-mexico-well-production-data-2026, conflicting observations remain side by side with their definitions and dates.

Topic-specific interpretation notes

API number deserves its own review note in New Mexico Well Production Data 2026: 3 Reconciliation Layers: retain state and county identifier, state why the field matters, and identify the condition that would make the observation unreliable.

Well name deserves its own review note in New Mexico Well Production Data 2026: 3 Reconciliation Layers: retain published name and operator label, state why the field matters, and identify the condition that would make the observation unreliable.

Production period deserves its own review note in New Mexico Well Production Data 2026: 3 Reconciliation Layers: retain month and commodity, state why the field matters, and identify the condition that would make the observation unreliable.

Status event deserves its own review note in New Mexico Well Production Data 2026: 3 Reconciliation Layers: retain permit, completion, shut-in, or other label, state why the field matters, and identify the condition that would make the observation unreliable.

Source timestamp deserves its own review note in New Mexico Well Production Data 2026: 3 Reconciliation Layers: retain retrieval or publication context, state why the field matters, and identify the condition that would make the observation unreliable.

Frequently asked questions

Do the API number and county match across systems?

The Oil Conservation Division provides regulatory and production-related records for New Mexico operations.

Does the status date precede or follow the production period?

A well’s status label may reflect a regulatory event rather than current field activity.

Is a missing month a zero, a delay, or an unavailable record?

Production rows should be compared only after the reporting month, commodity, and unit are aligned.

Evidence packet review before handoff

Before this record set is used in a land workflow, review the API number, county, operator label, commodity, production month, status date, unit, and retrieval path. Preserve each value exactly as the publisher displays it before adding a normalized copy. The normalized field may help with matching, but it should never overwrite the source label or conceal a conflict.

Open each cited source again from the saved locator. Confirm that the identifier, jurisdiction, date meaning, geography, and unit apply to the question being reviewed. Record whether the link opens a specific record, a search interface, or only a general program page. A general entry point can guide further research, but it is not evidence that a particular tract, lease, well, owner, order, or transaction was found.

Keep missing results visible. Note the query used, the coverage available through that interface, the date searched, and the next authorized source or reviewer. Do not convert a blank value into zero or infer an event between two published observations. If two systems disagree, retain both source values and describe the difference without deciding which one controls.

The handoff should separate source observations, administrative normalization, unresolved exceptions, and reviewer decisions. That structure lets another researcher reproduce the search and lets the authorized land, legal, regulatory, accounting, engineering, or commercial reviewer resolve questions within their role. It also prevents a workflow note from being mistaken for a title conclusion, operational determination, or assurance about source completeness.

Limits of the record

The FY 2024 inspection and plugging counts measure statewide regulatory activity. They do not identify a named well’s production, ownership, mechanical condition, lease terms, or future output.

Reference register

These are the distinct public record layers used to frame New Mexico Well Production Data 2026: 3 Reconciliation Layers; each link should be checked for its own definition and update schedule.

  • New Mexico OCD: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • OCD Imaging: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • OCD Well Data: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • EIA State Data: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • USGS New Mexico: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • BLM New Mexico: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • EPA UIC: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • FracFocus: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • NMOSE Data: public record entry point; check the source's definitions, coverage, and update schedule before use.
  • New Mexico GIS: public record entry point; check the source's definitions, coverage, and update schedule before use.

Additional reading notes

Observation 1. The Oil Conservation Division provides regulatory and production-related records for New Mexico operations.

Observation 2. A well’s status label may reflect a regulatory event rather than current field activity.

Observation 3. Production rows should be compared only after the reporting month, commodity, and unit are aligned.

Conclusion

Keep the API identity separate from statewide inspection statistics and reconcile the monthly production row; Book a free consultation when a New Mexico well file needs senior review.

land researchpublic dataproduction and drilling data