TEXAS · WELLS · LA SALLE COUNTY · ZCW UNIT B LEASE · API 42-283-33029 · DISTRICT 01

ZCW Unit B #1H

Y

La Salle County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Zcw Unit B #1H (API 42-283-33029) is a horizontal well in La Salle County operated by Crescent Energy Operating LLC, completed June 19, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 8, 2012, permitted to 8,533 ft.

It was permitted by Cheyenne Petroleum Company and has since transferred to Crescent Energy Operating LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Olmos, Anacacho, Eagle Ford.

Its lease has reported 318K barrels of oil and 519K mcf of gas since June 2012, last reporting volume in March 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Crescent Energy Operating LLC

Permitted by Cheyenne Petroleum Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Aug 28, 2025
Permits on file
54
Phone
(713) 337-4600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCrescent Energy Operating LLC
Production reportsCrescent Energy Operating, LLCthrough Mar 2026
Latest permitCheyenne Petroleum CompanyFeb 8, 2012

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

8,533
total depth, ft
1
permits on file
Feb 8, 2012
last permit issued
Jun 19, 2012
completed
318K
cumulative oil, bbl
519K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2012 THROUGH Mar 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 19, 2012
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
ZCW Unit B O-1-16004Eagleville (Eagle Ford-1)Crescent Energy Operating, LLC3318K519KJun 2012 – Mar 2026

Oil, barrels lease total

Last 12 months 3,335 · prior 12 5,534(-40%)

05001K202420252026

Gas, mcf lease total

Last 12 months 2,572 · prior 12 5,380(-52%)

05001K202420252026

Chain of custody

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

  1. 1Cheyenne Petroleum CompanyJul 2012 → Apr 2024
  2. 2Silverbow Resources Oper, LLCMay 2024 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
732494-99DrillCheyenne Petroleum CompanyJan 26, 2012Feb 8, 2012Mar 22, 20128,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 19, 2012ZCW Unit B O-1-16004Eagleville (Eagle Ford-1)Crescent Energy Operating LLCProducing8,533

Formation tops

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

FormationMD ftSubsea
Olmos6,240-5,782
Anacacho7,663-7,205
Eagle Ford8,300-7,842

Perforations

Perforated and open-hole intervals.

FromToType
8,8108,820Perforated
9,0709,080Perforated
9,3309,340Perforated
9,5909,600Perforated
9,8509,860Perforated
10,11010,120Perforated
10,37010,380Perforated
10,63010,640Perforated
10,89010,900Perforated
11,00511,007Perforated
11,09511,097Perforated
11,26511,267Perforated
11,35511,357Perforated
11,67011,680Perforated
11,93011,940Perforated
12,19012,200Perforated
12,45012,460Perforated
12,71012,720Perforated
12,97012,980Perforated
13,23013,240Perforated
13,49013,500Perforated
13,73513,745Perforated
14,35014,360Perforated
15,15315,163Perforated
15,45315,455Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,10014.751,822 S
5.515,8288.753,348 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Nov 14, 2012Jul 17, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Dec 5, 2012. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Olmos, Anacacho, Eagle Ford2 TIFF3,100 to 15,828Dec 5, 2012run Apr 9, 20121.84 + 1.38

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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