WELL · 42-383-31963 · DISTRICT 7

Loftin #5

Plugged

Reagan County · Spraberry (Trend Area) field  · Vertical

Loftin #5 (API 42-383-31963) is a plugged well in Reagan County, plugged April 11, 2023, last operated by Earthstone Operating LLC.

The RRC has issued one drilling permit, issued June 15, 1981, permitted to 7,700 ft.

It was permitted by Discovery Operating, Inc. and has since transferred to Earthstone Operating LLC on the wellbore schedule.

Its lease has reported 89.7K barrels of oil and 515K mcf of gas since January 1993, last reporting in May 2023. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

Earthstone Operating LLC

Permitted by Discovery Operating, Inc.; the EWA schedule now lists a different operator.

The Woodlands, TX · P-5 Inactive, filed May 25, 2023 · 283 permits on file · (281) 298-4246

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEarthstone Operating LLC
Production reportsSable Permian Resources, LLCthrough Dec 2020
Latest permitDiscovery Operating, Inc.Jun 15, 1981

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

7,700
total depth, ft
1
permits on file
Jun 15, 1981
last permit issued
Apr 15, 1982
completed
89.7K
cumulative oil, bbl
515K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 15, 1982
Shut in
—
Plugged
Apr 11, 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 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Loftin O-9-5585Spraberry (Trend Area)Earthstone Operating, LLC789.7K515KJan 1993 – May 2023

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. 1Discovery Operating, Inc.Jan 1993 → Apr 2014
  2. 2Enduring Resources, LLCMay 2014 → Jun 2014
  3. 3American Energy-Perm Basin, LLCJul 2014 → Apr 2016
  4. 4Permian Resources, LLCMay 2016 → Jun 2017
  5. 5Sable Permian Resources Land,llcOct 2018 → Oct 2018
  6. 6Sable Permian Resources, LLCDec 2020 → Dec 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
120920-99DrillDiscovery Operating, Inc.Jun 15, 1981Jun 15, 1981—7,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-5585————

Perforations

Perforated and open-hole intervals.

FromToType
—7,280Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62572811400 S
2.3756,032——
4.57,4507.875950 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
00Jan 12, 1984Jun 17, 1982—

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