TEXAS · WELLS · WEBB COUNTY · WILLIAMSON, STANLEY H. LEASE · API 42-479-35578 · DISTRICT 04

Williamson Stanley H. #2

Plugged

Webb County · Cinco Compadres (Lobo) field  · Vertical

Williamson Stanley H. #2 (API 42-479-35578) is a plugged well in Webb County, plugged March 15, 2002, last operated by Eog Resources Inc..

The RRC has issued 2 drilling permits (amended 4 times) between 1992 and 1993, permitted to 8,900 ft.

It was permitted by Amoco Production Company and has since transferred to Eog Resources Inc. on the wellbore schedule.

Operator of record

EOG Resources Inc.

Permitted by Amoco Production Company; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
16,348
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsEnron Oil & Gas Companythrough Jan 1999
Latest permitAmoco Production CompanyMay 18, 1993
8,900
total depth, ft
6
permits on file
May 18, 1993
last permit issued
Feb 9, 1993
completed
0
cumulative oil, bbl
211K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 1993 THROUGH Mar 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 9, 1993
Shut in
—
Plugged
Mar 15, 2002

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
Williamson, Stanley H. G-4-144855Cinco Compadres (Lobo)EOG Resources, Inc.10211KFeb 1993 – Mar 2002

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. 1Amoco Production CompanyFeb 1993 → Oct 1996
  2. 2Conoco Inc.Dec 1996 → Feb 1998
  3. 3Enron Oil & Gas CompanyMar 1998 → Jan 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
411869-99RecompletionAmoco Production CompanyMay 18, 1993May 18, 1993—8,900
402812-95Field transferAmoco Production CompanyMay 18, 1993Sep 2, 1992—8,900
402812-96DrillAmoco Production CompanyMar 26, 1993Sep 2, 1992Dec 30, 19928,900
402812-97DrillAmoco Production CompanyDec 2, 1992Sep 2, 1992—8,900
402812-98DrillAmoco Production CompanyNov 17, 1992Sep 2, 1992—8,300
402812-99DrillAmoco Production CompanyAug 27, 1992Sep 2, 1992—8,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 9, 1993Williamson Stanley H. G-4-144855Cinco Compadres (Lobo)EOG Resources Inc.Plugged—

Perforations

Perforated and open-hole intervals.

FromToType
7,9808,008Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62552012.25230 S
76,5459.75415 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
00Jul 1, 1993May 18, 1993—
00May 6, 1993Mar 29, 1993Yes
00Apr 28, 1993——

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