Arkansas Well Completion Record Lineage Study 2026

Arkansas Well Completion Record Lineage Study 2026: Research question

How should a land team connect an Arkansas completion filing to the correct permit, well, operator, location, producing interval, test evidence, and later Commission status?

Executive finding

A completion record describes reported construction and completion facts, while a permit, test, Commission order, and current well-data row serve different functions. The strongest packet keys them by full API and permit identifiers and preserves the event date attached to each artifact.

Arkansas source roles

The Arkansas Oil and Gas Commission provides separate routes for filings, rules, orders, and public well data. Those routes answer different questions. A permit documents authorization before drilling. A completion filing reports construction and completion information after the work described by the filer. The public well-data row is a current agency-system observation. An order may add field, spacing, pooling, or other context when the record connects it to the well. The research packet should keep those roles visible instead of presenting the newest screen as a complete history.

The method begins with a permit candidate located through the Commission records. It then searches for the corresponding completion artifact using the complete API number, permit number, well name and number, operator, county, and legal location. A match is stronger when several independent fields agree. Similar well names or the same operator are discovery clues, not sufficient identity evidence.

Each saved observation retains the source title, Commission route, access date, document date, and field labels. Current status is recorded with the date it was observed. If an image or attachment cannot be located, the packet names the missing item and the searches performed rather than reconstructing its contents from a later summary.

Dates describe different events

Permit issuance, drilling, completion, test, filing, order, and current-status observation can all have different dates. Store the event label with the date exactly as the source uses it. A filing date should not be substituted for the reported completion date. The access date belongs to the researcher’s observation, not to the well event.

Chronology is useful because it exposes impossible or unexplained sequences. A completion artifact that appears to predate its linked permit may reflect a mistaken join, a corrected record, or a date-label misunderstanding. The research step is to preserve the conflict and reopen the source. It is not to reorder the dates until the sequence looks plausible.

Negative results and current status

Public systems can require alternate searches and may update after the initial review. Document the interface, query terms, filters, and access time for a negative result. A failed search for a completion image does not prove that the operator failed to file one. It proves only that the documented search did not locate the artifact.

Current well status also needs restraint. A later status can establish what the public system displayed on the checked date. It does not by itself explain the intervening filings or orders. When the chronology jumps from completion to a later status, list the missing transition evidence as an exception. That gives the next researcher a specific target instead of a narrative assembled from assumptions.

Start with permit-to-completion continuity

The completion review begins with the permitted well identity: API number, permit number, well name and number, operator, county, and legal location. Compare those fields to the completion filing before reviewing formation or test details. If the operator or well name differs, record the variance rather than normalizing it away. A later operator display does not automatically explain who submitted the completion record.

Location evidence deserves field-level comparison

Arkansas well records may combine section-township-range, county, and mapped coordinates. Those representations are not interchangeable. Preserve the legal-location text as published and store latitude and longitude separately with their source and datum when stated. A map point can corroborate a candidate, but it cannot correct a legal description. Any disagreement routes to the document or qualified reviewer responsible for location interpretation.

Completion intervals and formation labels

Capture reported producing formation, perforated or completed interval, total depth, and completion date using the source’s labels. Formation names can be abbreviated or grouped differently across forms and databases. Maintain the original string and add a controlled comparison value only when the project defines the rule. Never infer acreage, ownership, or productive rights from an interval match.

Tests are observations, not permanent conditions

A test result belongs to a stated test type, date, duration, unit, and document. It should not be presented as current production or guaranteed capacity. If the public well row shows a different status later, the completion test remains a historical observation. The packet links the artifacts chronologically and avoids using a test value to explain a later status unless an official record makes that connection.

Commission orders and exceptions

Orders may supply field, spacing, pooling, or other context, but they should enter the packet only when an identifier or explicit reference connects them to the well or decision question. Party-name similarity and geographic proximity are discovery clues. Record the order number, docket or cause reference, date, page, and exact connection. If the link is inferential, label it as such and identify what would confirm it.

Scenario: permit location and completion map differ

