WELL · 42-481-33746 · DISTRICT 3

Appling G. U. #1

Plugged

Wharton County · Hutchins-Kubela (5800) field  · Vertical

Appling G. U. #1 (API 42-481-33746) is a plugged well in Wharton County, plugged February 10, 2003, last operated by Venus Exploration Inc..

The RRC has issued 2 drilling permits between 1994 and 2001, permitted to 12,000 ft.

It was permitted by Venus Oil Company and has since transferred to Venus Exploration Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Frio, Vicksburg, Yegua.

Operator of record

Venus Exploration Inc.

Permitted by Venus Oil Company; the EWA schedule now lists a different operator.

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 Jul 2001
Latest permitVenus Oil CompanyFeb 15, 2001

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

12,000
total depth, ft
2
permits on file
Feb 15, 2001
last permit issued
Jan 29, 2001
completed
0
cumulative oil, bbl
24.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1995 THROUGH Feb 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 29, 2001
Shut in
—
Plugged
Feb 10, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Appling G. U. G-3-181492Hutchins-Kubela (5800)Venus Exploration, Inc.1014.8KJan 2001 – Feb 2003
Appling G.U. G-3-153089WildcatVenus Oil Company109.49KJan 1995 – Jan 2001

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 Oil CompanyJan 1995 → Feb 1995
  2. 2Venus Exploration, Inc.Feb 2001 → Jul 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
505194-99RecompletionVenus Oil CompanyFeb 12, 2001Feb 15, 2001Jan 22, 200112,000
429809-99DrillVenus Oil CompanyNov 8, 1994Nov 10, 1994Nov 22, 199412,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-153089————
—— G-3-181492————

Formation tops

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

FormationMD ftSubsea
Frio4,259-4,128
Vicksburg6,152-6,021
Yegua8,475-8,344

Perforations

Perforated and open-hole intervals.

FromToType
5,9435,945Perforated
9,2619,285Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,80417.52,050 S
9.6256,90012.25554 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
00May 24, 2001Mar 12, 2001Yes
00Apr 2, 2001——
00Mar 20, 1995Feb 23, 1995Yes
00Mar 8, 1995——

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