WELL · 42-025-32602 · DISTRICT 2
Savage #1
Bee County · Poesta Creek (3800) field · Vertical
Savage #1 (API 42-025-32602) is a plugged well in Bee County, plugged May 26, 1993, last operated by Yuma Petroleum Company.
The RRC has issued one drilling permit (amended once), issued December 7, 1990, permitted to 6,000 ft.
Completion filings report 3 formation tops, including Miocene (undifferentiated), Frio, Vicksburg.
Operator of record
Houston, TX · P-5 Y, filed Dec 6, 2002 · 65 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Yuma Petroleum Company |
| Production reports | Yuma Petroleum Companythrough Mar 1993 |
| Latest permit | Yuma Petroleum CompanyDec 7, 1990 |
- 6,000
- total depth, ft
- 2
- permits on file
- Dec 7, 1990
- last permit issued
- Oct 15, 1992
- completed
- 0
- cumulative oil, bbl
- 371
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 1993
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 15, 1992
- Shut in
- —
- Plugged
- May 26, 1993
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 |
|---|---|---|---|---|---|---|
| Savage G-2-144192 | Poesta Creek (3800) | Yuma Petroleum Company | 1 | 0 | 371 | Jan 1993 – May 1993 |
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.
- 1Yuma Petroleum CompanyJan 1993 → Mar 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 381583-98 | Drill | Yuma Petroleum Company | Nov 12, 1992 | Dec 7, 1990 | — | 6,000 |
| 381583-99 | Drill | Yuma Petroleum Company | Nov 27, 1990 | Dec 7, 1990 | Sep 26, 1992 | 6,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-144192 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 206 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 1,765 | -1,559 |
| Frio | 2,440 | -2,234 |
| Vicksburg | 3,810 | -3,604 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,135 | 4,136 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 472 | 12.25 | 175 S |
| 4.5 | 4,331 | 7.875 | 940 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 9, 1993 | Nov 16, 1992 | Yes |
| 00 | Mar 9, 1993 | — | — |
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-025-32602 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-32602 → 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/02532602, documented in the API reference.