WELL · 42-353-32864 · DISTRICT 7
Evb (Canyon Sand) Unit #1159
Nolan County · Evb (4800 Canyon Sand) field · Producing · Vertical
Evb (Canyon Sand) Unit #1159 (API 42-353-32864) is a well in Nolan County operated by Clear Fork Incorporated, completed December 7, 2007 and listed as producing on the RRC schedule.
The RRC has issued 2 drilling permits between 2005 and 2007, permitted to 6,777 ft.
Completion filings report 3 formation tops, including Cisco, Canyon, Palo Pinto.
Its 3 leases have reported 723K barrels of oil and 280K mcf of gas since April 2000, last reporting in July 2026. The leases carry 22 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 Apr 2026 |
| Latest permit | Clear Fork, IncorporatedDec 3, 2007 |
- 6,777
- total depth, ft
- 2
- permits on file
- Dec 3, 2007
- last permit issued
- Dec 7, 2007
- completed
- 723K
- cumulative oil, bbl
- 280K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2000 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 7, 2007
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 3 leases this well is completed on; they carry 22 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Boyd, C.E. "59" O-8-29582 | Evb, S. (Caddo Conglomerate) | Clear Fork, Incorporated | 2 | 40.5K | 51.1K | Apr 2005 – Jul 2026 |
| Evb (Canyon Sand) Unit O-8-30532 | Evb (4800 Canyon Sand) | Clear Fork, Incorporated | 17 | 601K | 148K | May 2010 – Jul 2026 |
| Boyd, C. E. O-8-28809 | Evb (4800 Canyon Sand) | Clear Fork, Incorporated | 3 | 81.1K | 80.8K | Apr 2000 – Jul 2010 |
Oil, barrels lease total
Last 12 months 5,452 · prior 12 7,728(-29%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Clear Fork, IncorporatedApr 2000 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 650161-99 | Recompletion | Clear Fork, Incorporated | Nov 26, 2007 | Dec 3, 2007 | Dec 3, 2007 | 6,758 |
| 557216-99 | Drill | Clear Fork, Incorporated | Feb 3, 2005 | Feb 8, 2005 | Mar 17, 2005 | 6,900 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 3, 2008 | Boyd C.E. 59 O-8-29582 | Evb S. (Caddo Conglomerate) | Clear Fork Incorporated | NO Production · shut in Feb 1, 2024 | 6,777 |
| Dec 7, 2007 | Evb (Canyon Sand) Unit O-8-30532 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Producing | 6,777 |
| Dec 7, 2007 | Boyd C. E. O-8-28809 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Not on Schedule | — |
| Dec 7, 2007 | Boyd C. E. O-8-28809 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Not on Schedule | — |
| Apr 1, 2005 | Boyd C.E. 59 O-8-29582 | Evb S. (Caddo Conglomerate) | Clear Fork Incorporated | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,530 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| CiscoCISCO LIME | 4,372 | -1,842 |
| CanyonUPPER CANYON SAND | 4,584 | -2,054 |
| Palo PintoPALO PINTO REEF | 5,802 | -3,272 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,873 | 4,881 | Perforated |
| 4,904 | 4,909 | Perforated |
| 4,912 | 4,931 | Perforated |
| 6,596 | 6,628 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 503 | 12.25 | 310 S |
| 5.5 | 6,758 | 7.875 | 385 S |
| 5.5 | 6,777 | 7.875 | 385 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 | Jun 9, 2010 | Dec 10, 2007 | Yes |
| 00 | Oct 28, 2009 | Jun 5, 2009 | — |
| 00 | Aug 26, 2009 | Dec 10, 2007 | Yes |
| 00 | Aug 26, 2009 | Apr 27, 2005 | Yes |
| 00 | Oct 1, 2008 | Dec 10, 2007 | Yes |
| 00 | Aug 5, 2008 | — | — |
| 00 | Sep 2, 2005 | Apr 27, 2005 | Yes |
| 00 | Jul 6, 2005 | — | — |
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-32864 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-353-32864 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- Nov 2025
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000102006 | H-1 Injection | Not activated | 500 | 1,500 | 4,873–4,931 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 0 · prior 12 0
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/35332864, documented in the API reference.