WELL · 42-047-31727 · DISTRICT 4

EL Coyote C #15

Plugged

Brooks County · Lopez Ranch (Consolidated) field  · Vertical

El Coyote C #15 (API 42-047-31727) is a plugged well in Brooks County, plugged August 18, 2022, last operated by Besco Operating L.P..

The RRC has issued one drilling permit, issued July 29, 1996, permitted to 11,600 ft.

It was permitted by Shell Western E&P Inc. and has since transferred to Besco Operating L.P. on the wellbore schedule.

Completion filings report one formation top, including Vicksburg.

Operator of record

Besco Operating L.P.

Permitted by Shell Western E&P Inc.; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Nov 4, 2025 · 1 permits on file · (817) 390-8787

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBesco Operating L.P.
Production reportsBesco Operating, L.P.through Mar 2022
Latest permitShell Western E&P Inc.Jul 29, 1996

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

11,600
total depth, ft
1
permits on file
Jul 29, 1996
last permit issued
Jan 14, 1997
completed
0
cumulative oil, bbl
2.03M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1996 THROUGH Aug 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 14, 1997
Shut in
—
Plugged
Aug 18, 2022

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
EL Coyote "C" G-4-160275Lopez Ranch (Vksbg F1)Besco Operating, L.P.102.03MSep 1996 – Aug 2022

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. 1Shell Western E&P Inc.Oct 1996 → Oct 1999
  2. 2Bass Enterprises Production Co.Nov 1999 → Aug 2006
  3. 3Bepco, L.P.Jan 2007 → Nov 2008
  4. 4Bopco, L.P.Jul 2009 → Oct 2015
  5. 5Besco Operating, L.P.Sep 2017 → Mar 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
450882-99DrillShell Western E&P Inc.Jul 29, 1996Jul 29, 1996Aug 24, 199611,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-160275————

Formation tops

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

FormationMD ftSubsea
VicksburgVICKSBURG F9,780-9,633

Perforations

Perforated and open-hole intervals.

FromToType
9,8009,820Perforated
10,28010,364Perforated
10,39010,514Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,02514.75965 S
7.6258,7269.8751,062 S
3.510,6866.5268 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
00May 28, 1997May 13, 1997—
00Apr 18, 1997Mar 31, 1997—
00Jan 29, 1997Oct 23, 1996Yes
00Oct 31, 1996——

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