WELL · 42-135-10600 · DISTRICT 8

Fasken David -AV- #3

Plugged

Ector County · Circle Bar (Fusselman) field  · Vertical

Fasken David -AV- #3 (API 42-135-10600) is a plugged well in Ector County, plugged July 21, 2016, last operated by Amoco Production CO.-Andrews.

The RRC has issued one drilling permit, issued October 2, 1984, permitted to 13,098 ft.

Completion filings report 4 formation tops, including Clear Fork, Devonian, Fusselman, Ellenburger.

Its lease has reported 62.6K barrels of oil and 834K mcf of gas since January 1993, last reporting in August 2016.

Operator of record

Amoco Production Co.-Andrews

Based in
Andrews, TX
P-5 status
Inactive (I)
Permits on file
1,295

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAmoco Production Co.-Andrews
Production reportsApache Corporationthrough Oct 2009
Latest permitAmoco Production Co.-AndrewsOct 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.

13,098
total depth, ft
1
permits on file
Oct 2, 1984
last permit issued
—
completed
62.6K
cumulative oil, bbl
834K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Jul 21, 2016

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Fasken, David -AV- O-10-29403Circle Bar (Devonian)Apache Corporation162.6K834KJan 1993 – Aug 2016

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. 1MW Petroleum CorporationJan 1993 → Aug 1998
  2. 2Apache CorporationSep 1998 → Oct 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
253684-99RecompletionAmoco Production Co.-AndrewsOct 1, 1984Oct 2, 1984—13,098

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-29403————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK6,800-3,797
Devonian11,204-8,201
Fusselman12,253-9,250
Ellenburger13,077-10,074

Perforations

Perforated and open-hole intervals.

FromToType
11,44611,520Perforated
—12,320Perforated
—13,093Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37529917.5400 S
13.37531617.5400 S
9.6254,93112.252,350 S
9.6254,94512.252,150 S
5.55,9548.75470 S
5.513,0928.752,750 S
5.513,0938.752,550 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 23, 2012Jul 12, 2011—
00Dec 27, 1984Dec 7, 1984—
00Dec 20, 1984——
00Jan 12, 1984Feb 7, 1972—
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) and the University Lands library. 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/13510600, documented in the API reference.