TEXAS · WELLS · SHACKELFORD COUNTY · PATTY "A" LEASE · API 42-417-35776 · DISTRICT 6E

Patty A #3

Plugged

Shackelford County · Lilly (Palo Pinto Lo.) field  · Vertical

Patty A #3 (API 42-417-35776) is a plugged well in Shackelford County, plugged July 13, 2012, last operated by Sojourner Drilling Corporation.

The RRC has issued one drilling permit, issued May 2, 1984, permitted to 3,500 ft.

Completion filings report 2 formation tops, including T/Patio, T/Lower Palo Pinto Lo.

Its lease has reported 51.3K barrels of oil and 19.2K mcf of gas since January 1993, with no volume in the three years through April 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Sojourner Drilling Corporation

Based in
Abilene, TX
P-5 status
Active (A)
P-5 last filed
Oct 7, 2025
Permits on file
872
Phone
(325) 672-2832

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSojourner Drilling Corporation
Production reportsSojourner Drilling Corporationthrough Jun 2009
Latest permitSojourner Drlg. Corp.May 2, 1984
3,500
total depth, ft
1
permits on file
May 2, 1984
last permit issued
May 12, 1984
completed
51.3K
cumulative oil, bbl
19.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 12, 1984
Shut in
—
Plugged
Jul 13, 2012

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Patty "A" O-8-20785Lilly (Palo Pinto, Lo.)Sojourner Drilling Corporation451.3K19.2KJan 1993 – Jun 2009

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. 1Sojourner Drilling CorporationJan 1993 → Jun 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
237514-99DrillSojourner Drlg. Corp.May 1, 1984May 2, 1984May 5, 19843,500

Completions

CompletedLeaseFieldOperatorStatusDepth
May 12, 1984Patty A O-8-20785Lilly (Palo Pinto Lo.)Sojourner Drilling CorporationPlugged—

Formation tops

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

FormationMD ftSubsea
T/Patio3,208-1,598
T/Lower Palo Pinto LO3,428-1,818

Perforations

Perforated and open-hole intervals.

FromToType
3,4243,431Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511012.2590 sx
4.53,4997.875200 sx

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 15, 1984May 21, 1984—
00Jun 13, 1984May 21, 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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

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