WELL · 42-503-39690 · DISTRICT 9
Peterson #1
Young County · Young County Regular field · Vertical
Peterson #1 (API 42-503-39690) is a plugged well in Young County, plugged March 2, 1992, last operated by Peterson & Wilton.
The RRC has issued 2 drilling permits (amended once) between 1987 and 1990, permitted to 5,500 ft.
Completion filings report 7 formation tops, including Gunsight, Weir Sand, Strawn, Caddo.
Operator of record
Loving, TX · P-5 Y, filed Jan 7, 1994 · 2 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Peterson & Wilton |
| Production reports | none |
| Latest permit | Peterson & WiltonNov 19, 1990 |
- 5,500
- total depth, ft
- 3
- permits on file
- Nov 19, 1990
- last permit issued
- Nov 19, 1990
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 19, 1990
- Shut in
- —
- Plugged
- Mar 2, 1992
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 2 leases this well is completed on; this well is the only one on it.Why →
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 381210-99 | Recompletion | Peterson & Wilton | Nov 19, 1990 | Nov 19, 1990 | Nov 19, 1990 | 3,600 |
| 339507-98 | Drill | Ranger Operating Co. | Feb 8, 1988 | Dec 7, 1987 | — | 5,500 |
| 339507-99 | Drill | Ranger Operating Co. | Dec 1, 1987 | Dec 7, 1987 | — | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-26948 | — | — | — | — |
| — | — O-13-27950 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,106 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Gunsight | 558 | 548 |
| Weir Sand | 2,670 | -1,564 |
| StrawnSTRAWN SAND | 3,492 | -2,386 |
| Caddo | 4,296 | -3,190 |
| Marble Falls | 4,762 | -3,656 |
| BarnettBARNETT SHALE | 5,134 | -4,028 |
| Mississippian | 5,184 | -4,078 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,492 | 3,495 | Perforated |
| 5,183 | 8,208 | Open hole |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 527 | 12.25 | 280 S |
| 8.625 | 527 | — | 280 S |
| 4.5 | 3,636 | 7.875 | 190 S |
| 5.5 | 5,183 | 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 | Apr 15, 1991 | Jan 8, 1991 | Yes |
| 00 | Mar 25, 1991 | Feb 8, 1988 | Yes |
| 00 | Mar 11, 1988 | Feb 8, 1988 | Yes |
| 00 | Feb 12, 1988 | — | — |
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-503-39690 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-503-39690 → 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/50339690, documented in the API reference.