TEXAS · WELLS · LEE COUNTY · API 42-287-31141 · DISTRICT 03

Stork #3

Plugged

Lee County · Giddings (Austin Chalk-3) field  · Vertical

Fields on the latest permit · any of 3
Giddings (Austin Chalk-3) · Giddings (Buda) · Giddings (Austin Chalk, Gas)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Stork #3 (API 42-287-31141) is a plugged well in Lee County, plugged October 28, 1985, last operated by Union Pacific Resources Company.

The RRC has issued one drilling permit, issued December 31, 1981, permitted to 9,700 ft.

It was permitted by Santa FE - Windsor Producing CO. and has since transferred to Union Pacific Resources Company on the wellbore schedule.

Operator of record

Union Pacific Resources Company

Permitted by Santa FE - Windsor Producing Co.; the EWA schedule now lists a different operator.

Based in
Fort Worth, TX
P-5 status
Inactive (I)
P-5 last filed
May 2, 2000
Permits on file
5,638
Phone
(817) 321-7424

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUnion Pacific Resources Company
Production reportsnone
Latest permitSanta FE - Windsor Producing Co.Dec 31, 1981

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

9,700
total depth, ft
1
permits on file
Dec 31, 1981
last permit issued
Feb 17, 1982
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 17, 1982
Shut in
—
Plugged
Oct 28, 1985

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Wells named Stork

Union Pacific Resources Company's other wells filed under this lease name in Lee County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
147762-99DrillSanta FE - Windsor Producing Co.Dec 31, 1981Dec 31, 1981—9,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 17, 1982Stork O-3-15264Giddings (Austin Chalk-3)Union Pacific Resources CompanyPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
8,7328,935Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,22112.25950 S
2.3758,628——
5.59,2758.75500 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
00Jan 12, 1984Mar 1, 1982—

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