TEXAS · WELLS · ANDREWS COUNTY · API 42-003-04663 · DISTRICT 7B
Shafter Lake Clearfork Unit #504
Andrews County · Shafter Lake (Clear Fork) field · Vertical
Shafter Lake Clearfork Unit #504 (API 42-003-04663) is a plugged well in Andrews County, plugged March 20, 2025, last operated by Highmark Energy Operating LLC.
The RRC has issued one drilling permit, issued May 24, 1995, permitted to 9,880 ft.
It was permitted by Henry Petroleum Corp. and has since transferred to Highmark Energy Operating LLC on the wellbore schedule.
Completion filings report 5 formation tops, including Ruslter, Yates, San Andres, Clear Fork.
Its 3 leases have reported 5.63M barrels of oil and 1.51M mcf of gas since January 1993, last reporting in July 2026. The leases carry 86 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Henry Petroleum Corp.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 9, 2026
- Permits on file
- 23
- Phone
- (469) 214-5299
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Highmark Energy Operating LLC |
| Production reports | Highmark Energy Operating, LLCthrough Apr 2026 |
| Latest permit | Henry Petroleum Corp.May 24, 1995 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,880
- total depth, ft
- 1
- permits on file
- May 24, 1995
- last permit issued
- Aug 7, 1995
- completed
- 5.63M
- cumulative oil, bbl
- 1.51M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 7, 1995
- Shut in
- —
- Plugged
- Mar 20, 2025
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 86 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Shafter Lake Clearfork Unit O-10-34411 | Shafter Lake (Clear Fork) | Highmark Energy Operating, LLC | 79 | 5.61M | 1.5M | Feb 1995 – Jul 2026 |
| University -T- O-10-5502 | Shafter Lake (Devonian) | Henry Petroleum Corp. | 2 | 7.91K | 4.05K | Jan 1993 – Sep 1995 |
| University -T- O-10-5496 | Shafter Lake (Clear Fork) | Henry Petroleum Corp. | 5 | 10.5K | 4.3K | Jan 1993 – Apr 1995 |
Oil, barrels lease total
Last 12 months 74,714 · prior 12 76,953(-3%)
Gas, mcf lease total
Last 12 months 6,401 · prior 12 11,994(-47%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Phillips Petroleum CompanyJan 1993 → Apr 1994
- 2Henry Petroleum Corp.May 1994 → Mar 2001
- 3Henry Petroleum LPApr 2001 → Dec 2008
- 4COG Operating LLCJan 2009 → Dec 2012
- 5Legacy Reserves Operating LPJan 2013 → Feb 2023
- 6Highmark Energy Operating, LLCMar 2023 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 436076-99 | Recompletion | Henry Petroleum Corp. | May 22, 1995 | May 24, 1995 | Jul 31, 1995 | 9,880 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 7, 1995 | Shafter Lake Clearfork Unit O-10-34411 | Shafter Lake (Clear Fork) | Highmark Energy Operating LLC | Plugged | — |
| — | University -T- O-10-5502 | Shafter Lake (Devonian) | Henry Petroleum Corp. | Plugged | — |
| — | University -T- O-10-5496 | Shafter Lake (Clear Fork) | Henry Petroleum Corp. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,227 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Ruslter | 1,670 | 1,557 |
| Yates | 2,895 | 332 |
| San Andres | 4,455 | -1,228 |
| Clear ForkUPPER CLEARFORK | 5,708 | -2,481 |
| Clear ForkLOWER CLEARFORK | 6,645 | -3,418 |
| Tubb | 6,758 | -3,531 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,647 | 6,653 | Perforated |
| 6,656 | 6,660 | Perforated |
| 6,674 | 6,679 | Perforated |
| 6,776 | 6,780 | Perforated |
| 6,782 | 6,820 | Perforated |
| 6,811 | 6,869 | Perforated |
| 6,825 | 6,831 | Perforated |
| 6,881 | 6,889 | Perforated |
| 6,910 | 6,917 | Perforated |
| — | 6,869 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 320 | — | — |
| 8.625 | 4,109 | — | 3,500 S |
| 5.5 | 9,872 | — | — |
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 | Nov 21, 1995 | Sep 7, 1995 | Yes |
| 00 | Mar 7, 1995 | Aug 26, 1965 | — |
| 00 | Jan 12, 1984 | Aug 26, 1965 | — |
| 00 | Jan 12, 1984 | — | — |
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-003-04663 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-003-04663 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/00304663, documented in the API reference.