TEXAS · WELLS · YOAKUM COUNTY · API 42-501-01605 · DISTRICT 7B
Ownby San Andres Unit #39W
Yoakum County · Ownby field · Vertical
Ownby San Andres Unit #39W (API 42-501-01605) is a plugged well in Yoakum County, plugged April 7, 1982, last operated by Occidental Permian Ltd..
The RRC has issued one drilling permit, issued February 16, 1994, permitted to 5,490 ft.
It was permitted by Shell Western E&P Inc. and has since transferred to Occidental Permian Ltd. on the wellbore schedule.
Operator of record
Permitted by Shell Western E&P Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Feb 2, 2026
- Permits on file
- 6,251
- Phone
- (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Occidental Permian Ltd. |
| Production reports | none |
| Latest permit | Shell Western E&P Inc.Feb 16, 1994 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,490
- total depth, ft
- 1
- permits on file
- Feb 16, 1994
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Apr 7, 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.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 420946-99 | Reenter | Shell Western E&P Inc. | Feb 7, 1994 | Feb 16, 1994 | — | 5,490 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | Ownby San Andres Unit O-11-60739 | Ownby | Occidental Permian Ltd. | Plugged | — |
| — | Ownby E. -A- O-11-4594 | Ownby | Great Western Drilling Company | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,402 | 5,471 | Perforated |
| — | 5,350 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 255 | — | — |
| 5.5 | 5,240 | 4.75 | — |
| 5.5 | 5,250 | — | — |
| 3.5 | 5,489 | — | — |
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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Aug 27, 1945 | — |
| 00 | Jan 12, 1984 | — | — |
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-501-01605 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-501-01605 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- —
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000123590 | H-1 Injection | Plugged Apr 22, 1982 | 500 | 1,500 | 5,295–0 |
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/50101605, documented in the API reference.