WELL · 42-371-39519 · DISTRICT 8

State Neal Lethco 3405A-142 #3H

Plugged

Pecos County · Phantom (Wolfcamp) field  · Horizontal

State Neal Lethco 3405a-142 #3H (API 42-371-39519) is a plugged horizontal well in Pecos County, plugged July 29, 2021, last operated by Swordfish Energy Operating LLC.

The RRC has issued one drilling permit, issued April 17, 2017, permitted to 15,000 ft.

It was permitted by Jagged Peak Energy LLC and has since transferred to Swordfish Energy Operating LLC on the wellbore schedule.

Its lease has reported 691K barrels of oil and 1.3M mcf of gas since April 2017, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Swordfish Energy Operating LLC

Permitted by Jagged Peak Energy LLC; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Sep 4, 2025 · 2 permits on file · (281) 371-9035

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSwordfish Energy Operating LLC
Production reportsSwordfish Energy Operating, LLCthrough Mar 2026
Latest permitJagged Peak Energy LLCApr 17, 2017

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

15,000
total depth, ft
1
permits on file
Apr 17, 2017
last permit issued
May 7, 2017
completed
691K
cumulative oil, bbl
1.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 7, 2017
Shut in
—
Plugged
Jul 29, 2021

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
State Neal Lethco 3405A-142 O-10-49113Phantom (Wolfcamp)Swordfish Energy Operating, LLC4691K1.3MApr 2017 – Jul 2026

Oil, barrels lease total

Last 12 months 37,060 · prior 12 52,099(-29%)

05K10K202420252026

Gas, mcf lease total

Last 12 months 114,725 · prior 12 156,534(-27%)

010K20K30K202420252026

Chain of custody

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

  1. 1Jagged Peak Energy LLCApr 2017 → Feb 2020
  2. 2Parsley Energy Operations, LLCMar 2020 → Nov 2020
  3. 3Pecos River Exploration, LLCDec 2020 → Jun 2025
  4. 4Swordfish Energy Operating, LLCJul 2025 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
825287-99DrillJagged Peak Energy LLCApr 7, 2017Apr 17, 2017May 4, 201715,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-49113————

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,42017.51,200 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
00Aug 6, 2018Apr 18, 2018Yes

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