WELL · 42-203-34231 · DISTRICT 6

Byrne Hazel Gas Unit No. 2 #8

N

Harrison County · Carthage North (Bossier Shale) field  · Vertical

Byrne Hazel Gas Unit NO. 2 #8 (API 42-203-34231) is a well in Harrison County operated by Berry Oil Comp., completed June 9, 2008.

The RRC has issued 2 drilling permits (amended once) between 2007 and 2009, permitted to 12,000 ft.

Completion filings report 4 formation tops, including Rodessa, Pettit, Travis Peak, Taylor.

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

Operator of record

Berry Oil Comp.

Houston, TX · P-5 Y, filed Mar 4, 2016 · 831 permits on file · (281) 840-4000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBerry Oil Comp.
Production reportsBerry Petroleum Company, LLCthrough May 2018
Latest permitBerry Oil Comp.Jan 29, 2009

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

12,000
total depth, ft
3
permits on file
Jan 29, 2009
last permit issued
Jun 9, 2008
completed
0
cumulative oil, bbl
243K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 9, 2008
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Byrne, Hazel R. Gas Unit No. 2 G-6-248399Darco S.E. Cotton ValleyDiversified Production LLC10211KFeb 2009 – Jul 2026
Byrne, Hazel Gas Unit No. 2 G-6-243231Carthage, North (Bossier Shale)Berry Oil Comp.1031.5KJun 2008 – Feb 2009

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. 1Berry Oil Comp.Jun 2008 → Jun 2014
  2. 2Linn Operating, Inc.Jul 2014 → Apr 2017
  3. 3Berry Petroleum Company, LLCMay 2017 → May 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
677668-99RecompletionBerry Oil Comp.Jan 21, 2009Jan 29, 2009Feb 4, 200911,900
651425-98DrillO'Benco, Inc.Jul 31, 2008Dec 19, 2007Apr 27, 200812,000
651425-99DrillO'Benco, Inc.Dec 13, 2007Dec 19, 2007Apr 27, 200810,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-243231————
—— G-6-248399————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Rodessa5,665
Pettit6,316
Travis Peak6,628
Taylor9,835

Perforations

Perforated and open-hole intervals.

FromToType
9,86610,123Perforated
11,13311,364Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,58111542 S
5.511,9007.8751,120 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
00Aug 31, 2009May 1, 2009Yes
00Jun 25, 2009——
00Jan 10, 2009Nov 25, 2008Yes
00Dec 22, 2008——

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