WELL · 42-215-00042 · DISTRICT 4

Goldston, W. L. et AL #11

N

Hidalgo County  · Vertical

Goldston, W. L. ET AL #11 (API 42-215-00042) is a permitted well in Hidalgo County filed by Wynn-Crosby Energy, Inc.; no completion report is on file yet.

The RRC has issued 4 drilling permits between 1978 and 1996, permitted to 7,265 ft.

Completion filings report 7 formation tops, including Mf-22, D, E, F.

Operator of record

Wynn-Crosby Energy, Inc.

Houston, TX · P-5 Y, filed Nov 5, 2004 · 117 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsMilagro Exploration, LLCthrough May 2009
Latest permitWynn-Crosby Energy, Inc.Dec 4, 1996
7,265
total depth, ft
4
permits on file
Dec 4, 1996
last permit issued
—
completed
0
cumulative oil, bbl
574K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2010

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Goldston, W. L. et AL G-4-162067Los Indios, W. (MF-22)Milagro Exploration, LLC10574KFeb 1997 – Mar 2010
Goldston, W.L. G-4-128554Los Indios (D)Wynn-Crosby Energy, Inc.100Jan 1993 – Feb 1997

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. 1Wynn-Crosby Energy, Inc.Feb 1997 → May 2005
  2. 2Petrohawk Operating CompanyJun 2005 → Oct 2007
  3. 3Milagro Exploration, LLCMar 2008 → May 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
455888-99RecompletionWynn-Crosby Energy, Inc.Dec 4, 1996Dec 4, 1996Dec 2, 19967,265
427432-99RecompletionPg&e Resources CompanyAug 26, 1994Aug 31, 1994—7,265
350635-99RecompletionUnion Pacific Resources CompanyAug 29, 1988Aug 29, 1988—7,265
37040-99RecompletionChamplin Petroleum Co.Nov 16, 1978Nov 16, 1978—7,265

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-128554————
—— G-4-162067————

Formation tops

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

FormationMD ftSubsea
MF-225,004-4,898
D5,870-5,764
E5,946-5,840
F5,986-5,880
J6,522-6,416
K6,695-6,589
M6,834-6,728

Perforations

Perforated and open-hole intervals.

FromToType
5,0045,028Perforated
5,9495,968Perforated
6,6956,704Perforated
6,8346,867Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,19515485 S
10.751,195—485 S
26,745——
5.56,9608.75600 S
5.56,960——

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 23, 1997Mar 20, 1997Yes
00Mar 26, 1997——
00Nov 22, 1988Oct 5, 1988Yes
00Oct 21, 1988——
00Jan 12, 1984Mar 23, 1979—
00Jan 12, 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.

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