TEXAS · WELLS · WARD COUNTY · PITZER 8 LEASE · API 42-475-36294 · DISTRICT 7B
Pitzer 8 #3H
Ward County · Phantom (Wolfcamp) field · Shut In · Horizontal
Pitzer 8 #3H (API 42-475-36294) is a horizontal well in Ward County operated by Apache Corporation, completed February 9, 2013 and listed as shut in on the RRC schedule, shut in October 1, 2023.
The RRC has issued one drilling permit, issued November 14, 2012, permitted to 11,251 ft.
It was permitted by Cimarex Energy CO. and has since transferred to Apache Corporation on the wellbore schedule.
Completion filings report 3 formation tops, including Brushy Canyon, Bone Spring, Wolfcamp.
Its lease has reported 808K barrels of oil and 920K mcf of gas since July 2011, last reporting volume in August 2025. The lease carries 3 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Cimarex Energy Co.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Dec 3, 2025
- Permits on file
- 9,758
- Phone
- (713) 954-5500
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Apache Corporation |
| Production reports | Apache Corporationthrough Aug 2025 |
| Latest permit | Cimarex Energy Co.Nov 14, 2012 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 11,251
- total depth, ft
- 1
- permits on file
- Nov 14, 2012
- last permit issued
- Feb 9, 2013
- completed
- 808K
- cumulative oil, bbl
- 920K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2011 THROUGH Aug 2025
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Feb 9, 2013
- Shut in
- Oct 1, 2023
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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; they carry 3 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Pitzer 8 O-10-42260 | Phantom (Wolfcamp) | Apache Corporation | 3 | 808K | 920K | Jul 2011 – Aug 2025 |
Oil, barrels lease total
Last 12 months 1,062 · prior 12 7,957(-87%)
Gas, mcf lease total
Last 12 months 35 · prior 12 3,663(-99%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Cimarex Energy Co.Jul 2011 → Aug 2018
- 2Callon Petroleum Operating CoSep 2018 → Jul 2024
- 3Apache CorporationAug 2024 → Aug 2025
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 751096-99 | Drill | Cimarex Energy Co. | Nov 7, 2012 | Nov 14, 2012 | Dec 13, 2012 | 11,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Feb 9, 2013 | Pitzer 8 O-10-42260 | Phantom (Wolfcamp) | Apache Corporation | Shut In · shut in Oct 1, 2023 | 11,251 |
Formation tops
As filed on W-2/G-1. Subsea from 2,608 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Brushy Canyon | 7,220 | -4,612 |
| Bone SpringFIRST BONE SPRING SAND | 9,350 | -6,742 |
| Wolfcamp | 11,090 | -8,482 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 11,500 | 15,876 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10 | 5,130 | 12.25 | 1,432 S |
| 9.625 | 5,130 | 12.25 | 635 S |
| 7 | 10,860 | 8.75 | 712 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. 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 29, 2014 | Feb 25, 2013 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Feb 2, 2016. Density, Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| NEUTRON/DENSITY POROSITYSpans Brushy Canyon, Bone Spring, Wolfcamp | TIFF | 200 to 12,084 | Feb 2, 2016run Dec 27, 2012 | 5.68 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-475-36294 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-475-36294 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/47536294, documented in the API reference.