Skip to content

Operations and Evidence

Kansas Operator License and Well Inventory Lineage Study 2026

A record-lineage method for relating Kansas operator licenses, well inventories, and T-1 transfers without overwriting history.

Landman Business Editorial TeamSources: 12Verified 2026-10-07Reviewed 2026-10-0711 minute read
Evidence worksheet for Kansas operator license and well inventory lineage

3 record roles

5 event classes

13 lineage fields

Kansas Operator License and Well Inventory Lineage Study 2026: Research question and scope

A Kansas operator name can appear in a current license search, a well inventory, a transfer request, a completion record, and a well database observation. Those appearances are related but not interchangeable. This study defines a lineage model that helps a land-support team describe who was shown in which role, by which source, and at what time without making a legal conclusion about responsibility.

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.

Separate the three record roles

The operator-license record describes a regulated party and its displayed license status. The well inventory associates an operator with the unplugged wells it reports or is required to report. A T-1 is a request for a change of operator or permit transfer and can contain transferor, transferee, well, and notice information. None of these roles should be collapsed into one “operator” field.

Create an observation for each record role. Store the publisher’s operator name and license number literally, the well identifier when present, the status or action label, every labeled date, and the access time. A party’s presence on a form is a fact about that artifact; it is not by itself proof that the requested change was approved or effective.

Build an event sequence

A practical sequence includes license observation, inventory observation, transfer request, agency approval observation, and later well-database observation. The sequence is evidence-led: it does not assume that a submission date is an approval date or that a current database value states when a change became effective.

When a new license number appears, retain the old and new identifiers and look for an explicit source relationship. KCC’s well-inventory guidance notes that operators receiving a new license number must transfer wells from the old license through a T-1. That is a workflow clue, not permission to infer that a particular transfer occurred. The specific well and transfer evidence still matter.

Reconcile names without merging parties

Normalize punctuation and common business suffixes only in a derived search column. Preserve legal or trade names as displayed. Similar names, shared addresses, or the same contact detail can support review, but they do not establish that two license records represent the same legal person.

Use the license number as the primary operator key where the official source provides it. If one name maps to multiple numbers, report the one-to-many relationship. If one number appears with materially different names, preserve the dated observations and seek the underlying license or transfer records. Do not choose the newest string and erase the rest.

Treat current status carefully

The public operator query offers active-only and all-listing views and says the information is continuously updated. “Active” is therefore a source-labeled current observation. It does not establish operatorship of every listed well on every earlier date. Likewise, an inactive operator record does not explain when or why a well moved.

For diligence, pair the current query with well-specific transfer and inventory evidence. Record the query mode, search text, result count, and access time. If no result appears, broaden the search as the KCC page suggests and document both attempts. A negative query is not proof that the party never held a Kansas license.

Deliver a bounded operatorship packet

The final packet should contain an operator identifier table, well-specific event timeline, direct locators to transfer and inventory evidence, unresolved name or number conflicts, and a clear statement of the period covered. A reviewer should be able to distinguish submission, approval, and current display at a glance.

Escalate when the transfer record is missing, license numbers conflict, the well cannot be identified confidently, an effective date requires legal interpretation, or the public systems do not expose the necessary history. Administrative research should organize the evidence and exceptions, not decide legal operatorship.

Operational worksheet

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

  • operator name as shown: 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.
  • license number: Record the literal source value, publisher, record role, labeled event date, and access time.
  • license status: Record the literal source value, publisher, record role, labeled event date, and access time.
  • record role: 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.
  • well identifier: Record the literal source value, publisher, record role, labeled event date, and access time.
  • lease and well name: Record the literal source value, publisher, record role, labeled event date, and access time.
  • transferor: 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.
  • transferee: Record the literal source value, publisher, record role, labeled event date, and access time.
  • filing date as labeled: Record the literal source value, publisher, record role, labeled event date, and access time.
  • approval date as labeled: 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.
  • inventory observation date: Record the literal source value, publisher, record role, labeled event date, and access time.
  • source locator: Record the literal source value, publisher, record role, labeled event date, and access time.
  • exception reason: 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.

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.

Evidence layer Required control What it does not prove
Public query observation Interface, inputs, filters, result locator, and access time A complete historical record
Source artifact Publisher, record role, native identifier, labeled date, and page locator The meaning of an unstated or ambiguous event
Derived comparison Preserved source values, transformation rule, reviewer, and run time Title, compliance, engineering sufficiency, or legal effect

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 operator license and well inventory lineage, 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 OPL-1 License Application: Kansas Corporation Commission. Official operator-license application and instructions. 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 and Maps: Kansas Geological Survey. Official overview of Kansas oil-and-gas records, maps, wells, production, and physical holdings. 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 operator license and well inventory lineage packet, Book a free consultation.

Kansas oil and gasland researchpublic recordsevidence control