Kansas Plugged Well Record Verification Study 2026

Kansas Plugged Well Record Verification Study 2026: Research question and scope

A Kansas public search can identify a well as plugged, while KGS may hold well pages, scans, logs, or other records related to the same asset. The label is useful, but a review-ready conclusion needs identity, chronology, artifact role, and search limitations. This study sets a verification workflow for land and diligence teams that need to document public plugging evidence without making engineering or legal determinations.

The unit of analysis is one public-source observation at one access time. Facts are limited to what the cited publisher or artifact displays. Analysis compares those facts. Inference is labeled and states what additional evidence would confirm it. Uncertainty includes missing images, unclear dates, changing interfaces, conflicting identifiers, and records not exposed online. This study does not determine title, ownership, boundaries, regulatory compliance, engineering sufficiency, environmental condition, or legal effect.

Define the verification question

Start by naming what must be verified: whether an official public interface currently labels a well as plugged; whether a plugging report or related artifact can be located; or whether a date and identity can be reconciled across sources. These are different questions. A broad request to “confirm plugging” invites unsupported conclusions.

The intake record should include every known native identifier, operator and lease names, well number, county, PLSS location, coordinates and datum if available, and the relevant time period. Record which facts came from the requester and which came from an official source.

Build four evidence layers

Use four layers: proposed or planned work when an official artifact says so; submitted or reported plugging evidence; agency action when an official record explicitly displays it; and later database status observation. Never infer one layer from another. A report can show what was represented; a current status can show what the interface displayed at access time.

Store source-stated dates with their exact labels. “Plugged,” “filed,” “approved,” “scanned,” and “updated” are not interchangeable. When an interface supplies only a date without a clear event label, preserve the label or surrounding context and mark the interpretation as uncertain.

Prove well identity before assembling the packet

Join the plugged-well result to the KGS well page and any scanned artifact using KID or API-oriented identifiers where available. Then compare operator, lease, well number, county, and PLSS location. If the identifier is absent, classify the match as provisional and explain the corroborating evidence.

Do not use proximity on a map as the only join. Points can represent different geometry roles, and nearby wells may share names or leases. Record the map layer, selected feature identifier, coordinates, and access time when spatial evidence is used.

Handle missing records honestly

A no-result response means that one documented query returned no match at one time. Save the interface, search fields, exact values, filters, result count, and timestamp. Repeat with justified variants such as native identifier, lease name, operator, and PLSS fields, while preserving each attempt.

If the public website does not expose the necessary artifact, the next route may be the KGS Data Resources Library or a KCC records process. State the missing evidence and requested record role. Do not transform “not located online” into “not plugged,” “no report,” or “no record exists.”

Quality review and stop rules

A second researcher should reproduce the query, confirm the well identity, reopen decisive files, verify hashes, and trace every date to its label. The final packet should include the search receipt, identity crosswalk, event chronology, document index, status observation, negative searches, and exception list.

Stop when competing well identities remain, a date role is unclear, the source artifact is incomplete, or an engineering, environmental, regulatory, or legal conclusion is requested. The defensible administrative output is a bounded public-record verification that makes both evidence and limitations visible.

Operational worksheet

The minimum worksheet is observation-centered. A later value creates another row instead of overwriting earlier evidence.

• query interface: Record the literal source value, publisher, record role, labeled event date, and access time. Keep any normalized or inferred value in a separate field with its transformation rule.
• search inputs: Record the literal source value, publisher, record role, labeled event date, and access time.
• result count: Record the literal source value, publisher, record role, labeled event date, and access time.
• well identifier: Record the literal source value, publisher, record role, labeled event date, and access time. Keep any normalized or inferred value in a separate field with its transformation rule.
• operator as shown: Record the literal source value, publisher, record role, labeled event date, and access time.
• lease and well number: Record the literal source value, publisher, record role, labeled event date, and access time.
• PLSS location: Record the literal source value, publisher, record role, labeled event date, and access time. Keep any normalized or inferred value in a separate field with its transformation rule.
• status label: Record the literal source value, publisher, record role, labeled event date, and access time.
• plugging document role: Record the literal source value, publisher, record role, labeled event date, and access time.
• source-stated date: Record the literal source value, publisher, record role, labeled event date, and access time. Keep any normalized or inferred value in a separate field with its transformation rule.
• file hash: Record the literal source value, publisher, record role, labeled event date, and access time.
• access timestamp: Record the literal source value, publisher, record role, labeled event date, and access time.

