WELL · 42-353-32783 · DISTRICT 7
Patterson #4
Nolan County · Group (Massive) field · Vertical
Patterson #4 (API 42-353-32783) is a plugged well in Nolan County, plugged June 5, 2015, last operated by Clear Fork Incorporated.
The RRC has issued one drilling permit (amended once), issued February 13, 2003, permitted to 4,300 ft.
Completion filings report 3 formation tops, including B/Coleman Junction, T/Cisco Lm, T/Upper Cisco Sd.
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 Mar 2013 |
| Latest permit | Clear Fork, IncorporatedFeb 13, 2003 |
- 4,300
- total depth, ft
- 2
- permits on file
- Feb 13, 2003
- last permit issued
- Mar 18, 2003
- completed
- 0
- cumulative oil, bbl
- 92.6K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2003 THROUGH Jun 2015
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 18, 2003
- Shut in
- —
- Plugged
- Jun 5, 2015
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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Patterson G-8-195909 | Group (Massive) | Clear Fork, Incorporated | 1 | 0 | 92.6K | Mar 2003 – Jun 2015 |
| — G-8-195908 | — | — | 0 | 0 | 0 | — |
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, IncorporatedMar 2003 → Mar 2013
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 528291-98 | Drill | Clear Fork, Incorporated | May 1, 2003 | Feb 13, 2003 | — | 4,300 |
| 528291-99 | Drill | Clear Fork, Incorporated | Feb 10, 2003 | Feb 13, 2003 | Feb 20, 2003 | 4,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Mar 18, 2003 | Patterson G-8-195909 | Group (Massive) | Clear Fork Incorporated | Plugged | — |
| — | Patterson G-8-195908 | Group (Massive) | Clear Fork Incorporated | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,227 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| B/Coleman Junction | 3,420 | -1,193 |
| T/Cisco LM | 3,824 | -1,597 |
| T/Upper Cisco SD | 4,090 | -1,863 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,092 | 4,093 | Perforated |
| 4,111 | 4,113 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 440 | 12.25 | 225 S |
| 4.5 | 4,199 | 7.875 | 370 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 | Dec 8, 2003 | — | — |
| 00 | Aug 28, 2003 | Mar 24, 2003 | Yes |
| 00 | Aug 12, 2003 | — | — |
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-32783 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-353-32783 → 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/35332783, documented in the API reference.