TEXAS · WELLS · LAVACA COUNTY · SCHACHERL UNIT LEASE · API 42-285-33699 · DISTRICT 02

Schacherl Unit #2H

Shut in

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

Schacherl Unit #2H (API 42-285-33699) is a horizontal well in Lavaca County operated by FW Eagle Ford I LLC, completed October 8, 2013 and listed as producing on the RRC schedule, shut in November 1, 2022.

The RRC has issued one drilling permit, issued March 15, 2013, permitted to 11,844 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 286K barrels of oil and 383K mcf of gas since May 2012, last reporting volume in December 2023. The lease carries 2 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 Dec 2023
Latest permitPenn Virginia Oil & Gas, L.P.Mar 15, 2013

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

11,844
total depth, ft
1
permits on file
Mar 15, 2013
last permit issued
Oct 8, 2013
completed
286K
cumulative oil, bbl
383K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · MAY 2012 THROUGH DEC 2023

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 8, 2013
Shut in
Nov 1, 2022
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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Schacherl Unit O-2-10035Eagleville (Eagle Ford-2)FW Eagle Ford I, LLC2286K383KMay 2012 – Dec 2023

Oil, barrels lease total

Last 12 months 0 · prior 12 0

0102030202420252026

Gas, mcf lease total

Last 12 months 0 · prior 12 0

0102030202420252026

Wells named Schacherl 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.May 2012 → Oct 2022
  2. 2Rocc Oil & Gas, L.P.Jul 2023 → Dec 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
758569-99DrillPenn Virginia Oil & Gas, L.P.Mar 13, 2013Mar 15, 2013Apr 6, 201314,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 8, 2013Schacherl Unit O-2-10035Eagleville (Eagle Ford-2)FW Eagle Ford I LLCProducing · shut in Nov 1, 202211,844

Formation tops

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

FormationMD ftSubsea
Anacacho10,540-10,117
Austin Chalk10,748-10,325
Eagle Ford11,440-11,017

Perforations

Perforated and open-hole intervals.

FromToType
12,02116,316Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,54114.752,932 S
7.62511,6609.8751,450 S
4.516,4096.751,851 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 22, 2015Feb 5, 2015—
00Sep 18, 2013Jul 24, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Aug 25, 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,400 to 16,520Aug 25, 2016run May 19, 20131.24

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