WELL · 42-215-30821 · DISTRICT 4

Sal del Rey Cattle Land & Salt #1B

Plugged

Hidalgo County · Sal del Rey (7900) field  · Vertical

Sal Del Rey Cattle Land & Salt #1B (API 42-215-30821) is a plugged well in Hidalgo County, plugged December 5, 2003, last operated by Starco Exploration Inc..

The RRC has issued 3 drilling permits between 1978 and 2002, permitted to 8,400 ft.

Completion filings report one formation top, including See Original Form G-1.

Operator of record

Starco Exploration Inc.

Dallas, TX · P-5 Y, filed Feb 6, 2015 · 21 permits on file · (214) 360-0407

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStarco Exploration Inc.
Production reportsStarco Exploration, Inc.through Sep 2002
Latest permitStarco Exploration, Inc.Sep 18, 2002
8,400
total depth, ft
3
permits on file
Sep 18, 2002
last permit issued
Sep 26, 2002
completed
0
cumulative oil, bbl
37.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 26, 2002
Shut in
—
Plugged
Dec 5, 2003

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sal del Rey Cattle, Land & Salt G-4-195223Sal del Rey (7900)Starco Exploration, Inc.1046Sep 2002 – Dec 2003
Sal del Rey Cattle, Land & Salt G-4-76800Connie (8000)Starco Exploration, Inc.1036.2KJan 1993 – Sep 2002
Sal del Rey Cattle, Land/Salt Co G-4-85993Connie (8300)Starco Exploration, Inc.101.28KJan 1993 – Sep 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. 1Starco Exploration, Inc.Jan 1993 → Sep 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
523722-99RecompletionStarco Exploration, Inc.Sep 16, 2002Sep 18, 2002Sep 18, 20027,940
46942-99RecompletionMoore McCormack Production, Inc.Apr 20, 1979Apr 20, 1979—8,380
16328-99DrillMoore McCormack Production, Inc.Jan 13, 1978Jan 13, 1978Mar 3, 19788,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-76800————
—— G-4-85993————
—— G-4-195223————

Formation tops

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

FormationMD ftSubsea
See Original Form G-1——

Perforations

Perforated and open-hole intervals.

FromToType
7,8587,870Perforated
7,9867,994Perforated
8,2848,290Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,01012.25400 S
8.6251,02312.25400 S
2.3758,175——
4.58,3727.875570 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 18, 2003Jun 13, 2003—
00Jul 3, 2003——
00Jan 19, 1994Nov 15, 1993—
00Jan 12, 1984Dec 21, 1979—
00Jan 12, 1984May 8, 1978—

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