TEXAS · WELLS · ANDREWS COUNTY · MIDLAND FARMS DEEP UNIT LEASE · API 42-003-31742 · DISTRICT 7B

Midland Farms Deep Unit #73

Plugged

Andrews County · Midland Farms Deep field  · Vertical

Midland Farms Deep Unit #73 (API 42-003-31742) is a plugged well in Andrews County, plugged July 26, 2017, last operated by Occidental Permian Ltd..

The RRC has issued 2 drilling permits between 1978 and 1980, permitted to 12,900 ft.

It was permitted by Amoco Production CO.-Andrews and has since transferred to Occidental Permian Ltd. on the wellbore schedule.

Completion filings report 6 formation tops, including Grayburg, Wolfcamp, Strawn, Devonian.

Its lease has reported 4.93M barrels of oil and 21.6M mcf of gas since the record begins in January 1993, last reporting volume in August 2026. The lease carries 67 wells, so these are lease totals, not this well alone.

Operator of record

Occidental Permian Ltd.

Permitted by Amoco Production Co.-Andrews; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Feb 2, 2026
Permits on file
6,251
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOccidental Permian Ltd.
Production reportsOccidental Permian Ltd.through Aug 2026
Latest permitAmoco Production Co.-AndrewsSep 5, 1980

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

12,900
total depth, ft
2
permits on file
Sep 5, 1980
last permit issued
Aug 3, 2015
completed
4.93M
cumulative oil, bbl
21.6M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 3, 2015
Shut in
—
Plugged
Jul 26, 2017

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 67 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Midland Farms Deep Unit O-10-30861Midland Farms DeepOccidental Permian Ltd.674.93M21.6Mby Jan 1993 – Aug 2026

Oil, barrels lease total

Last 12 months 1,037,450 · prior 12 591,130(+76%)

0200K400K202420252026

Gas, mcf lease total

Last 12 months 5,043,246 · prior 12 1,669,342(+202%)

0500K1M202420252026

Wells named Midland Farms Deep Unit

Occidental Permian Ltd.'s other wells filed under this lease name in Andrews County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Amoco Production CompanyJan 1993 → Feb 1997
  2. 2Altura Energy Ltd.Mar 1997 → Apr 2000
  3. 3Occidental Permian Ltd.May 2000 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
91684-99RecompletionAmoco Production Co.-AndrewsSep 5, 1980Sep 5, 1980—12,637
31471-99DrillAmoco Production Co.-AndrewsAug 28, 1978Aug 28, 1978Feb 11, 197912,900

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 3, 2015Midland Farms Deep Unit O-10-30861Midland Farms DeepOccidental Permian Ltd.Plugged—
Jun 23, 1980Midland Farms Deep Unit O-10-13351Midland Farms (Fusselman)Amoco Production Co.-AndrewsPlugged—
Mar 26, 1979Midland Farms Deep Unit O-10-25593Midland Farms SW (Ellenburger)Amoco Production Co.-AndrewsPlugged—
Mar 26, 1979Midland Farms Deep Unit O-10-13350Midland Farms (Ellenburger)Occidental Permian Ltd.Plugged—

Formation tops

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

FormationMD ftSubsea
Grayburg4,665-1,607
Wolfcamp8,270-5,212
Strawn9,663-6,605
Devonian10,837-7,779
Fusselman11,844-8,786
Ellenburger12,543-9,485

Perforations

Perforated and open-hole intervals.

FromToType
11,06211,204Perforated
11,13311,386Perforated
11,23811,386Perforated
11,88411,930Perforated
12,60312,608Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37541617.5450 S
9.6254,99012.251,180 S
2.8755,039——
2.37511,687——
712,6378.75900 S
7———

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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jun 14, 2017Jun 8, 2017—
00Oct 25, 1993Jul 29, 1993—
00Jan 30, 1987Jan 14, 1987—
00Oct 8, 1986Sep 16, 1980—
00Sep 20, 1986——
00Jan 12, 1984Sep 16, 1980—
00Jan 12, 1984Oct 5, 1979—
00Jan 12, 1984May 24, 1979—

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.

Find logs withinmiles of this well:List →Map →

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