WELL · 42-407-30697 · DISTRICT 3

Vann #2

Y

San Jacinto County · Cold Springs (Wilcox Cons.) field · Temp Abandoned  · Vertical

Vann #2 (API 42-407-30697) is a well in San Jacinto County operated by Oretta Holdings LLC, completed June 23, 2009 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 17, 2009, permitted to 11,700 ft.

It was permitted by Famcor Oil, Inc. and has since transferred to Oretta Holdings LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Yegua, Wilcox.

No lease production has been reported under this well’s leases.

Operator of record

Oretta Holdings LLC

Permitted by Famcor Oil, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Aug 4, 2025 · (832) 283-7042

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOretta Holdings LLC
Production reportsSouthcoast Production Incthrough Jul 2022
Latest permitFamcor Oil, Inc.Mar 17, 2009

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

11,700
total depth, ft
1
permits on file
Mar 17, 2009
last permit issued
Jun 23, 2009
completed
0
cumulative oil, bbl
1.48M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 23, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Vann G-3-249154Cold Springs (Wilcox, Cons.)Oretta Holdings LLC101.48MMay 2009 – Jul 2026

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. 1Famcor Oil, Inc.May 2009 → Feb 2016
  2. 2Alta Mesa Services, LPMar 2016 → Sep 2017
  3. 3Southcoast Production IncNov 2020 → Jul 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
679505-99DrillFamcor Oil, Inc.Mar 16, 2009Mar 17, 2009Mar 26, 200911,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-249154————

Formation tops

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

FormationMD ftSubsea
YeguaTOP YEGUA4,414-4,096
WilcoxTOP WILCOX7,595-7,277

Perforations

Perforated and open-hole intervals.

FromToType
11,02411,028Perforated
11,03611,038Perforated
11,04611,060Perforated
11,45111,456Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,89512.25697 S
5.511,6038.75940 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 12, 2009Jul 9, 2009—
00Sep 3, 2009May 20, 2009Yes
00Jul 11, 2009——

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