WELL · 42-173-32133 · DISTRICT 8
Glasscock Z Fee #1
Glasscock County · Powell (Clearfork) field · Vertical
Glasscock Z Fee #1 (API 42-173-32133) is a plugged well in Glasscock County, plugged April 29, 2000, last operated by Texaco E & P Inc..
The RRC has issued 2 drilling permits between 1990 and 1999, permitted to 8,700 ft.
Completion filings report one formation top, including Wolfcamp.
Its 2 leases have reported 245 barrels of oil and 110 mcf of gas since October 1999, last reporting in August 2000.
Operator of record
Houston, TX · P-5 Y, filed Oct 4, 2025 · 3,332 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Texaco E & P Inc. |
| Production reports | Texaco E & P Inc.through Dec 1999 |
| Latest permit | Texaco E & P Inc.Sep 23, 1999 |
- 8,700
- total depth, ft
- 2
- permits on file
- Sep 23, 1999
- last permit issued
- —
- completed
- 245
- cumulative oil, bbl
- 110
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 1999 THROUGH Aug 2000
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Apr 29, 2000
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Glasscock 'Z' Fee O-10-36281 | Powell (Clearfork) | Texaco E & P Inc. | 1 | 245 | 110 | Oct 1999 – Aug 2000 |
| — O-10-32660 | — | — | 0 | 0 | 0 | — |
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.
- 1Texaco E & P Inc.Oct 1999 → Dec 1999
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 487817-99 | Reenter | Texaco E & P Inc. | Sep 22, 1999 | Sep 23, 1999 | — | 7,750 |
| 373455-99 | Drill | Texaco Inc. | May 16, 1990 | May 18, 1990 | Jun 3, 1990 | 8,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-10-32660 | — | — | — | — |
| — | — O-10-36281 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,587 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Wolfcamp | 8,534 | -5,947 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 350 | 17 | 450 S |
| 9.625 | 3,500 | 12.25 | 1,200 S |
| 7 | 8,400 | 8.75 | 480 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 15, 2000 | — | — |
| 00 | Sep 18, 1990 | Aug 8, 1990 | Yes |
| 00 | Sep 5, 1990 | — | — |
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-173-32133 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-173-32133 → 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/17332133, documented in the API reference.