WELL · 42-467-31152 · DISTRICT 5

Vien Lam #1

Plugged

Van Zandt County · Fruitvale field  · Vertical

Vien Lam #1 (API 42-467-31152) is a plugged well in Van Zandt County, plugged June 5, 2024, last operated by Jamex Inc..

The RRC has issued one drilling permit, issued February 28, 2013, permitted to 9,000 ft.

It was permitted by Parten Operating Inc. and has since transferred to Jamex Inc. on the wellbore schedule.

Completion filings report 9 formation tops, including Austin Chalk, Base Ofaustin Chalk, Woodbine, Buda.

Its lease has reported 11.2K barrels of oil since May 2013, last reporting in July 2024.

Operator of record

Jamex Inc.

Permitted by Parten Operating Inc.; the EWA schedule now lists a different operator.

Lewisville, TX · P-5 Y, filed Apr 4, 2026 · 331 permits on file · (800) 880-1552

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJamex Inc.
Production reportsJamex, Inc.through Mar 2020
Latest permitParten Operating Inc.Feb 28, 2013

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

9,000
total depth, ft
1
permits on file
Feb 28, 2013
last permit issued
Sep 10, 2020
completed
11.2K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2013 THROUGH Jul 2024

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 10, 2020
Shut in
—
Plugged
Jun 5, 2024

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
Vien Lam O-5-4022FruitvaleJamex, Inc.111.2K0May 2013 – Jul 2024

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. 1Parten Operating Inc.Aug 2013 → Mar 2016
  2. 2Jamex, Inc.Apr 2016 → Mar 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
757551-99DrillParten Operating Inc.Feb 26, 2013Feb 28, 2013Apr 29, 20139,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-5-4022————

Formation tops

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

FormationMD ftSubsea
Austin Chalk3,362-2,856
Austin ChalkBASE OF AUSTIN CHALK3,840-3,334
Base Ofaustin Chalk3,840-3,334
Woodbine4,346-3,840
Buda5,368-4,862
Rodessa7,792-7,286
Base Anhydrite7,796-7,290
James LimeJAMES8,102-7,596
Pettit8,385-7,879
Travis Peak8,504-7,998

Perforations

Perforated and open-hole intervals.

FromToType
7,9988,056Perforated
8,6188,636Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62577312.25305 S
5.58,9008.75402 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
00Oct 28, 2020Sep 16, 2020—
00Jan 30, 2014Aug 23, 2013Yes

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