WELL · 42-041-31113 · DISTRICT 3

Kavanaugh M.S. #1

Plugged

Brazos County · Aggieland (Woodbine) field  · Vertical

Kavanaugh M.S. #1 (API 42-041-31113) is a plugged well in Brazos County, plugged May 31, 2018, last operated by Ramtex Energy LLC.

The RRC has issued one drilling permit, issued March 2, 1984, permitted to 10,000 ft.

It was permitted by Inexco Oil Company and has since transferred to Ramtex Energy LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Pecan Gap, Austin Chalk, Eagle Ford, Woodbine.

Its lease has reported 21.4K barrels of oil and 288K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Ramtex Energy LLC

Permitted by Inexco Oil Company; the EWA schedule now lists a different operator.

Tulsa, OK · P-5 Y, filed Mar 4, 2026 · 20 permits on file · (479) 287-7920

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRamtex Energy LLC
Production reportsRamtex Energy LLCthrough May 2016
Latest permitInexco Oil CompanyMar 2, 1984

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

10,000
total depth, ft
1
permits on file
Mar 2, 1984
last permit issued
Sep 22, 1984
completed
21.4K
cumulative oil, bbl
288K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 22, 1984
Shut in
—
Plugged
May 31, 2018

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kavanaugh, M.S. O-3-17944Aggieland (Woodbine)Ramtex Energy LLC121.4K288KJan 1993 – Jul 2026

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. 1Energy Development Corp.Jan 1993 → Aug 2001
  2. 2Samedan Oil CorporationFeb 2002 → Dec 2002
  3. 3Noble Energy IncJan 2003 → Feb 2004
  4. 4Chaparral Energy, L.L.C.Mar 2004 → Mar 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
231243-99DrillInexco Oil CompanyAug 7, 1984Mar 2, 1984—10,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-17944————

Formation tops

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

FormationMD ftSubsea
Pecan Gap8,507-8,219
Austin Chalk9,324-9,036
Eagle FordEAGLEFORD9,625-9,337
Woodbine9,685-9,397

Perforations

Perforated and open-hole intervals.

FromToType
9,6859,691Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,44512.251,150 S
5.59,7838.75500 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
00Oct 23, 1984Sep 27, 1984—
00Oct 6, 1984——

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