WELL · 42-481-34466 · DISTRICT 3

Vrana #1

Plugged

Wharton County · Black Owl (Yegua 9200) field  · Vertical

Vrana #1 (API 42-481-34466) is a plugged well in Wharton County, plugged June 16, 2010, last operated by Cox & Perkins Exploration Inc..

The RRC has issued 4 drilling permits between 2002 and 2010, permitted to 10,500 ft.

Completion filings report 4 formation tops, including Yegua, Dy, Ey, Nodosaria Mexicana.

Operator of record

Cox & Perkins Exploration Inc.

Houston, TX · P-5 Y, filed Nov 2, 2012 · 306 permits on file · (713) 783-7880

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCox & Perkins Exploration Inc.
Production reportsCox & Perkins Exploration, Inc.through Mar 2010
Latest permitCox & Perkins Exploration, Inc.Feb 12, 2010
10,500
total depth, ft
4
permits on file
Feb 12, 2010
last permit issued
Jan 4, 2006
completed
0
cumulative oil, bbl
2.26M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2002 THROUGH Jun 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 4, 2006
Shut in
—
Plugged
Jun 16, 2010

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Vrana G-3-191567Black Owl (Yegua 9200)Cox & Perkins Exploration, Inc.102.22MSep 2002 – Jun 2010
Vrana G-3-212526Black Owl (Yegua 8300)Cox & Perkins Exploration, Inc.1038.1KOct 2005 – Jun 2010

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. 1Cox & Perkins Exploration, Inc.Oct 2002 → Mar 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
691011-99RecompletionCox & Perkins Exploration, Inc.Feb 9, 2010Feb 12, 2010Feb 16, 20109,860
609785-99RecompletionCox & Perkins Exploration, Inc.Nov 18, 2005Nov 28, 2005Dec 6, 20059,860
605329-99RecompletionCox & Perkins Exploration, Inc.Aug 23, 2005Aug 23, 2005—9,860
522895-99DrillCox & Perkins Exploration, Inc.Aug 19, 2002Aug 19, 2002Aug 25, 200210,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-191567————
—— G-3-212526————

Formation tops

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

FormationMD ftSubsea
Yegua7,500-7,398
DY7,780-7,678
EY8,319-8,217
Nodosaria Mexicana8,472-8,370

Perforations

Perforated and open-hole intervals.

FromToType
8,7708,781Perforated
9,2729,347Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,87013.5720 S
7.6256,2849.875490 S
4.59,8606.75260 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
00Jun 29, 2010Mar 3, 2010Yes
00Jun 2, 2006Jan 20, 2006Yes
00Feb 7, 2006Nov 21, 2005Yes
00Dec 6, 2005——
00Dec 19, 2002Oct 23, 2002Yes
00Dec 3, 2002——

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