WELL · 42-013-32540 · DISTRICT 1

Watson Camp Trust A #15A

Plugged

Atascosa County · Somerset field  · Vertical

Watson Camp Trust A #15A (API 42-013-32540) is a plugged well in Atascosa County, plugged June 24, 2010, last operated by Prospectors Ltd. The.

The RRC has issued one drilling permit, issued February 2, 1984, permitted to 2,000 ft.

Completion filings report 2 formation tops, including Lit Zone, Olmos.

Its lease has reported 6.56K barrels of oil and 22 mcf of gas since January 1993, last reporting in August 2010. The lease carries 23 wells, so these are lease totals, not this well alone.

Operator of record

Prospectors Ltd. The

Somerset, TX · P-5 Y, filed Jul 5, 2002 · 27 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleProspectors Ltd. The
Production reportsU. D. Man, Inc.through Dec 2003
Latest permitProspectors Ltd., TheFeb 2, 1984

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

2,000
total depth, ft
1
permits on file
Feb 2, 1984
last permit issued
Feb 11, 1984
completed
6.56K
cumulative oil, bbl
22
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 11, 1984
Shut in
—
Plugged
Jun 24, 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 lease this well is completed on; they carry 23 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Watson Camp Trust O-1-10825SomersetAminex USA, Inc.236.56K22Jan 1993 – Aug 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. 1Caspen Operating CompanyJan 1993 → Jul 1993
  2. 2Cottonwood Resources, Inc.Aug 1993 → Jan 1994
  3. 3Butler, Kevin O.Feb 1994 → Mar 1996
  4. 4Butler, Kevin O. & Assoc., Inc.Apr 1996 → Mar 1997
  5. 5U. D. Man, Inc.Apr 1997 → Dec 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
228252-99DrillProspectors Ltd., TheFeb 14, 1985Feb 2, 1984—2,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-10825————

Formation tops

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

FormationMD ftSubsea
Lit Zone1,544-907
OlmosOLMOS 02 SAND1,685-1,048
OlmosOLMOS O2 SAND1,685-1,048

Perforations

Perforated and open-hole intervals.

FromToType
1,6851,705Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,7486.75200 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
00Mar 25, 1986Feb 6, 1985—
00Jan 25, 1986——
00Jul 15, 1985Feb 6, 1985—
00Jul 12, 1985Apr 19, 1984—
00Jul 10, 1985——
00May 16, 1984Apr 19, 1984—
00May 9, 1984Apr 19, 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/01332540, documented in the API reference.