WELL · 42-131-35868 · DISTRICT 4

Kohler V. -A- #153

Plugged

Duval County · Kohler NE (Mirando #2) field  · Vertical

Kohler V. -A- #153 (API 42-131-35868) is a plugged well in Duval County, plugged October 8, 2009, last operated by KD Energy LLC.

The RRC has issued 4 drilling permits between 1982 and 1996, permitted to 3,730 ft.

It was permitted by Manti Operating Company and has since transferred to KD Energy LLC on the wellbore schedule.

Operator of record

KD Energy LLC

Permitted by Manti Operating Company; the EWA schedule now lists a different operator.

Houston, TX · P-5 X, filed May 12, 2026 · 72 permits on file · (713) 364-7822

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleKD Energy LLC
Production reportsManti Operating Companythrough Jun 1997
Latest permitManti Operating CompanyDec 17, 1996

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

3,730
total depth, ft
4
permits on file
Dec 17, 1996
last permit issued
Mar 8, 1989
completed
0
cumulative oil, bbl
115K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 8, 1989
Shut in
—
Plugged
Oct 8, 2009

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kohler, V. -A- G-4-161047Kohler, NE. (Kayla)KD Energy, LLC103.93KOct 1996 – Oct 2009
Kohler, V. "A" G-4-133826Kohler, N.E. (Hockley 2270)Manti Operating Company10111KJan 1993 – Oct 1996

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Exxon Corp.Jan 1993 → Jan 1996
  2. 2Manti Operating CompanyFeb 1996 → Jun 1997

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
456074-99RecompletionManti Operating CompanyDec 9, 1996Dec 17, 1996Oct 10, 19962,850
365643-99RecompletionExxon Corp.Oct 26, 1989Oct 30, 1989—2,850
352508-99RecompletionExxon Corp.Oct 20, 1988Oct 21, 1988—2,850
156137-99DrillExxon Corp.Apr 8, 1982Apr 8, 1982Aug 19, 19823,730

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-133826————
—— G-4-161047————

Perforations

Perforated and open-hole intervals.

FromToType
1,1101,118Perforated
1,8101,816Perforated
2,2652,274Perforated
2,6412,656Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,22412.25650 S
2.3752,510——
5.52,8567.875657 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
00Mar 28, 1997Dec 6, 1996Yes
00Jan 10, 1997——
00Jul 18, 1990Apr 30, 1990Yes
00Jun 15, 1990——
00Jul 5, 1989May 5, 1989—
00Jan 12, 1984Oct 5, 1982—

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/13135868, documented in the API reference.