WELL · 42-071-32178 · DISTRICT 3

State Tract 1-4A Unit #1

Plugged

Chambers County · Fishers Reef (FB C 9800) field  · Directional

State Tract 1-4a Unit #1 (API 42-071-32178) is a plugged well in Chambers County, plugged November 15, 2023, last operated by Galveston Bay Operating CO LLC.

The RRC has issued one drilling permit, issued May 22, 2000, permitted to 11,500 ft.

It was permitted by Davis Petroleum Corp. and has since transferred to Galveston Bay Operating CO LLC on the wellbore schedule.

Completion filings report 3 formation tops, including F-15 (Banfield), Tex 2, Lox B.

Operator of record

Galveston Bay Operating Co LLC

Permitted by Davis Petroleum Corp.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Feb 4, 2026 · 5 permits on file · (828) 817-7260

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGalveston Bay Operating Co LLC
Production reportsGalveston Bay Operating Co LLCthrough Jun 2021
Latest permitDavis Petroleum Corp.May 22, 2000

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

11,500
total depth, ft
1
permits on file
May 22, 2000
last permit issued
Oct 20, 2000
completed
0
cumulative oil, bbl
2.4M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 20, 2000
Shut in
—
Plugged
Nov 15, 2023

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
State Tract 1-4A Unit G-3-183428Fishers Reef (FB C 9800)Galveston Bay Operating Co LLC102.4MOct 2000 – 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. 1Vintage Petroleum, Inc.Nov 2000 → Nov 2002
  2. 2Masters Oil & Gas, LLCDec 2002 → Sep 2006
  3. 3Tekoil and Gas Gulf Coast, LLCOct 2006 → Dec 2006
  4. 4Galveston Bay Operating Co LLCApr 2020 → Jun 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
495273-99DrillDavis Petroleum Corp.May 19, 2000May 22, 2000Aug 7, 200011,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-183428————

Formation tops

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

FormationMD ftSubsea
F-15 (Banfield)9,005-8,965
Tex 29,690-9,650
Lox B10,425-10,385

Perforations

Perforated and open-hole intervals.

FromToType
10,19010,228Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,70014.751,815 S
7.6259,7679.875885 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
00Aug 29, 2001Dec 22, 2000Yes
00Aug 2, 2001——

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