TEXAS · WELLS · LAVACA COUNTY · BARRAZA UNIT LEASE · API 42-285-33672 · DISTRICT 02

Barraza Unit #1H

On schedule

Lavaca County · Eagleville (Eagle Ford-2) field · Producing  · Horizontal

Barraza Unit #1H (API 42-285-33672) is a horizontal well in Lavaca County operated by FW Eagle Ford I LLC, completed April 23, 2013 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 25, 2012, permitted to 11,595 ft.

It was permitted by Penn Virginia Oil & Gas, L.P. and has since transferred to FW Eagle Ford I LLC on the wellbore schedule.

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

Its lease has reported 141K barrels of oil and 193K mcf of gas since January 2013, last reporting volume in March 2026.

Operator of record

FW Eagle Ford I LLC

Permitted by Penn Virginia Oil & Gas, L.P.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jan 15, 2026
Permits on file
46
Phone
(713) 722-6500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFW Eagle Ford I LLC
Production reportsFW Eagle Ford I, LLCthrough Mar 2026
Latest permitPenn Virginia Oil & Gas, L.P.Oct 25, 2012

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

11,595
total depth, ft
1
permits on file
Oct 25, 2012
last permit issued
Apr 23, 2013
completed
141K
cumulative oil, bbl
193K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JAN 2013 THROUGH MAR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 23, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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
Barraza Unit O-2-10349Eagleville (Eagle Ford-2)FW Eagle Ford I, LLC1141K193KJan 2013 – Mar 2026

Oil, barrels lease total

Last 12 months 1,837 · prior 12 3,361(-45%)

0200400600202420252026

Gas, mcf lease total

Last 12 months 26 · prior 12 1,950(-99%)

0200400600202420252026

Wells named Barraza Unit

FW Eagle Ford I LLC's other wells filed under this lease name in Lavaca County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Penn Virginia Oil & Gas, L.P.Jan 2013 → Nov 2022
  2. 2Rocc Oil & Gas, L.P.Dec 2022 → Sep 2023
  3. 3Baytex Energy USA, Inc.May 2024 → Dec 2025
  4. 4FW Eagle Ford I, LLCJan 2026 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
749795-99DrillPenn Virginia Oil & Gas, L.P.Oct 11, 2012Oct 25, 2012Nov 24, 201214,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 23, 2013Barraza Unit O-2-10349Eagleville (Eagle Ford-2)FW Eagle Ford I LLCProducing11,595

Formation tops

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

FormationMD ftSubsea
Anacacho10,786-10,369
Austin Chalk11,035-10,618
Eagle Ford11,727-11,310

Perforations

Perforated and open-hole intervals.

FromToType
12,13716,089Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,50714.752,084 S
7.62511,9849.8751,522 S
4.516,1746.751,807 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
00Jul 8, 2026Jun 15, 2026—
00Sep 21, 2015Feb 3, 2015—
00Mar 26, 2013Jan 24, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Jan 13, 2016. 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 Anacacho, Austin Chalk, Eagle FordTIFF2,731 to 16,174Jan 13, 2016run Dec 20, 20121.36

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