WELL · 42-399-34428 · DISTRICT 7
Rufus Allen G #1
Runnels County · Winters SW. (Palo Pinto) field · Vertical
Rufus Allen G #1 (API 42-399-34428) is a plugged well in Runnels County, plugged October 10, 1997, last operated by Western Pride Resources Inc..
The RRC has issued one drilling permit, issued February 28, 1996, permitted to 4,900 ft.
Completion filings report 2 formation tops, including Palo Pinto, Goen.
Its lease has reported 462 barrels of oil since July 1996, last reporting in August 2003.
Operator of record
Jacksboro, TX · P-5 Y, filed Dec 3, 2010 · 17 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Western Pride Resources Inc. |
| Production reports | Western Pride Resources, Inc.through Jan 1997 |
| Latest permit | Western Pride Resources, Inc.Feb 28, 1996 |
- 4,900
- total depth, ft
- 1
- permits on file
- Feb 28, 1996
- last permit issued
- Jul 20, 1996
- completed
- 462
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 1996 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 20, 1996
- Shut in
- —
- Plugged
- Oct 10, 1997
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 |
|---|---|---|---|---|---|---|
| Rufus, Allen G O-9-14428 | Winters, SW. (Palo Pinto) | Western Pride Resources, Inc. | 1 | 462 | 0 | Jul 1996 – Aug 2003 |
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.
- 1Western Pride Resources, Inc.Aug 1996 → Jan 1997
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 445274-99 | Drill | Western Pride Resources, Inc. | Feb 28, 1996 | Feb 28, 1996 | Mar 13, 1996 | 4,900 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-14428 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,828 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Palo Pinto | 3,600 | -1,772 |
| Goen | 4,077 | -2,249 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,692 | 3,702 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 153 | 11 | 65 S |
| 4.5 | 4,125 | 7.875 | 400 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 | Sep 19, 1996 | Aug 7, 1996 | Yes |
| 00 | Sep 5, 1996 | — | — |
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-399-34428 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-399-34428 → 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/39934428, documented in the API reference.