WELL · 42-485-44077 · DISTRICT 9

Holman L. K. #17

Y

Wichita County · Wichita County Regular field · Producing  · Vertical

Holman L. K. #17 (API 42-485-44077) is a well in Wichita County operated by Rog Enterprises LLC, completed May 18, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 23, 2006, permitted to 1,950 ft.

It was permitted by Felty, F. T. Operating Company and has since transferred to Rog Enterprises LLC on the wellbore schedule.

Completion filings report one formation top, including Gunsight.

Its lease has reported 62.1K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Rog Enterprises LLC

Permitted by Felty, F. T. Operating Company; the EWA schedule now lists a different operator.

Burkburnett, TX · P-5 Y, filed Mar 4, 2026 · 42 permits on file · (214) 514-6379

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRog Enterprises LLC
Production reportsRog Enterprises, LLCthrough Apr 2026
Latest permitFelty, F. T. Operating CompanyMar 23, 2006

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

1,950
total depth, ft
1
permits on file
Mar 23, 2006
last permit issued
May 18, 2006
completed
62.1K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 18, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Holman, L. K. O-13-27494Wichita County RegularRog Enterprises, LLC1662.1K21Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 480 · prior 12 612(-22%)

050100202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Felty, F. T. Operating CompanyJan 1993 → Jul 2018
  2. 2Rog Enterprises, LLCAug 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
616027-99DrillFelty, F. T. Operating CompanyMar 17, 2006Mar 23, 2006May 17, 20061,950

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27494————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Gunsight1,200

Perforations

Perforated and open-hole intervals.

FromToType
1,2011,212Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,2656.75180 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Dec 15, 2006Jul 19, 2006Yes
00Aug 16, 2006——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/48544077, documented in the API reference.