WELL · 42-409-01316 · DISTRICT 4

Schmidt, David et AL #4

N

San Patricio County  · Vertical

Schmidt, David ET AL #4 (API 42-409-01316) is a former disposal or injection well in San Patricio County, last operated by Haas, C. F. Oil & Gas Inc.; its UIC permit is no longer active.

The RRC has issued one drilling permit, issued April 16, 1987, permitted to 5,000 ft.

Completion filings report one formation top, including Taft.

Its lease has reported 5.61K barrels of oil and 383 mcf of gas since January 1993, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

Haas, C. F. Oil & Gas Inc.

Corpus Chrsti, TX · P-5 Y, filed Oct 2, 2009 · 35 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsGreen Exploration Companythrough Aug 2017
Latest permitHaas, C. F. Oil & Gas Inc.Apr 16, 1987
5,000
total depth, ft
1
permits on file
Apr 16, 1987
last permit issued
—
completed
5.61K
cumulative oil, bbl
383
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; they carry 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Taft Gin and Seed Co A O-4-7262Taft (4300)Green Exploration Company75.61K383Jan 1993 – 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. 1Blackland Oil & GasJan 1993 → Jul 1994
  2. 2Green Exploration CompanyJan 2011 → Aug 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
328932-99RecompletionHaas, C. F. Oil & Gas Inc.Apr 13, 1987Apr 16, 1987—5,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-4-7262————

Formation tops

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

FormationMD ftSubsea
Taft4,300-4,256

Perforations

Perforated and open-hole intervals.

FromToType
4,3544,358Perforated
—3,990Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7563512.25250 S
10.75635——
74,9058.875250 S
74,905——

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
00Apr 25, 2013Apr 16, 2013—
00Jun 9, 1987Apr 13, 1987Yes
00May 21, 1987——
00May 25, 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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

550K
bbl, last 12 reported months
550K
bbl, all reported
Feb 1984
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000004673H-1 InjectionPlugged Apr 2, 20203,0008004,080–4,470

MONTHLY INJECTED, BBL · H-10 · LAST 4 REPORTED MONTHS

Last 12 months 550,000

050K100K150K1984

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