WELL · 42-311-02029 · DISTRICT 1

Gouger H. E. Fee NCT-9 #7

N

McMullen County · Campana South field  · Vertical

Gouger H. E. Fee Nct-9 #7 (API 42-311-02029) is a permitted well in Mcmullen County filed by Texaco Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued June 27, 1989, permitted to 3,009 ft.

It was permitted by Texaco Inc. and has since transferred to Simray Oil & Gas Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Frio, Jackson, Yegua.

Operator of record

Simray Oil & Gas Inc.

Permitted by Texaco Inc.; the EWA schedule now lists a different operator.

Richardson, TX · P-5 Y, filed Oct 8, 2004 · 16 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSimray Oil & Gas Inc.
Production reportsProline Energy Resources Incthrough Apr 2026
Latest permitTexaco Inc.Jun 27, 1989

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

3,009
total depth, ft
1
permits on file
Jun 27, 1989
last permit issued
—
completed
0
cumulative oil, bbl
249K
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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gouger Gas Unit NO 4 O/A G-1-132133Campana, South (1500)Proline Energy Resources Inc10249KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 48 · prior 12 62(-23%)

05001K1.5K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Texaco E & P Inc.Jan 1993 → Mar 1995
  2. 2Simray Oil & Gas, Inc.Dec 1996 → Jul 2002
  3. 3Bluestone Natural Resources, LLCMar 2011 → Jun 2011
  4. 4Columbus Energy, LLCJul 2011 → Jan 2024
  5. 5Fourth Floor Operating LLCMar 2019 → Apr 2022
  6. 6Proline Energy Resources IncMar 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
360749-99RecompletionTexaco Inc.Jun 23, 1989Jun 27, 1989—3,009

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-132133————

Formation tops

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

FormationMD ftSubsea
FrioLOWER FRIO1,750-1,245
JacksonTOP OF JACKSON1,875-1,370
YeguaTOP OF YEGUA2,900-2,395

Perforations

Perforated and open-hole intervals.

FromToType
1,4901,502Perforated
—3,006Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62526112.2580 S
4.53,0097.875210 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
00Dec 7, 1989Sep 27, 1989Yes
00Nov 8, 1989——
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). 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/31102029, documented in the API reference.