TEXAS · WELLS · NOLAN COUNTY · API 42-353-32984 · DISTRICT 6E
Evb (Canyon Sand) Unit #1444
Nolan County · Evb (4800 Canyon Sand) field · Shut In · Vertical
Evb (Canyon Sand) Unit #1444 (API 42-353-32984) is a well in Nolan County operated by Clear Fork Incorporated, completed October 1, 2007 and listed as shut in on the RRC schedule, shut in February 1, 2024.
The RRC has issued one drilling permit (amended once), issued August 13, 2007, permitted to 6,640 ft.
Completion filings report 2 formation tops, including Cisco, Palo Pinto.
Its 2 leases have reported 621K barrels of oil and 188K mcf of gas since October 2007, last reporting volume in April 2026. The leases carry 19 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, IncorporatedAug 13, 2007 |
- 6,640
- total depth, ft
- 2
- permits on file
- Aug 13, 2007
- last permit issued
- Oct 1, 2007
- completed
- 621K
- cumulative oil, bbl
- 188K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2007 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 1, 2007
- Shut in
- Feb 1, 2024
- 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 2 leases this well is completed on; they carry 19 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Evb (Canyon Sand) Unit O-8-30532 | Evb (4800 Canyon Sand) | Clear Fork, Incorporated | 17 | 601K | 148K | May 2010 – Apr 2026 |
| Boyd, C. E. 44C O-8-30015 | Evb (4800 Canyon Sand) | Clear Fork, Incorporated | 2 | 20.2K | 40.3K | Oct 2007 – Apr 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, IncorporatedOct 2007 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 644143-98 | Drill | Clear Fork, Incorporated | Sep 4, 2007 | Aug 13, 2007 | Aug 27, 2007 | 7,000 |
| 644143-99 | Drill | Clear Fork, Incorporated | Aug 9, 2007 | Aug 13, 2007 | — | 5,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Oct 1, 2007 | Evb (Canyon Sand) Unit O-8-30532 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Shut In · shut in Feb 1, 2024 | 6,640 |
| Oct 1, 2007 | Boyd C. E. 44C O-8-30015 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Not on Schedule | — |
| — | Boyd C. E. 44C O-8-30015 | Evb (4800 Canyon Sand) | Clear Fork Incorporated | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,448 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| CiscoBASE OF CISCO LIME | 4,520 | -2,072 |
| Palo PintoTOP PALO PINTO REEF | 5,744 | -3,296 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,917 | 4,920 | Perforated |
| 4,931 | 4,933 | Perforated |
| 4,938 | 4,950 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 488 | 12.25 | 275 S |
| 5.5 | 5,936 | 7.875 | 125 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 9, 2010 | Oct 29, 2007 | Yes |
| 00 | Jun 9, 2008 | Oct 29, 2007 | Yes |
| 00 | May 23, 2008 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Nov 2, 2010. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Cisco, Palo Pinto | TIFF | 75 to 6,526 | Nov 2, 2010run Sep 15, 2007 | 0.78 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-32984 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-353-32984 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/35332984, documented in the API reference.