TEXAS · WELLS · LA SALLE COUNTY · IRVIN LEASE · API 42-283-32859 · DISTRICT 01

Irvin #6H

Y

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

Irvin #6H (API 42-283-32859) is a horizontal well in La Salle County operated by Crescent Energy Operating LLC, completed March 25, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 27, 2011, permitted to 8,421 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 2.53M barrels of oil and 2.7M mcf of gas since January 2012, last reporting volume in April 2026. The lease carries 17 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 Apr 2026
Latest permitCheyenne Petroleum CompanyOct 27, 2011

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

8,421
total depth, ft
1
permits on file
Oct 27, 2011
last permit issued
Mar 25, 2012
completed
2.53M
cumulative oil, bbl
2.7M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2012 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 25, 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 17 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Irvin O-1-15841Eagleville (Eagle Ford-1)Crescent Energy Operating, LLC172.53M2.7MJan 2012 – Apr 2026

Oil, barrels lease total

Last 12 months 82,677 · prior 12 122,805(-33%)

010K20K30K202420252026

Gas, mcf lease total

Last 12 months 66,674 · prior 12 155,930(-57%)

020K40K202420252026

Chain of custody

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

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
726611-99DrillCheyenne Petroleum CompanyOct 19, 2011Oct 27, 2011Jan 19, 20128,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 25, 2012Irvin O-1-15841Eagleville (Eagle Ford-1)Crescent Energy Operating LLCProducing8,421

Formation tops

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

FormationMD ftSubsea
Olmos6,531-6,149
Anacacho7,859-7,477
Eagle Ford8,459-8,077

Perforations

Perforated and open-hole intervals.

FromToType
10,07510,085Perforated
10,50010,510Perforated
10,78310,793Perforated
11,04011,050Perforated
11,34811,858Perforated
11,63111,643Perforated
11,91411,924Perforated
12,19712,207Perforated
12,48012,490Perforated
12,76212,772Perforated
13,04513,055Perforated
13,32813,338Perforated
13,61113,621Perforated
13,89313,903Perforated
14,17614,186Perforated
14,45914,469Perforated
14,74214,752Perforated
15,02515,035Perforated
15,30715,317Perforated
15,59015,600Perforated
15,87315,883Perforated
16,15616,166Perforated
16,43816,448Perforated
16,72116,731Perforated
17,00417,006Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,45014.752,020 S
5.517,1368.753,426 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
00Jun 28, 2012Apr 24, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Jul 17, 2012. Cased hole. 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
SURVEYS CASED HOLESpans Olmos, Anacacho, Eagle FordTIFF3,450 to 17,136Jul 17, 2012run Feb 10, 20121.70

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