WELL · 42-383-32751 · DISTRICT 7

Patterson Susan #5

N

Reagan County · Calvin (Dean) field  · Vertical

Patterson Susan #5 (API 42-383-32751) is a well in Reagan County operated by Stephens Autry C., completed January 11, 1984.

The RRC has issued one drilling permit, issued September 21, 1983, permitted to 8,100 ft.

Completion filings report 2 formation tops, including Spraberry, Dean.

Its 2 leases have reported 119K barrels of oil and 915K mcf of gas since January 1993, last reporting in July 2026. The leases carry 14 wells, so these are lease totals, not this well alone.

Operator of record

Stephens Autry C.

Based in
Midland, TX
P-5 status
Inactive (I)
P-5 last filed
Nov 22, 1999
Permits on file
475
Phone
(432) 687-1575

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStephens Autry C.
Production reportsDiamondback E&P LLCthrough Dec 2025
Latest permitStephens, Autry C.Sep 21, 1983

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

8,100
total depth, ft
1
permits on file
Sep 21, 1983
last permit issued
Jan 11, 1984
completed
119K
cumulative oil, bbl
915K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 11, 1984
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 14 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Patterson, Susan O-9-14184Spraberry (Trend Area)Diamondback E&P LLC796.4K764KNov 1995 – Jul 2026
Patterson, Susan O-9-6081Calvin (Dean)Stephens, Autry C.722.6K151KJan 1993 – Feb 1996

Oil, barrels lease total

Last 12 months 130 · prior 12 164(-21%)

0204060202420252026

Chain of custody

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

  1. 1Stephens, Autry C.Jan 1993 → Aug 2000
  2. 2Endeavor Energy Resources L.P.Sep 2000 → Dec 2024
  3. 3Diamondback E&P LLCJan 2025 → Dec 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
214216-99DrillStephens, Autry C.Sep 21, 1983Sep 21, 1983Oct 29, 19838,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-6081————
—— O-9-14184————

Formation tops

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

FormationMD ftSubsea
Spraberry6,206-3,575
Dean7,602-4,971

Perforations

Perforated and open-hole intervals.

FromToType
6,8317,772Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62545211200 S
5.57,9507.8751,100 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
00Dec 21, 1995Jan 24, 1984—
00Feb 7, 1984Jan 24, 1984—
00Feb 2, 1984Jan 24, 1984—

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