WELL · 42-329-36271 · DISTRICT 8

Fee AX #1316

Plugged

Midland County · Spraberry (Trend Area) field  · Vertical

Fee AX #1316 (API 42-329-36271) is a plugged well in Midland County, plugged June 28, 2023, last operated by Fasken Oil And Ranch Ltd..

The RRC has issued one drilling permit (amended once), issued April 9, 2009, permitted to 11,200 ft.

Completion filings report 4 formation tops, including Clear Fork, Dean, Wolfcamp, Strawn.

Its lease has reported 1.28M barrels of oil and 2.95M mcf of gas since September 2009, last reporting in July 2026. The lease carries 16 wells, so these are lease totals, not this well alone.

Operator of record

Fasken Oil and Ranch Ltd.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Nov 14, 2025
Permits on file
2,057
Phone
(432) 687-1777

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFasken Oil and Ranch Ltd.
Production reportsFasken Oil and Ranch, Ltd.through Apr 2026
Latest permitFasken Oil and Ranch, Ltd.Jun 9, 2009
11,200
total depth, ft
2
permits on file
Jun 9, 2009
last permit issued
Jan 26, 2010
completed
1.28M
cumulative oil, bbl
2.95M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 26, 2010
Shut in
—
Plugged
Jun 28, 2023

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 16 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Fee "AX" O-10-39610Spraberry (Trend Area)Fasken Oil and Ranch, Ltd.161.28M2.95MSep 2009 – Jul 2026

Oil, barrels lease total

Last 12 months 1,636 · prior 12 8,243(-80%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 12,846 · prior 12 20,367(-37%)

05K10K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Fasken Oil and Ranch, Ltd.Sep 2009 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
680268-98DrillFasken Oil and Ranch, Ltd.Jun 8, 2009Jun 9, 2009Sep 30, 200911,200
680268-99DrillFasken Oil and Ranch, Ltd.Apr 8, 2009Apr 9, 2009Sep 30, 200911,200

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 26, 2010Fee AX O-10-39610Spraberry (Trend Area)Fasken Oil and Ranch Ltd.Plugged—

Formation tops

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

FormationMD ftSubsea
Clear ForkLOWER CLEARFORK7,161-4,285
Dean9,294-6,418
Wolfcamp9,570-6,694
Strawn10,629-7,753

Perforations

Perforated and open-hole intervals.

FromToType
7,71010,690Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,74314.751,050 S
5.510,7657.8751,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
00Aug 18, 2010Feb 19, 2010Yes
00Jun 29, 2010——

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