WELL · 42-175-31877 · DISTRICT 2

Shirley Brothers #2

Plugged

Goliad County · Blanconia N. (4820) field  · Vertical

Shirley Brothers #2 (API 42-175-31877) is a plugged well in Goliad County, plugged August 9, 2000, last operated by Lytle Creek Operating Inc..

The RRC has issued one drilling permit, issued May 22, 1984, permitted to 5,500 ft.

It was permitted by Thompson, John R. Operating, Inc and has since transferred to Lytle Creek Operating Inc. on the wellbore schedule.

Completion filings report one formation top, including Vicksburg.

Its lease has reported 39.3K barrels of oil and 133K mcf of gas since January 1993, last reporting in November 2000. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Lytle Creek Operating Inc.

Permitted by Thompson, John R. Operating, Inc; the EWA schedule now lists a different operator.

Based in
Abilene, TX
P-5 status
Delinquent (D)
P-5 last filed
May 27, 2016
Permits on file
81
Phone
(325) 665-4461

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLytle Creek Operating Inc.
Production reportsLytle Creek Operating, Inc.through Apr 1999
Latest permitThompson, John R. Operating, IncMay 22, 1984

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

5,500
total depth, ft
1
permits on file
May 22, 1984
last permit issued
Mar 1, 1985
completed
39.3K
cumulative oil, bbl
133K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2000

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 1, 1985
Shut in
—
Plugged
Aug 9, 2000

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 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Shirley Brothers O-2-6703Blanconia, N. (4820)Lytle Creek Operating, Inc.439.3K133KJan 1993 – Nov 2000

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. 1Lytle Creek Operating, Inc.Jan 1993 → Apr 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
239736-99DrillThompson, John R. Operating, IncSep 4, 1984May 22, 1984Sep 19, 19845,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-6703————

Formation tops

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

FormationMD ftSubsea
Vicksburg5,190-5,092

Perforations

Perforated and open-hole intervals.

FromToType
4,8204,827Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550112.25225 S
4.55,0107.8751,040 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
00Mar 29, 1985Mar 15, 1985—
00Mar 26, 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 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/17531877, documented in the API reference.