WELL · 42-387-30544 · DISTRICT 6
Jones #1
Red River County · Heavy O (Paluxy) field · Vertical
Jones #1 (API 42-387-30544) is a plugged well in Red River County, plugged July 20, 1999, last operated by Barrow-Shaver Resources CO..
The RRC has issued one drilling permit, issued May 15, 1998, permitted to 6,500 ft.
Completion filings report one formation top, including Paluxy.
Its lease has reported 1.22K barrels of oil since July 1998, last reporting in October 1999.
Operator of record
- Based in
- Tyler, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Apr 2, 2026
- Permits on file
- 201
- Phone
- (903) 593-5221
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Barrow-Shaver Resources Co. |
| Production reports | Barrow-Shaver Resources Co.through Jun 1999 |
| Latest permit | Barrow-Shaver Resources Co.May 15, 1998 |
- 6,500
- total depth, ft
- 1
- permits on file
- May 15, 1998
- last permit issued
- Jul 15, 1998
- completed
- 1.22K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 1998 THROUGH Oct 1999
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 15, 1998
- Shut in
- —
- Plugged
- Jul 20, 1999
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 lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Jones O-6-13852 | Heavy "O" (Paluxy) | Barrow-Shaver Resources Co. | 1 | 1.22K | 0 | Jul 1998 – Oct 1999 |
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.
- 1Barrow-Shaver Resources Co.Aug 1998 → Jun 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 476335-99 | Drill | Barrow-Shaver Resources Co. | May 15, 1998 | May 15, 1998 | May 21, 1998 | 6,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-6-13852 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 348 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| PaluxyTOP PALUXY | 2,610 | -2,262 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,634 | 2,635 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 320 | 11 | 130 S |
| 5.5 | 2,773 | 7.875 | 270 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 16, 1998 | Aug 12, 1998 | — |
| 00 | Sep 30, 1998 | — | — |
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-387-30544 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-387-30544 → 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/38730544, documented in the API reference.