WELL · 42-329-00591 · DISTRICT 8

Sweetie Peck -A- #6

Plugged

Midland County · Sweetie Peck (Devonian) field  · Vertical

Sweetie Peck -A- #6 (API 42-329-00591) is a plugged well in Midland County, plugged December 12, 1984, last operated by Endeavor Energy Resources L.P..

The RRC has issued one drilling permit (amended once), issued July 15, 2011, permitted to 12,000 ft.

Completion filings report 3 formation tops, including Shale, Lime, Shale, Blk Shale And Lime.

Its lease has reported 37.9K barrels of oil and 255K mcf of gas since January 2012, last reporting in July 2026.

Operator of record

Endeavor Energy Resources L.P.

Midland, TX · P-5 Y, filed Apr 4, 2026 · 6,190 permits on file · (855) 247-5920

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEndeavor Energy Resources L.P.
Production reportsDiamondback E&P LLCthrough Apr 2026
Latest permitEndeavor Energy Resources L.P.Jul 15, 2011

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

12,000
total depth, ft
2
permits on file
Jul 15, 2011
last permit issued
—
completed
37.9K
cumulative oil, bbl
255K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Dec 12, 1984

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
Sweetie Peck -A- O-10-43609Spraberry (Trend Area)Diamondback E&P LLC137.9K255KJan 2012 – Jul 2026

Oil, barrels lease total

Last 12 months 363 · prior 12 3,707(-90%)

05001K1.5K202420252026

Gas, mcf lease total

Last 12 months 2,170 · prior 12 5,225(-58%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Endeavor Energy Resources L.P.Jan 2012 → Dec 2024
  2. 2Diamondback E&P LLCJan 2025 → Sep 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
720140-98ReenterEndeavor Energy Resources L.P.Jul 10, 2012Jul 15, 2011Sep 19, 201110,364
720140-99ReenterEndeavor Energy Resources L.P.Jul 13, 2011Jul 15, 2011—12,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-43609————

Formation tops

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

FormationMD ftSubsea
Shale8,430-5,537
Lime, Shale9,628-6,735
BLK Shale and Lime10,740-7,847

Perforations

Perforated and open-hole intervals.

FromToType
9,08310,364Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531017.5—
9.6254,64412.25—
4.510,7955.5670 S
5.512,2156.5—

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 2, 2014Nov 12, 2012Yes
00Jan 12, 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). 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/32900591, documented in the API reference.