WELL · 42-363-34995 · DISTRICT 7
Stephens E #6
Palo Pinto County · Texas-57 (Strawn 3100) field · Vertical
Stephens E #6 (API 42-363-34995) is a plugged well in Palo Pinto County, plugged February 24, 2012, last operated by Stephens Energy Corp..
The RRC has issued one drilling permit, issued February 21, 2001, permitted to 4,400 ft.
Completion filings report 3 formation tops, including Palo Pinto, Atoka, Marble Falls.
Operator of record
Graham, TX · P-5 Y, filed Aug 5, 2022 · 8 permits on file · (940) 549-0281
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Stephens Energy Corp. |
| Production reports | Stephens Energy Corp.through Sep 2001 |
| Latest permit | Stephens Energy Corp.Feb 21, 2001 |
- 4,400
- total depth, ft
- 1
- permits on file
- Feb 21, 2001
- last permit issued
- Apr 1, 2001
- completed
- 0
- cumulative oil, bbl
- 704
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2001 THROUGH Feb 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 1, 2001
- Shut in
- —
- Plugged
- Feb 24, 2012
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 |
|---|---|---|---|---|---|---|
| Stephens E G-8-182857 | Texas-57 (Strawn 3100) | Stephens Energy Corp. | 1 | 0 | 704 | Apr 2001 – Feb 2012 |
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.
- 1Stephens Energy Corp.May 2001 → Sep 2001
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 505548-99 | Drill | Stephens Energy Corp. | Feb 20, 2001 | Feb 21, 2001 | Mar 4, 2001 | 4,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-182857 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,408 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Palo PintoPALO PINTO LIME | 298 | 1,110 |
| AtokaATOKA LIME | 3,862 | -2,454 |
| Marble FallsMARBLE FALLS LIME | 4,306 | -2,898 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,291 | 3,301 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 253 | 12.25 | 170 S |
| 4.5 | 4,338 | 7.875 | 160 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 | Feb 24, 2003 | Nov 12, 2002 | — |
| 00 | Jul 30, 2001 | May 17, 2001 | Yes |
| 00 | Jun 14, 2001 | — | — |
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-363-34995 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-363-34995 → 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/36334995, documented in the API reference.