TEXAS · WELLS · CALHOUN COUNTY · G-2-126586 LEASE · API 42-057-31356 · DISTRICT 02

State Tract 27 #3

Plugged

Calhoun County · Lavaca Bay (F-31) field  · Vertical

State Tract 27 #3 (API 42-057-31356) is a plugged well in Calhoun County, plugged September 4, 1992, last operated by Neumin Production Company.

The RRC has issued 3 drilling permits between 1984 and 1988, permitted to 12,232 ft.

Completion filings report 6 formation tops, including F-30, F-31, F-36, F-37.

Operator of record

Neumin Production Company

Based in
Point Comfort, TX
P-5 status
Delinquent (D)
P-5 last filed
Aug 9, 2023
Permits on file
380
Phone
(361) 987-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNeumin Production Company
Production reportsnone
Latest permitNeumin Production CompanyFeb 22, 1988
12,232
total depth, ft
3
permits on file
Feb 22, 1988
last permit issued
Jan 27, 1988
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 27, 1988
Shut in
—
Plugged
Sep 4, 1992

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
— G-2-126586——000—

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
342814-99RecompletionNeumin Production CompanyFeb 18, 1988Feb 22, 1988—12,232
297954-99RecompletionNeumin Production CompanyFeb 3, 1986Feb 19, 1986—12,232
261782-99DrillNeumin Production CompanyJul 12, 1985Dec 17, 1984Apr 28, 198512,232

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 27, 1988State Tract 27 G-2-126586Lavaca Bay (F-31)Neumin Production CompanyPlugged—
Jan 22, 1986State Tract 27 G-2-120175Lavaca Bay (F-43)Neumin Production CompanyPlugged—
Jun 19, 1985State Tract 27 G-2-117662Lavaca Bay (F-40-B)Neumin Production CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
F-309,686-9,685
F-319,686-9,685
F-3610,194-10,193
F-3710,374-10,373
F-40B10,640-10,639
F-4310,850-10,849

Perforations

Perforated and open-hole intervals.

FromToType
9,6889,696Perforated
10,64010,658Perforated
10,85010,865Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2074——
13.3752,50017.51,400 S
9.6259,39312.25670 S
511,2108.5802 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Apr 6, 1988Feb 19, 1988Yes
00Mar 15, 1988——
00Mar 17, 1986Feb 14, 1986Yes
00Mar 12, 1986——
00Sep 11, 1985Jul 12, 1985—
00Aug 31, 1985——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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