TEXAS · WELLS · LAVACA COUNTY · PAVLICEK LEASE · API 42-285-33652 · DISTRICT 02

Pavlicek #1H

On schedule

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

Pavlicek #1H (API 42-285-33652) is a horizontal well in Lavaca County operated by FW Eagle Ford I LLC, completed October 25, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 13, 2012, permitted to 11,923 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 341K barrels of oil and 599K mcf of gas since September 2012, last reporting volume in April 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

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 Apr 2026
Latest permitPenn Virginia Oil & Gas, L.P.Jul 13, 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,923
total depth, ft
1
permits on file
Jul 13, 2012
last permit issued
Oct 25, 2012
completed
341K
cumulative oil, bbl
599K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · SEP 2012 THROUGH APR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 25, 2012
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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Pavlicek O-2-10160Eagleville (Eagle Ford-2)FW Eagle Ford I, LLC3341K599KSep 2012 – Apr 2026

Oil, barrels lease total

Last 12 months 6,291 · prior 12 7,661(-18%)

05001K202420252026

Gas, mcf lease total

Last 12 months 4,565 · prior 12 8,228(-45%)

01K2K202420252026

Wells named Pavlicek

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.Sep 2012 → Nov 2022
  2. 2Rocc Oil & Gas, L.P.Dec 2022 → Dec 2023
  3. 3Baytex Energy USA, Inc.Jan 2024 → Dec 2025
  4. 4FW Eagle Ford I, LLCJan 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
744028-99DrillPenn Virginia Oil & Gas, L.P.Jul 5, 2012Jul 13, 2012Aug 3, 201214,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 25, 2012Pavlicek O-2-10160Eagleville (Eagle Ford-2)FW Eagle Ford I LLCProducing11,923

Formation tops

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

FormationMD ftSubsea
Anacacho10,603-10,210
Austin Chalk10,850-10,457
Eagle Ford11,570-11,177

Perforations

Perforated and open-hole intervals.

FromToType
11,90116,771Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,25014.751,622 S
7.62511,8729.8751,481 S
4.516,8956.751,917 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
00Feb 4, 2013Nov 12, 2012—
00Nov 6, 2012Sep 19, 2012Yes

Well logs

1 log loaded from the RRC's log index, the latest received Aug 17, 2015. 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 Eagle FordTIFF11,920 to 15,484Aug 17, 2015run Aug 20, 20122.80

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