WELL · 42-239-33061 · DISTRICT 2

Lay #1

Plugged

Jackson County · EL Toro South (5500 -A-) field  · Vertical

Lay #1 (API 42-239-33061) is a plugged well in Jackson County, plugged November 7, 2008, last operated by Pegasus Operating Inc..

The RRC has issued one drilling permit, issued March 27, 2000, permitted to 6,400 ft.

It was permitted by Allegro Investments, Inc. and has since transferred to Pegasus Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Greta, Frio.

Operator of record

Pegasus Operating Inc.

Permitted by Allegro Investments, Inc.; the EWA schedule now lists a different operator.

Coldspring, TX · P-5 Y, filed Jan 5, 2026 · 18 permits on file · (361) 550-9484

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePegasus Operating Inc.
Production reportsAllegro Investments, Inc.through May 2002
Latest permitAllegro Investments, Inc.Mar 27, 2000

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

6,400
total depth, ft
1
permits on file
Mar 27, 2000
last permit issued
Apr 29, 2000
completed
0
cumulative oil, bbl
79.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2000 THROUGH Nov 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 29, 2000
Shut in
—
Plugged
Nov 7, 2008

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
Lay G-2-179350EL Toro, South (5500 -A-)Pegasus Operating, Inc.1079.4KApr 2000 – Nov 2008

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. 1Allegro Investments, Inc.May 2000 → May 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
493472-99DrillAllegro Investments, Inc.Mar 27, 2000Mar 27, 2000Apr 2, 20006,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-179350————

Formation tops

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

FormationMD ftSubsea
GretaGRETA (TOP)4,760-4,710
GretaGRETA (BASE)5,120-5,070
FrioFRIO (TOP)5,330-5,280

Perforations

Perforated and open-hole intervals.

FromToType
5,4445,446Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62572612.25260 S
4.55,6007.8751,130 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 6, 2001Aug 9, 2000Yes
00Nov 9, 2000——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000093398W-14 DisposalPlugged Nov 14, 20086002,4004,830–5,120

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