WELL · 42-311-02116 · DISTRICT 1
Gouger Gas Unit No. 4 O/A #3
McMullen County · Campana South (1500) field · Vertical
Gouger Gas Unit NO. 4 O/A #3 (API 42-311-02116) is a plugged well in Mcmullen County, plugged December 19, 1997, last operated by Simray Oil & Gas Inc..
The RRC has issued one drilling permit, issued October 9, 1989, permitted to 3,014 ft.
It was permitted by Texaco Inc. and has since transferred to Simray Oil & Gas Inc. on the wellbore schedule.
Operator of record
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 schedule | Simray Oil & Gas Inc. |
| Production reports | none |
| Latest permit | Texaco Inc.Oct 9, 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,014
- total depth, ft
- 1
- permits on file
- Oct 9, 1989
- last permit issued
- Dec 31, 1989
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Dec 31, 1989
- Shut in
- —
- Plugged
- Dec 19, 1997
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 8 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Gouger, H. E. Fee NCT-9 O-1-2507 | Campana, South | Simray Oil & Gas, Inc. | 7 | 0 | 0 | Jan 1993 – Aug 2003 |
| Gouger Gas Unit No. 4 O/A G-1-137945 | Campana, South (1500) | Simray Oil & Gas, Inc. | 1 | 0 | 0 | Jan 1993 – Dec 1997 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 364755-99 | Recompletion | Texaco Inc. | Oct 5, 1989 | Oct 9, 1989 | — | 3,014 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-1-137945 | — | — | — | — |
| — | — O-1-2507 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,518 | 1,530 | Perforated |
| — | 3,012 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 293 | 12.25 | 85 S |
| 4.5 | 3,014 | 7.25 | 162 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, 1991 | Jan 17, 1990 | Yes |
| 00 | May 3, 1991 | — | — |
| 00 | Jan 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.
- Wellbore filings for 42-311-02116 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-311-02116 → 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/31102116, documented in the API reference.