WELL · 42-149-32649 · DISTRICT 3

Schaefer Oil Unit #1

Plugged

Fayette County · Giddings (Austin Chalk-3) field  · Horizontal

Schaefer Oil Unit #1 (API 42-149-32649) is a plugged horizontal well in Fayette County, plugged July 28, 1995, last operated by AL-TX Operating Inc..

The RRC has issued one drilling permit (amended once), issued June 25, 1992, permitted to 9,100 ft.

It was permitted by Tana Oil And Gas Corporation and has since transferred to AL-TX Operating Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Taylor, Pecan Gap, Austin Chalk.

Its lease has reported 38.9K barrels of oil and 73.6K mcf of gas since January 1993, last reporting in August 1995.

Operator of record

AL-TX Operating Inc.

Permitted by Tana Oil and Gas Corporation; the EWA schedule now lists a different operator.

Plum, TX · P-5 Y, filed Nov 6, 1998

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAL-TX Operating Inc.
Production reportsTana Oil and Gas Corporationthrough Mar 1995
Latest permitTana Oil and Gas CorporationJun 25, 1992

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

9,100
total depth, ft
2
permits on file
Jun 25, 1992
last permit issued
Aug 10, 1992
completed
38.9K
cumulative oil, bbl
73.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 10, 1992
Shut in
—
Plugged
Jul 28, 1995

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
Schaefer Oil Unit O-3-21799Giddings (Austin Chalk-3)AL-TX Operating Inc.138.9K73.6KJan 1993 – Aug 1995

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. 1Tana Oil and Gas CorporationJan 1993 → Mar 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
400369-98DrillTana Oil and Gas CorporationOct 15, 1992Jun 25, 1992—9,100
400369-99DrillTana Oil and Gas CorporationJun 19, 1992Jun 25, 1992Jun 25, 19929,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-21799————

Formation tops

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

FormationMD ftSubsea
Taylor7,000-6,722
Pecan Gap7,950-7,672
Austin Chalk8,250-7,972

Perforations

Perforated and open-hole intervals.

FromToType
8,8339,092Perforated
8,86612,602Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,84712.25985 S
78,5158.75320 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 22, 1992Sep 4, 1992Yes
00Dec 17, 1992——

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