WELL · 42-135-34716 · DISTRICT 8

Midland Farms -A- #1

Plugged

Ector County · Fasken (Penn.) field  · Vertical

Midland Farms -A- #1 (API 42-135-34716) is a plugged well in Ector County, plugged December 10, 2024, last operated by Fasken Oil And Ranch Ltd..

The RRC has issued one drilling permit, issued November 12, 1984, permitted to 10,800 ft.

It was permitted by Amoco Production Company and has since transferred to Fasken Oil And Ranch Ltd. on the wellbore schedule.

Completion filings report one formation top, including Pennsylvanian.

Its lease has reported 247 barrels of oil and 14.7K mcf of gas since January 1993, last reporting in January 2025.

Operator of record

Fasken Oil and Ranch Ltd.

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

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 reportsMW Petroleum Corporationthrough Feb 1995
Latest permitAmoco Production CompanyNov 12, 1984

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

10,800
total depth, ft
1
permits on file
Nov 12, 1984
last permit issued
Feb 25, 1985
completed
247
cumulative oil, bbl
14.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2025

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 25, 1985
Shut in
—
Plugged
Dec 10, 2024

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
Midland Farms -A- O-10-29674Fasken (Penn.)Fasken Oil and Ranch, Ltd.124714.7KJan 1993 – Jan 2025

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 → Feb 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
257702-99DrillAmoco Production CompanyOct 31, 1984Nov 12, 1984—10,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 25, 1985Midland Farms -A- O-10-29674Fasken (Penn.)Fasken Oil and Ranch Ltd.Plugged—

Formation tops

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

FormationMD ftSubsea
PennsylvanianPENN10,384-7,342

Perforations

Perforated and open-hole intervals.

FromToType
10,38410,402Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37542817.5500 S
8.6255,02212.251,910 S
5.510,6157.8751,405 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
00Apr 3, 1985Mar 25, 1985—
00Apr 2, 1985——

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