WELL · 42-237-38315 · DISTRICT 9
Ellis A #4
Jack County · Lost Valley (Stanley Congl.) field · Vertical
Ellis A #4 (API 42-237-38315) is a plugged well in Jack County, plugged August 20, 1999, last operated by Miles Production CO..
The RRC has issued one drilling permit, issued September 16, 1997, permitted to 4,999 ft.
Completion filings report 5 formation tops, including Palo Pinto, Village Bend, Bryson, Caddo.
Operator of record
Argyle, TX · P-5 Y, filed May 6, 2005 · 280 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Miles Production Co. |
| Production reports | Miles Production Co.through Jan 1999 |
| Latest permit | Miles Production Co.Sep 16, 1997 |
- 4,999
- total depth, ft
- 1
- permits on file
- Sep 16, 1997
- last permit issued
- Nov 7, 1997
- completed
- 0
- cumulative oil, bbl
- 24.2K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 1997 THROUGH Aug 1999
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 7, 1997
- Shut in
- —
- Plugged
- Aug 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 |
|---|---|---|---|---|---|---|
| Ellis "A" G-13-167717 | Lost Valley (Stanley Congl.) | Miles Production Co. | 1 | 0 | 24.2K | Nov 1997 – Aug 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.
- 1Miles Production Co.Dec 1997 → Jan 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 467005-99 | Drill | Miles Production Co. | Sep 2, 1997 | Sep 16, 1997 | Sep 19, 1997 | 4,999 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-13-167717 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,073 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Palo Pinto | 1,864 | -791 |
| Village Bend | 2,412 | -1,339 |
| BrysonBRYSON LM. | 3,515 | -2,442 |
| Caddo | 4,558 | -3,485 |
| Marble Falls | 5,006 | -3,933 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,980 | 4,983 | Perforated |
| 4,984 | 4,986 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 470 | 12.25 | 390 S |
| 4.5 | 5,070 | 7.875 | 215 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 | May 11, 1998 | Nov 17, 1997 | Yes |
| 00 | May 4, 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-237-38315 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-38315 → 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/23738315, documented in the API reference.