WELL · 42-301-31088 · DISTRICT 8

Red Fish 7 #1

Plugged

Loving County · Red Bluff (Wolfcamp) field  · Vertical

Red Fish 7 #1 (API 42-301-31088) is a plugged well in Loving County, plugged October 29, 2014, last operated by Oxy USA Inc..

The RRC has issued one drilling permit (amended once), issued October 7, 1997, permitted to 12,400 ft.

It was permitted by Pogo Producing CO. and has since transferred to Oxy USA Inc. on the wellbore schedule.

Completion filings report 6 formation tops, including Delaware, Bell Canyon, Cherry Canyon, Brushy Canyon.

Operator of record

OXY USA Inc.

Permitted by Pogo Producing Co.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jan 26, 2026
Permits on file
3,316
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOXY USA Inc.
Production reportsOXY USA Inc.through Nov 2010
Latest permitPogo Producing Co.Oct 27, 1997

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

12,400
total depth, ft
2
permits on file
Oct 27, 1997
last permit issued
Mar 1, 1998
completed
0
cumulative oil, bbl
458K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1998 THROUGH Oct 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 1, 1998
Shut in
—
Plugged
Oct 29, 2014

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Red Fish 7 G-10-167916Red Bluff (Wolfcamp)OXY USA Inc.10458KFeb 1998 – Oct 2014

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. 1Pogo Producing CompanyFeb 1998 → Jan 2008
  2. 2Pogo Producing Company LLCFeb 2008 → Feb 2008
  3. 3OXY USA Inc.Mar 2008 → Nov 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
468054-99DrillPogo Producing Co.Sep 25, 1997Oct 27, 1997—12,400
468054-98DrillPogo Producing Co.Oct 7, 1997Oct 7, 1997Nov 10, 199712,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-167916————

Formation tops

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

FormationMD ftSubsea
DelawareDELAWARE LIME3,238-312
Bell Canyon3,258-332
Cherry Canyon4,176-1,250
Brushy Canyon5,330-2,404
Bone SpringBONE SPRINGS7,088-4,162
Wolfcamp10,278-7,352

Perforations

Perforated and open-hole intervals.

FromToType
11,63011,660Perforated
11,88011,918Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,03317.5950 S
711,4068.5700 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
00Jun 24, 1998Mar 20, 1998Yes
00May 12, 1998——

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/30131088, documented in the API reference.