WELL · 42-251-34556 · DISTRICT 9

Broyles (AW) #103H

Y

Johnson County · Newark East (Barnett Shale) field · Temp Abandoned  · Horizontal

Broyles (AW) #103H (API 42-251-34556) is a horizontal well in Johnson County operated by Bkv Barnett II LLC, completed January 9, 2014 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued July 11, 2013, permitted to 9,000 ft.

It was permitted by Enervest Operating, L.L.C. and has since transferred to Bkv Barnett II LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Smithwick, Marble Falls, Barnett.

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

Operator of record

BKV Barnett II LLC

Permitted by Enervest Operating, L.L.C.; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Dec 2, 2025 · 5 permits on file · (833) 425-8677

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBKV Barnett II LLC
Production reportsBedrock Production, LLCthrough Jun 2024
Latest permitEnervest Operating, L.L.C.Jul 11, 2013

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

9,000
total depth, ft
1
permits on file
Jul 11, 2013
last permit issued
Jan 9, 2014
completed
0
cumulative oil, bbl
1.28M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 9, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Broyles (AW) G-13-275001Newark, East (Barnett Shale)BKV Barnett II, LLC101.28MJan 2014 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 7,919(-100%)

05K10K202420252026

Chain of custody

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

  1. 1Enervest Operating, L.L.C.Jan 2014 → Jan 2019
  2. 2Bedrock Production, LLCFeb 2019 → Jun 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
766150-99DrillEnervest Operating, L.L.C.Jul 9, 2013Jul 11, 2013Oct 17, 20139,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-275001————

Formation tops

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

FormationMD ftSubsea
Smithwick5,951-5,098
Marble Falls6,024-5,171
BarnettUPPER BARNETT6,053-5,200

Perforations

Perforated and open-hole intervals.

FromToType
6,28010,500Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62596212.25395 S
5.510,8338.751,075 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
00Dec 8, 2014Feb 13, 2014Yes

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