TEXAS · WELLS · LIBERTY COUNTY · RIVIERE EST. LEASE · API 42-291-03521 · DISTRICT 03

Riviere Est. #3

Plugged

Liberty County · Liberty South field  · Vertical

Riviere Est. #3 (API 42-291-03521) is a plugged well in Liberty County, plugged October 26, 2016, last operated by Anderson Arnold.

The RRC has issued one drilling permit, issued April 12, 1983, permitted to 2,252 ft.

It was permitted by P & V Oil CO. and has since transferred to Anderson Arnold on the wellbore schedule.

Completion filings report 2 formation tops, including Miocene (undifferentiated), Frio.

Operator of record

Anderson Arnold

Permitted by P & V Oil Co.; the EWA schedule now lists a different operator.

Based in
Arlington, TX
P-5 status
Inactive (I)
P-5 last filed
Feb 3, 1998
Permits on file
1
Phone
(713) 783-3663

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnderson Arnold
Production reportsnone
Latest permitP & V Oil Co.Apr 12, 1983

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

2,252
total depth, ft
1
permits on file
Apr 12, 1983
last permit issued
Jan 28, 1984
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 28, 1984
Shut in
—
Plugged
Oct 26, 2016

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
Riviere Est. O-3-17569Liberty, SouthAnderson, Arnold100Jan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
191231-99OtherP & V Oil Co.Apr 12, 1983Apr 12, 1983—2,252

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 28, 1984Riviere Est. O-3-17569Liberty SouthAnderson ArnoldPlugged—
—Riviere A. B. et Al O-3-7273Liberty SouthSpider Oil CorporationPlugged—

Formation tops

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

FormationMD ft
Miocene (undifferentiated)MIOCENE1
Frio1,900

Perforations

Perforated and open-hole intervals.

FromToType
1,6101,630Perforated
—1,650Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.75203——
5.52,823——

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
00Jun 8, 1984Feb 2, 1984—
00May 22, 1984Feb 2, 1984—
00Jan 12, 1984——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Jan 1987
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000050831W-14 DisposalPlugged Nov 3, 20161502501,610–1,630

MONTHLY INJECTED, BBL · H-10 · LAST 1 REPORTED MONTHS

Last 12 months 0

011987

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