WELL · 42-287-32349 · DISTRICT 3

Vavra #3

Plugged

Lee County · Giddings (Austin Chalk-3) field  · Horizontal

Vavra #3 (API 42-287-32349) is a plugged horizontal well in Lee County, plugged March 25, 2003, last operated by Wcs Oil And Gas Corporation.

The RRC has issued one drilling permit, issued July 30, 1992, permitted to 7,800 ft.

It was permitted by Keystone Exploration, Inc and has since transferred to Wcs Oil And Gas Corporation on the wellbore schedule.

Completion filings report 3 formation tops, including Navarro, Pecan Gap, Austin Chalk.

Its lease has reported 102K barrels of oil and 110K mcf of gas since January 1993, last reporting in July 2003.

Operator of record

WCS Oil and Gas Corporation

Permitted by Keystone Exploration, Inc; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Jan 7, 2005 · 277 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWCS Oil and Gas Corporation
Production reportsWCS Oil and Gas Corporationthrough Mar 2003
Latest permitKeystone Exploration, IncJul 30, 1992

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

7,800
total depth, ft
1
permits on file
Jul 30, 1992
last permit issued
Oct 1, 1992
completed
102K
cumulative oil, bbl
110K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 1, 1992
Shut in
—
Plugged
Mar 25, 2003

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
Vavra O-3-21738Giddings (Austin Chalk-3)WCS Oil and Gas Corporation1102K110KJan 1993 – Jul 2003

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. 1Keystone Exploration, IncJan 1993 → Dec 1997
  2. 2United Oil & Minerals, Inc.Jan 1998 → Dec 1998
  3. 3WCS Oil and Gas CorporationJan 1999 → Mar 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
401795-99DrillKeystone Exploration, IncJul 30, 1992Jul 30, 1992Aug 5, 19927,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-21738————

Formation tops

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

FormationMD ftSubsea
Navarro5,062-4,742
Pecan Gap6,460-6,140
Austin Chalk7,036-6,716

Perforations

Perforated and open-hole intervals.

FromToType
7,0908,649Perforated
7,0908,980Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,07012.25450 S
5.57,0908.75295 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 1, 1992Oct 16, 1992Yes
00Nov 10, 1992——

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