WELL · 42-485-42351 · DISTRICT 9

Munger K #2

Plugged

Wichita County · Wichita County Regular field  · Vertical

Munger K #2 (API 42-485-42351) is a plugged well in Wichita County, plugged June 3, 2011, last operated by Extex Operating Company.

The RRC has issued one drilling permit, issued May 8, 1991, permitted to 1,999 ft.

It was permitted by Sep, Inc. and has since transferred to Extex Operating Company on the wellbore schedule.

Completion filings report 2 formation tops, including Thomas Sand, Gunsight.

Its lease has reported 375 barrels of oil and 8 mcf of gas since January 1993, last reporting in December 2011. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Extex Operating Company

Permitted by Sep, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Nov 4, 2025 · 117 permits on file · (713) 870-4327

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleExtex Operating Company
Production reportsExtex Operating Companythrough Nov 2003
Latest permitSep, Inc.May 8, 1991

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

1,999
total depth, ft
1
permits on file
May 8, 1991
last permit issued
May 6, 1991
completed
375
cumulative oil, bbl
8
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 6, 1991
Shut in
—
Plugged
Jun 3, 2011

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Munger "K" O-13-27491Wichita County RegularExtex Operating Company23758Jan 1993 – Dec 2011

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. 1Sep, Inc.Jan 1993 → Nov 1993
  2. 2Bud's Drilling Company, Inc.Aug 1996 → Aug 1997
  3. 3Aztel Operating Inc.Oct 2003 → Oct 2003
  4. 4Extex Operating CompanyNov 2003 → Nov 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
387370-99DrillSep, Inc.May 1, 1991May 8, 1991May 2, 19911,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27491————

Formation tops

As filed on W-2/G-1. Subsea from 1,012 ft elevation.Download CSV →

FormationMD ftSubsea
Thomas Sand1,508-496
GunsightGUNSIGHT LIME1,758-746
GunsightGUNSIGHT SAND1,770-758

Perforations

Perforated and open-hole intervals.

FromToType
1,7701,771Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
5.51,7807.875300 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
00Jun 26, 1991May 20, 1991Yes
00Jun 10, 1991——

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