TEXAS · WELLS · ANDREWS COUNTY · FASKEN, DAVID -H- LEASE · API 42-003-31736 · DISTRICT 7B

Fasken David -H- #3

Plugged

Andrews County · Fasken North (Fusselemn) field  · Vertical

Fasken David -H- #3 (API 42-003-31736) is a plugged well in Andrews County, plugged June 13, 1995, last operated by MW Petroleum Corporation.

The RRC has issued 3 drilling permits (amended once) between 1978 and 1987, permitted to 13,800 ft.

It was permitted by Amoco Production Company and has since transferred to MW Petroleum Corporation on the wellbore schedule.

Completion filings report one formation top, including Fusselman.

Operator of record

MW Petroleum Corporation

Permitted by Amoco Production Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Aug 6, 1998
Permits on file
364
Phone
(713) 296-6000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitAmoco Production CompanyJan 26, 1987
13,800
total depth, ft
4
permits on file
Jan 26, 1987
last permit issued
Apr 1, 1987
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 1, 1987
Shut in
—
Plugged
Jun 13, 1995

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 -H- O-10-31197Fasken ,north (Fusselemn)MW Petroleum Corporation100Jan 1993 – Jul 1995

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
325843-99RecompletionAmoco Production CompanyJan 26, 1987Jan 26, 1987—13,105
43100-99RecompletionAmoco Production CompanyFeb 26, 1979Feb 26, 1979—8,600
30710-98DrillAmoco Production CompanyFeb 26, 1979Aug 16, 1978—8,600
30710-99DrillAmoco Production CompanyAug 16, 1978Aug 16, 1978Aug 20, 197813,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 1, 1987Fasken David -H- O-10-31197Fasken North (Fusselemn)MW Petroleum CorporationPlugged—
Oct 15, 1978Fasken David H. O-10-25329Fasken (Wolfcamp North)Amoco Production CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Fusselman12,250-9,174

Perforations

Perforated and open-hole intervals.

FromToType
8,4208,470Perforated
12,25012,270Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37533517.5450 S
9.6254,57512.251,250 S
2.8758,266——
713,10512.253,050 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 14, 1987Apr 7, 1987Yes
00May 2, 1987——
00Jan 12, 1984Feb 23, 1979Yes

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