WELL · 42-235-10206 · DISTRICT 7

Winterbotham, J. M. #5

N

Irion County  · Vertical

Winterbotham, J. M. #5 (API 42-235-10206) is a permitted well in Irion County filed by Txp, Incorporated; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1986 and 1992, permitted to 6,613 ft.

Completion filings report 3 formation tops, including San Andres, Wolfcamp, Canyon.

Its 2 leases have reported 4.65K barrels of oil and 322K mcf of gas since January 1993, last reporting in July 2026. The leases carry 5 wells, so these are lease totals, not this well alone.

Operator of record

TXP, Incorporated

Based in
San Angelo, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jul 13, 2026
Permits on file
419
Phone
(325) 944-9894

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsOXY USA Inc.through Mar 2017
Latest permitTXP, IncorporatedApr 10, 1992
6,613
total depth, ft
2
permits on file
Apr 10, 1992
last permit issued
—
completed
4.65K
cumulative oil, bbl
322K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Winterbotham, J. M. G-9-141326Brooks (Canyon K)Hilcorp Energy Company10129KJan 1993 – Jul 2026
Winterbotham, J. M. O-9-4509Dove Creek (Canyon -B-)Hilcorp Energy Company44.65K193KJan 1993 – Jul 2026

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.

  1. 1TXP, IncorporatedJan 1993 → Dec 2003
  2. 2Pogo Producing CompanyJan 2004 → Jan 2008
  3. 3Pogo Producing Company LLCFeb 2008 → Feb 2008
  4. 4OXY USA Inc.Mar 2008 → Mar 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
398209-99RecompletionTXP, IncorporatedApr 8, 1992Apr 10, 1992Apr 20, 19926,613
294918-99RecompletionTexaco Producing Inc.Dec 5, 1985Jan 9, 1986—6,613

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-141326————
—— O-9-4509————

Formation tops

As filed on W-2/G-1. Subsea from 2,159 ft elevation.Download CSV →

FormationMD ftSubsea
San Andres9501,209
Wolfcamp4,990-2,831
CanyonCANYON K5,675-3,516
CanyonCANYON B6,224-4,065

Perforations

Perforated and open-hole intervals.

FromToType
5,6755,820Perforated
—6,319Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7544515.5225 S
3.56,095590 S
5.56,6498.625500 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 13, 1992May 15, 1992Yes
00May 26, 1992——
00Jan 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.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. 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/23510206, documented in the API reference.