Suppose the permit and completion form share an API number but the mapped coordinate appears outside the expected quarter section. Confirm transcription, coordinate labels, and access date; then inspect amendments, survey material, and the document image. Do not move the point or rewrite the legal call. The exception packet shows both representations and asks whether the difference reflects mapping precision, a corrected location, or a distinct record.

Completion-packet QA

A reviewer reopens the permit and completion artifacts, checks full identifiers, and verifies county, legal location, operator, dates, formation, intervals, and test units. They confirm that every current status is labeled with its observation date and that every order link states its evidence basis. They also reproduce any negative search using the recorded interface, query, filters, and time range.

Reconstructing a reviewable completion packet

The packet should open with a one-page chronology whose rows point to the underlying artifacts. The permit row identifies the authorization source and permitted location. The completion row identifies the reported completion date, construction details, interval labels, and any test reported on the filing. Later rows cover linked Commission orders and the current well-data observation. This arrangement lets the reviewer see a missing step without reading a blended narrative.

Supporting tables should stay narrow. One table compares identity fields across the permit, completion filing, and current well row. Another compares location representations and records the source of each coordinate or legal call. A third lists completion intervals and tests with their units and dates. Keeping those questions separate prevents a location discrepancy from being hidden inside a broad "matched" status.

The packet also needs a decision column. A clean identity match may be accepted for administrative indexing while a formation-label variance remains open for technical review. A location conflict may stop both decisions. State which output is blocked and why. This is more useful than assigning one overall confidence score to a file that contains several different research questions.

Example of an incomplete chain

Suppose the permit and completion filing share the full API number, permit number, county, and well name, but the operator differs and the public well row shows the completion operator. That evidence supports the well match. It does not explain the operator change between permit and completion. The researcher should keep both operator observations, search the Commission routes for an intervening filing, and hand off a named gap if none is located.

Now suppose the completion interval also uses a formation label not found on the permit. That difference is not proof of an error because the documents serve different stages of the well history. Preserve the terms and route any interpretation question to the qualified reviewer. The administrative packet can remain useful without pretending that every difference needs to be resolved by the researcher.

Study boundary

This review did not sample Arkansas wells, measure filing accuracy, or assess a particular completion’s technical or legal sufficiency. Public systems can omit images, require alternate searches, or update current values after access. The method supports a traceable land or regulatory research handoff; it does not establish title, spacing rights, compliance, physical condition, reserves, production accuracy, or operating authority.

Conclusion

The Arkansas packet succeeds when a reviewer can reopen the permit, completion filing, order, test evidence, and current well observation without losing their separate roles. Complete identifiers and location comparisons establish the proposed well link. The chronology then shows what changed, what is merely reported, and which transition evidence is missing. That structure supports an administrative decision while leaving technical and legal judgments with the responsible reviewer.

Sources

• Arkansas Oil and Gas Commission - Arkansas Department of Energy and Environment. Official Commission entry point. Checked October 2, 2026.
• Online Forms - Arkansas Oil and Gas Commission. Official filing and forms entry point. Checked October 2, 2026.
• Rules and Regulations - Arkansas Oil and Gas Commission. Official Commission rules directory. Checked October 2, 2026.
• Commission Orders - Arkansas Oil and Gas Commission. Official order-research route. Checked October 2, 2026.
• Well Data System - Arkansas Oil and Gas Commission. Official public well-data entry point. Checked October 2, 2026.
• Oil and Gas Data - U.S. Energy Information Administration. Official federal petroleum-data directory used to distinguish statistical series from filing records. Checked October 2, 2026.
• Energy Data - U.S. Geological Survey. Official federal energy-data entry point used for source-role comparison. Checked October 2, 2026.
• Data Center - Bureau of Ocean Energy Management. Official offshore mapping and data entry point used to compare jurisdiction and identifier scope. Checked October 2, 2026.
• Catalog of U.S. Government Publications - U.S. Government Publishing Office. Official publication catalog used to locate and version government materials. Checked October 2, 2026.
• National Archives Catalog - National Archives and Records Administration. Official archival catalog used to document the boundary between current agency systems and archival holdings. Checked October 2, 2026.