WELL · 42-137-32133 · DISTRICT 1
Patterson #3206
Edwards County · Hackberry Creek (Canyon) field · Vertical
Patterson #3206 (API 42-137-32133) is a plugged well in Edwards County, plugged November 6, 2019, last operated by Muskegon Development Company.
The RRC has issued one drilling permit, issued April 12, 2013, permitted to 4,700 ft.
Completion filings report 2 formation tops, including Wolfcamp, Canyon.
Operator of record
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 schedule | Muskegon Development Company |
| Production reports | Muskegon Development Companythrough Oct 2018 |
| Latest permit | Muskegon Development CompanyApr 12, 2013 |
- 4,700
- total depth, ft
- 1
- permits on file
- Apr 12, 2013
- last permit issued
- Jun 28, 2013
- completed
- 0
- cumulative oil, bbl
- 18.7K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2013 THROUGH Nov 2019
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 28, 2013
- Shut in
- —
- Plugged
- Nov 6, 2019
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Patterson G-1-272737 | Hackberry Creek (Canyon) | Muskegon Development Company | 1 | 0 | 18.7K | Jun 2013 – Nov 2019 |
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.
- 1Muskegon Development CompanyJul 2013 → Oct 2018
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 759909-99 | Drill | Muskegon Development Company | Apr 2, 2013 | Apr 12, 2013 | May 31, 2013 | 4,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-1-272737 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,885 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,734 | 2,754 | Perforated |
| 2,804 | 2,820 | Perforated |
| 2,824 | 2,836 | Perforated |
| 3,054 | 3,068 | Perforated |
| 3,080 | 3,090 | Perforated |
| 3,095 | 3,109 | Perforated |
| 3,312 | 3,328 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,027 | 12.25 | 450 S |
| 7 | 2,685 | 8.75 | 200 S |
| 4.5 | 3,855 | 6.125 | 235 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jul 18, 2014 | Jan 6, 2014 | Yes |
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.
- Wellbore filings for 42-137-32133 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-137-32133 → scanned completion filings
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/13732133, documented in the API reference.