WELL · 42-105-34066 · DISTRICT 1

Marley Jess #1

Y

Crockett County · Massie (Strawn) field · Producing  · Vertical

Marley Jess #1 (API 42-105-34066) is a well in Crockett County operated by Scout Energy Management LLC, completed August 1, 1982 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 24, 1982, permitted to 11,700 ft.

It was permitted by Union Oil Company Of California and has since transferred to Scout Energy Management LLC on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Scout Energy Management LLC

Permitted by Union Oil Company of California; the EWA schedule now lists a different operator.

Based in
Dallas, TX
P-5 status
Active (A)
P-5 last filed
Sep 22, 2025
Permits on file
483
Phone
(972) 277-1397

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleScout Energy Management LLC
Production reportsScout Energy Management LLCthrough Jan 2026
Latest permitUnion Oil Company of CaliforniaMay 24, 1982

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

11,700
total depth, ft
1
permits on file
May 24, 1982
last permit issued
Aug 1, 1982
completed
0
cumulative oil, bbl
2.54M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 1, 1982
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Marley, Jess G-1-101428Massie (Strawn)Scout Energy Management LLC102.54MJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 359 · prior 12 2,436(-85%)

05001K202420252026

Chain of custody

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

  1. 1Union Oil Company of CaliforniaJan 1993 → May 2000
  2. 2Pure Resources, L.P.Jun 2000 → Mar 2006
  3. 3Chevron Midcontinent, L.P.Apr 2006 → Aug 2018
  4. 4Epic Permian Operating, LLCSep 2018 → Dec 2024
  5. 5Scout Energy Management LLCOct 2025 → Jan 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
161627-99DrillUnion Oil Company of CaliforniaMay 24, 1982May 24, 1982Jun 2, 198211,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-101428————

Perforations

Perforated and open-hole intervals.

FromToType
11,06311,334Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,23917.51,200 S
8.6253,02512.251,200 S
2.37510,089——
5.511,4877.875900 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, 1984Aug 19, 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/10534066, documented in the API reference.