WELL · 42-137-31926 · DISTRICT 1

Jenkins #6203

Plugged

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

Jenkins #6203 (API 42-137-31926) is a plugged well in Edwards County, plugged March 19, 2020, last operated by Muskegon Development Company.

The RRC has issued one drilling permit (amended once), issued September 6, 2007, permitted to 3,000 ft.

It was permitted by Diamondback Operating, LP 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 Diamondback Operating, LP; 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 Sep 2019
Latest permitDiamondback Operating, LPSep 6, 2007

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

3,000
total depth, ft
2
permits on file
Sep 6, 2007
last permit issued
Jul 14, 2008
completed
0
cumulative oil, bbl
110K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2008 THROUGH Mar 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 14, 2008
Shut in
—
Plugged
Mar 19, 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
Jenkins G-1-243047Cool Water Ranch (Wlfc "a" Coal)Muskegon Development Company10110KJun 2008 – Mar 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. 1Diamondback Operating, LPJun 2008 → May 2012
  2. 2Muskegon Development CompanyJun 2012 → Sep 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
645481-98DrillDiamondback Operating, LPApr 17, 2008Sep 6, 2007Mar 1, 20083,000
645481-99DrillDiamondback Operating, LPSep 4, 2007Sep 6, 2007Mar 1, 20083,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-243047————

Formation tops

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

FormationMD ftSubsea
Base Cretaceous (marker)BASE CRETACEOUS1,375909
WolfcampWOLFCAMP "A" COAL2,363-79

Perforations

Perforated and open-hole intervals.

FromToType
2,3632,400Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
71,4049.625420 S
4.52,488——

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
00Nov 16, 2009Jun 8, 2009—
00Jan 10, 2009Oct 2, 2008Yes
00Dec 16, 2008——

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