WELL · 42-137-31708 · DISTRICT 1

Bowermaster 46 #3

Plugged

Edwards County · Cool Water Ranch (Wlfc a Coal) field  · Vertical

Bowermaster 46 #3 (API 42-137-31708) is a plugged well in Edwards County, plugged January 3, 2020, last operated by Muskegon Development Company.

The RRC has issued one drilling permit, issued October 14, 2003, permitted to 2,500 ft.

It was permitted by Patrick Exploration Company and has since transferred to Muskegon Development Company on the wellbore schedule.

Completion filings report 2 formation tops, including Base Cretaceous (marker), Wolfcamp.

Operator of record

Muskegon Development Company

Permitted by Patrick Exploration Company; the EWA schedule now lists a different operator.

MT Pleasant, MI · P-5 Y, filed Feb 7, 2020 · 17 permits on file · (989) 772-4900

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMuskegon Development Company
Production reportsMuskegon Development Companythrough May 2019
Latest permitPatrick Exploration CompanyOct 14, 2003

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

2,500
total depth, ft
1
permits on file
Oct 14, 2003
last permit issued
Mar 24, 2004
completed
0
cumulative oil, bbl
275K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2004 THROUGH Jan 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 24, 2004
Shut in
—
Plugged
Jan 3, 2020

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
Bowermaster "46" G-1-201477Cool Water Ranch (Wlfc "a" Coal)Muskegon Development Company10275KMar 2004 – Jan 2020

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. 1Patrick Exploration CompanyApr 2004 → Jun 2004
  2. 2Diamondback Operating, LPJul 2004 → May 2012
  3. 3Muskegon Development CompanyJun 2012 → May 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
537533-99DrillPatrick Exploration CompanyOct 14, 2003Oct 14, 2003Nov 13, 20032,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-201477————

Formation tops

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

FormationMD ftSubsea
Base Cretaceous (marker)BASE CRETACEOUS1,029956
WolfcampWOLFCAMP "A" COAL2,110-125
WolfcampWOLFCAMP LS2,159-174

Perforations

Perforated and open-hole intervals.

FromToType
2,1102,136Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,06111405 S
5.52,2367.875100 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
00Jul 20, 2004Jun 7, 2004Yes
00Jun 16, 2004——

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