WELL · 42-283-32219 · DISTRICT 1

Crescent C #1H

Y

LA Salle County · Hawkville (Eagleford Shale) field · Producing  · Horizontal

Crescent C #1H (API 42-283-32219) is a horizontal well in La Salle County operated by Perdido Energy LLC, completed June 10, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 8, 2009, permitted to 13,000 ft.

It was permitted by Murphy Exploration & Prod. CO. and has since transferred to Perdido Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Austin Chalk, Eagle Ford, Buda.

No lease production has been reported under this well’s leases.

Operator of record

Perdido Energy LLC

Permitted by Murphy Exploration & Prod. Co.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jun 4, 2026 · (833) 270-5173

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePerdido Energy LLC
Production reportsPerdido Energy, LLCthrough Mar 2026
Latest permitMurphy Exploration & Prod. Co.Sep 8, 2009

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

13,000
total depth, ft
1
permits on file
Sep 8, 2009
last permit issued
Jun 10, 2010
completed
0
cumulative oil, bbl
1.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 10, 2010
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Crescent C G-1-259085Hawkville (Eagleford Shale)Perdido Energy, LLC101.3MJun 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 15,779 · prior 12 27,059(-42%)

01K2K3K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Murphy Expl. & Prod. Co. - USAJun 2010 → Jan 2017
  2. 2Perdido Energy, LLCFeb 2017 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
684773-99DrillMurphy Exploration & Prod. Co.Sep 3, 2009Sep 8, 2009Feb 10, 201013,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-259085————

Formation tops

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

FormationMD ftSubsea
Austin Chalk10,945-10,921
Eagle Ford12,520-12,496
Buda12,740-12,716

Perforations

Perforated and open-hole intervals.

FromToType
13,19516,348Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.754,78414.752,815 S
7.62510,0089.875875 S
5.516,5506.75253 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 23, 2011Aug 11, 2010Yes
00Mar 8, 2011——

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