WELL · 42-481-33889 · DISTRICT 3

Swanson Acres #1

Plugged

Wharton County · Hutchins SW. (5800 SD) field  · Vertical

Swanson Acres #1 (API 42-481-33889) is a plugged well in Wharton County, plugged April 25, 2002, last operated by Venus Exploration Inc..

The RRC has issued 2 drilling permits (amended once) between 1996 and 1999, permitted to 6,012 ft.

Completion filings report 3 formation tops, including Oakville, Lwr Oakville, Frio.

Its 2 leases have reported 10.2K barrels of oil and 112K mcf of gas since January 1997, last reporting in April 2002. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Venus Exploration Inc.

San Antonio, TX · P-5 Y, filed Apr 4, 2003 · 21 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVenus Exploration Inc.
Production reportsVenus Exploration, Inc.through Oct 1999
Latest permitVenus Exploration, Inc.Apr 6, 1999
6,012
total depth, ft
3
permits on file
Apr 6, 1999
last permit issued
Jan 9, 1997
completed
10.2K
cumulative oil, bbl
112K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1997 THROUGH Apr 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 9, 1997
Shut in
—
Plugged
Apr 25, 2002

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
Swanson Acres G-3-173822Hutchins, SW. (5480)Ramsey Production Company, LLC1018.5KFeb 1999 – Apr 2002
Swanson Acres O-3-23192Hutchins, SW. (5800 SD)Venus Exploration, Inc.110.2K93.4KJan 1997 – Sep 1999

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. 1Venus Exploration, Inc.Jan 1997 → Oct 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
483109-98RecompletionVenus Exploration, Inc.Jul 12, 1999Apr 6, 1999Feb 17, 19996,012
483109-99RecompletionVenus Exploration, Inc.Mar 5, 1999Apr 6, 1999—6,012
450026-99DrillVenus Oil CompanyJul 3, 1996Aug 20, 1996Dec 2, 19966,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-173822————
—— O-3-23192————

Formation tops

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

FormationMD ftSubsea
OakvilleUPPER OAKVILLE3,336-3,211
OakvilleLOWER OAKVILLE3,450-3,325
LWR Oakville3,450-3,325
Frio3,607-3,482

Perforations

Perforated and open-hole intervals.

FromToType
5,2695,270Perforated
5,7845,785Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,04812.25505 S
5.56,0128.75631 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
00Aug 25, 1999Apr 29, 1999Yes
00Aug 13, 1999——
00Apr 28, 1997Apr 9, 1997Yes
00Apr 25, 1997——

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