WELL · 42-429-33324 · DISTRICT 7
Keith #4
Stephens County · Vertical
Keith #4 (API 42-429-33324) is a plugged well in Stephens County, plugged August 28, 1982, last operated by Herring, Ray.
The RRC has issued 2 drilling permits between 1982 and 2006, permitted to 4,300 ft.
Completion filings report 2 formation tops, including Caddo, Marble Falls.
Operator of record
- Based in
- Graham, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Apr 18, 2013
- Permits on file
- 401
- Phone
- (940) 549-0370
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Ray Herring Operating Co., LLCthrough Mar 2026 |
| Latest permit | Herring, RayMay 2, 2006 |
- 4,300
- total depth, ft
- 2
- permits on file
- May 2, 2006
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 134K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2007 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Aug 28, 1982
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 |
|---|---|---|---|---|---|---|
| Keith G-8-226452 | Stephens County Regular (Gas) | Ray Herring Operating Co., LLC | 1 | 0 | 134K | Mar 2007 – Jul 2026 |
Gas, mcf lease total
Last 12 months 3,759 · prior 12 4,052(-7%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Herring, RayMar 2007 → Jun 2014
- 2Ray Herring EstateJul 2014 → Mar 2016
- 3Ray Herring Operating Co., LLCApr 2016 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 618024-99 | Reenter | Herring, Ray | Apr 21, 2006 | May 2, 2006 | — | 4,300 |
| 161798-99 | Drill | Herring, Ray | May 25, 1982 | May 25, 1982 | — | 4,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-226452 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,390 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Caddo | 3,330 | -1,940 |
| Marble Falls | 3,950 | -2,560 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,956 | 3,968 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 205 | 12.25 | 155 S |
| 4.5 | 4,050 | 7.875 | 150 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 18, 2007 | Apr 17, 2007 | Yes |
| 00 | May 4, 2007 | — | — |
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-429-33324 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-429-33324 → 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/42933324, documented in the API reference.