WELL · 42-353-33318 · DISTRICT 7
White Hat 211 #2
Nolan County · Regalo-Divino (U. Cisco) field · Vertical
White Hat 211 #2 (API 42-353-33318) is a plugged well in Nolan County, plugged June 18, 2020, last operated by Clear Fork Incorporated.
The RRC has issued one drilling permit (amended once), issued May 3, 2012, permitted to 4,500 ft.
Completion filings report 2 formation tops, including Coleman Junction, Cisco.
Its 2 leases have reported 4.49K barrels of oil and 113K mcf of gas since July 2012, last reporting in July 2020. The leases carry 2 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Abilene, TX
- P-5 status
- Active (A)
- P-5 last filed
- Feb 4, 2026
- Permits on file
- 472
- Phone
- (325) 677-1309
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Clear Fork Incorporated |
| Production reports | Clear Fork, Incorporatedthrough Aug 2016 |
| Latest permit | Clear Fork, IncorporatedMay 3, 2012 |
- 4,500
- total depth, ft
- 2
- permits on file
- May 3, 2012
- last permit issued
- Jan 11, 2014
- completed
- 4.49K
- cumulative oil, bbl
- 113K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2012 THROUGH Jul 2020
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 11, 2014
- Shut in
- —
- Plugged
- Jun 18, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| White Hat 211 O-8-31621 | Regalo-Divino (U. Cisco) | Clear Fork, Incorporated | 1 | 4.49K | 32.8K | Jan 2014 – Jul 2020 |
| White Hat 211 G-8-266050 | Regalo-Divino (U. Cisco) | Clear Fork, Incorporated | 1 | 0 | 80.6K | Jul 2012 – Nov 2014 |
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.
- 1Clear Fork, IncorporatedAug 2012 → Aug 2016
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 738714-98 | Drill | Clear Fork, Incorporated | Aug 13, 2012 | May 3, 2012 | Jun 1, 2012 | 4,500 |
| 738714-99 | Drill | Clear Fork, Incorporated | Apr 20, 2012 | May 3, 2012 | — | 4,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-266050 | — | — | — | — |
| — | — O-8-31621 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,428 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Coleman Junction | 3,000 | -572 |
| Cisco | 4,330 | -1,902 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,330 | 4,333 | Perforated |
| 4,333 | 4,336 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 339 | 12.25 | 240 S |
| 8.625 | 340 | 12.25 | 240 S |
| 5.5 | 4,447 | 7.875 | 250 S |
| 5.5 | 4,456 | 7.875 | 250 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 | Oct 17, 2014 | Feb 4, 2014 | Yes |
| 00 | Feb 7, 2013 | Aug 23, 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-353-33318 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-353-33318 → 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/35333318, documented in the API reference.