Sort the completed worksheet by source event and then observation time, not by discovery order. Give every material conflict an owner, next source, and stop condition. If a field is unavailable, record the attempted query and result rather than filling the gap from memory or assumption.

Data sources and methodology

We reviewed the official Kansas source routes listed below on October 7, 2026. We inventoried each route's publisher, record role, searchable identifiers, stated dates, download or document functions, and public limitations. The method preserves source strings, direct locators, query inputs, access timestamps, and material files with byte counts and SHA-256 hashes. Normalization and comparisons occur in separate derived fields so another researcher can reproduce the work.

For quality control, a second reviewer should rerun decisive searches, reopen every source used for a material conclusion, verify file hashes, check identifier formatting and leading zeroes, and review all conflicts rather than only matched records. Facts, analysis, inference, and unavailable evidence should be visibly separated in the handoff.

Limitations

This is a source-architecture and workflow study, not a statistical sample of Kansas wells, operators, production reports, completion records, plugging records, or database accuracy. We did not test authenticated KOLAR functions, agency back-office systems, every possible query combination, all physical holdings, paid sources, or client records. Interfaces and underlying records may change after the checked date.

A negative result is bounded by the documented interface, inputs, filters, coverage, and access time. It does not prove that an event or document does not exist. Public records also do not eliminate the need for qualified legal, regulatory, engineering, survey, environmental, accounting, or title review.

Conclusion

For Kansas plugged well record verification, remote land support is most useful when it preserves provenance and shortens the professional reviewer’s exception list. A defensible packet connects each value to its source and time, keeps incompatible record roles separate, exposes conflicts, and states exactly where inference begins. That supports title research, lease and well data maintenance, GIS coordination, diligence, and document preparation without transferring professional judgment to an administrative workflow.

Sources

• KCC Oil & Gas: Kansas Corporation Commission. Official Conservation Division entry point for regulation, records, forms, dockets, maps, and public searches. Checked October 7, 2026.
• KCC Oil & Gas Data Search: Kansas Corporation Commission. Official directory for operator, transfer, plugged-well, well-log, production, docket, and intent searches. Checked October 7, 2026.
• KCC Oil & Gas Forms: Kansas Corporation Commission. Official forms directory defining the roles of licensing, inventory, transfer, completion, production-test, and plugging records. Checked October 7, 2026.
• Kansas Oil Operators: Kansas Corporation Commission. Official current-license query with active-only and all-operator views and downloadable lists. Checked October 7, 2026.
• KCC Well Inventory FAQs: Kansas Corporation Commission. Official explanation of the operator well inventory, its scope, correction workflow, and relationship to transfers. Checked October 7, 2026.
• KCC Form ACO-1 Instructions: Kansas Corporation Commission. Official completion-form instructions describing operator, well, location, test, log, sample, and first-production fields. Checked October 7, 2026.
• KCC Form T-1 Transfer: Kansas Corporation Commission. Official request for change of operator and permit-transfer form. Checked October 7, 2026.
• KGS Oil and Gas Well Database: Kansas Geological Survey. Official statewide well query with KID, API number, operator, lease, location, status, documents, and bulk files. Checked October 7, 2026.
• KGS Oil and Gas Database Update: Kansas Geological Survey. Official March 2026 notice describing the updated well database and retained query and download functions. Checked October 7, 2026.
• Data@KGS Energy Portal: Kansas Geological Survey. Official portal for well, production, mapper, injection, and subsurface datasets. Checked October 7, 2026.
• KGS Data Resources Library: Kansas Geological Survey. Official description of the state repository for oil, gas, and water-well records and its PLSS filing system. Checked October 7, 2026.
• KGS Data and Maps: Kansas Geological Survey. Official overview of Kansas oil-and-gas records, maps, wells, production, and physical holdings. Checked October 7, 2026.
• KGS Oil and Gas Mapper: Kansas Geological Survey. Official map interface for well information derived from filings submitted to the KCC. Checked October 7, 2026.

Frequently asked questions

Is the newest public screen the complete historical record?

No. It is a current, dated observation. Earlier filings, scans, transfers, downloads, physical holdings, or later corrections may be needed to reconstruct the relevant history.

Can a support team make the final professional determination?

Support staff can locate, preserve, transcribe, compare, and route evidence. Qualified reviewers remain responsible for title, legal, survey, engineering, regulatory, accounting, and other professional conclusions.

What should happen when KCC and KGS records differ?

Keep both observations, confirm identity, compare record roles and dates, and open a focused exception. The difference may reflect timing, scope, correction, or system design; do not invent the cause.

If your team needs a review-ready Kansas plugged well record verification packet, Book a free consultation.