WELL · 42-199-32925 · DISTRICT 3

Ben-Veniste Richard #1

Plugged

Hardin County · Sour Lake E. (Yegua #4) field  · Directional

Ben-Veniste Richard #1 (API 42-199-32925) is a plugged well in Hardin County, plugged November 5, 2009, last operated by Acock/Anaqua Operating CO. LP.

The RRC has issued one drilling permit (amended once), issued July 20, 2004, permitted to 12,900 ft.

It was permitted by Crown Petroleum Corp. and has since transferred to Acock/Anaqua Operating CO. LP on the wellbore schedule.

Completion filings report 3 formation tops, including Frio, Cockfield, Yegua.

Operator of record

Acock/Anaqua Operating Co. LP

Permitted by Crown Petroleum Corp.; the EWA schedule now lists a different operator.

Corpus Christ, TX · P-5 Y, filed Jan 4, 2026 · 288 permits on file · (361) 876-5691

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAcock/Anaqua Operating Co. LP
Production reportsCrown Petroleum Corp.through Jul 2005
Latest permitCrown Petroleum Corp.Jul 20, 2004

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

12,900
total depth, ft
2
permits on file
Jul 20, 2004
last permit issued
Jan 3, 2005
completed
0
cumulative oil, bbl
193K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH Jul 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 3, 2005
Shut in
—
Plugged
Nov 5, 2009

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
Ben-Veniste, Richard G-3-209010Sour Lake, E. (Yegua #4)Acock/Anaqua Operating Co., LP10193KJan 2005 – Jul 2012

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

Chain of custody

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

  1. 1Crown Petroleum Corp.Jan 2005 → Jul 2005

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
548457-98DrillCrown Petroleum Corp.Mar 8, 2005Jul 20, 2004Jul 28, 200412,900
548457-99DrillCrown Petroleum Corp.Jul 20, 2004Jul 20, 2004Aug 2, 200412,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-209010————

Formation tops

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

FormationMD ftSubsea
FrioBASE OF FRIO7,015-6,987
Cockfield9,410-9,382
YeguaYEGUA (EY-3)9,890-9,862
YeguaYEGUA (EY-4)10,040-10,012
YeguaYEGUA (EY06)11,140-11,112

Perforations

Perforated and open-hole intervals.

FromToType
10,04310,057Perforated
10,06210,090Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,70917.53,000 S
9.6259,95012.25680 S
710,2718.5135 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
00Aug 19, 2005Mar 23, 2005Yes
00Jun 30, 2005——

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