WELL · 42-469-32545 · DISTRICT 2

Lambert M.F. #4

Plugged

Victoria County · Tom O Connor (4150) field  · Vertical

Lambert M.F. #4 (API 42-469-32545) is a plugged well in Victoria County, plugged June 29, 2002, last operated by Hilcorp Energy Company.

The RRC has issued one drilling permit, issued July 1, 1987, permitted to 3,000 ft.

It was permitted by Averill, W. M. JR. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report one formation top, including Catahoula.

Its lease has reported 164K barrels of oil and 644 mcf of gas since January 1993, last reporting in July 2026. The lease carries 8 wells, so these are lease totals, not this well alone.

Operator of record

Hilcorp Energy Company

Permitted by Averill, W. M. Jr.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Mar 26, 2026 · 3,453 permits on file · (713) 209-2411

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsPetexthrough Oct 2025
Latest permitAverill, W. M. Jr.Jul 1, 1987

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

3,000
total depth, ft
1
permits on file
Jul 1, 1987
last permit issued
Oct 16, 1987
completed
164K
cumulative oil, bbl
644
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 16, 1987
Shut in
—
Plugged
Jun 29, 2002

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; they carry 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dietzel, Herman Estate O-2-6068Coletto Creek, East (2900)Petex8164K644Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 12 · prior 12 39(-69%)

0102030202420252026

Chain of custody

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

  1. 1Averill, W. M. Inc.Jan 1993 → Jun 2003
  2. 2Kamel Oil, L.L.C.Jul 2003 → Jul 2012
  3. 3Aries Operating, LPAug 2012 → Dec 2017
  4. 4PetexFeb 2018 → Oct 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
332378-99DrillAverill, W. M. Jr.Jul 1, 1987Jul 1, 1987—3,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-6068————

Formation tops

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

FormationMD ftSubsea
Catahoula2,902-2,809

Perforations

Perforated and open-hole intervals.

FromToType
2,9272,931Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62536412.25165 S
5.53,0037.875350 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
00Dec 15, 1987Nov 10, 1987Yes
00Dec 2, 1987——
00Nov 24, 1987——

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