WELL · 42-013-01866 · DISTRICT 1

Sandeen John #1

Plugged

Atascosa County · Jourdanton (Georgetown) field  · Vertical

Sandeen John #1 (API 42-013-01866) is a plugged well in Atascosa County, plugged February 25, 2014, last operated by Virtex Operating Company Inc..

The RRC has issued one drilling permit, issued February 22, 2010, permitted to 7,200 ft.

Completion filings report 4 formation tops, including Del Rio, Del Rioclay, Georgetown, Edwards.

Operator of record

Virtex Operating Company Inc.

Corpus Christ, TX · P-5 Y, filed Sep 6, 2024 · 170 permits on file · (361) 299-9790

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVirtex Operating Company Inc.
Production reportsVirtex Operating Company, Inc.through Jun 2010
Latest permitVirtex Operating Company, Inc.Feb 22, 2010
7,200
total depth, ft
1
permits on file
Feb 22, 2010
last permit issued
Nov 25, 2009
completed
0
cumulative oil, bbl
2.47M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 25, 2009
Shut in
—
Plugged
Feb 25, 2014

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
Sandeen, John G-1-255674Jourdanton (Georgetown)Virtex Operating Company, Inc.10238Nov 2009 – Feb 2014
Sandeen, John G-1-129294JourdantonVirtex Operating Company, Inc.102.47MJan 1993 – Nov 2009

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. 1Exxon Corp.Jan 1993 → May 1999
  2. 2Wagner Oil CompanyJun 1999 → Nov 2002
  3. 3Virtex Petroleum Company, Inc.Dec 2002 → Oct 2007
  4. 4Virtex Operating Company, Inc.Feb 2008 → Jun 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
691610-99RecompletionVirtex Operating Company, Inc.Feb 19, 2010Feb 22, 2010Nov 18, 20097,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-129294————
—— G-1-255674————

Formation tops

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

FormationMD ftSubsea
Del Rio7,128-6,675
Del Rioclay7,128-6,675
Georgetown7,234-6,781
GeorgetownGEORGETOWN LIME7,234-6,781
Edwards7,287-6,834
EdwardsEDWARDS LIME7,287-6,834

Perforations

Perforated and open-hole intervals.

FromToType
7,1327,170Perforated
7,3367,342Perforated
7,3577,362Perforated
7,3727,387Open hole
—7,388Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,487——
9.6252,49913.751,000 S
9.6252,499—1,000 S
5.57,372——
5.57,384—100 S
5.57,3848.75300 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 30, 2010Apr 16, 2010Yes
00May 13, 2010——
00Jan 30, 1989Nov 3, 1988—
00Jan 11, 1989——
00Jan 12, 1984——

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