WELL · 42-025-33837 · DISTRICT 2
Whiddon #1
Bee County · Holzmark (Yegua) field · Vertical
Whiddon #1 (API 42-025-33837) is a plugged well in Bee County, plugged March 14, 2016, last operated by Enco Exploration Company.
The RRC has issued one drilling permit, issued July 9, 2012, permitted to 5,500 ft.
Completion filings report 2 formation tops, including Singleton, Cole.
Its lease has reported 1.37K barrels of oil and 27.6K mcf of gas since August 2012, last reporting in March 2016.
Operator of record
- Based in
- Corpus Christ, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Mar 19, 2020
- Permits on file
- 204
- Phone
- (361) 882-6100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Enco Exploration Company |
| Production reports | Enco Exploration Companythrough May 2013 |
| Latest permit | Enco Exploration CompanyJul 9, 2012 |
- 5,500
- total depth, ft
- 1
- permits on file
- Jul 9, 2012
- last permit issued
- Aug 26, 2012
- completed
- 1.37K
- cumulative oil, bbl
- 27.6K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2012 THROUGH Mar 2016
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 26, 2012
- Shut in
- —
- Plugged
- Mar 14, 2016
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 |
|---|---|---|---|---|---|---|
| Whiddon O-2-10348 | Holzmark (Yegua) | Enco Exploration Company | 1 | 1.37K | 27.6K | Aug 2012 – Mar 2016 |
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.
- 1Enco Exploration CompanySep 2012 → May 2013
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 743737-99 | Drill | Enco Exploration Company | Jun 28, 2012 | Jul 9, 2012 | Jul 24, 2012 | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-2-10348 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 282 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Singleton | 2,133 | -1,851 |
| Cole | 3,968 | -3,686 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,327 | 5,332 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 602 | 12.25 | 245 S |
| 4.5 | 5,480 | 7.875 | 1,325 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 | Mar 26, 2013 | Sep 7, 2012 | 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-025-33837 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-33837 → 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/02533837, documented in the API reference.