TEXAS · WELLS · LOVING COUNTY · API 42-301-32970 · DISTRICT 7B

Pecos State 46 #6H

Y

Loving County · Phantom (Wolfcamp) field · Producing  · Horizontal

Pecos State 46 #6H (API 42-301-32970) is a horizontal well in Loving County operated by Wpx Energy Permian LLC, completed December 23, 2016 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 25, 2016, permitted to 10,296 ft.

It was permitted by Rki Exploration & Production LLC and has since transferred to Wpx Energy Permian LLC on the wellbore schedule.

Completion filings report 10 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

Its 2 leases have reported 401K barrels of oil and 2.28M mcf of gas since May 2014, last reporting volume in March 2026. The leases carry 4 wells, so these are lease totals, not this well alone.

Operator of record

WPX Energy Permian LLC

Permitted by RKI Exploration & Production LLC; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
956
Phone
(405) 235-3611

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWPX Energy Permian LLC
Production reportsWPX Energy Permian, LLCthrough Mar 2026
Latest permitRKI Exploration & Production LLCJul 25, 2016

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

10,296
total depth, ft
1
permits on file
Jul 25, 2016
last permit issued
Dec 23, 2016
completed
401K
cumulative oil, bbl
2.28M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2016 THROUGH Mar 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 23, 2016
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 2 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Pecos State 46 G-10-286876Phantom (Wolfcamp)WPX Energy Permian, LLC1401K2.28MNov 2016 – Mar 2026
Pecos State 46 O-10-45627Phantom (Wolfcamp)WPX Energy Permian, LLC300May 2014 – —

Gas, mcf lease total

Last 12 months 236,348 · prior 12 79,825(+196%)

020K40K202420252026

Chain of custody

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

  1. 1WPX Energy Permian, LLCDec 2016 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
817031-99DrillRKI Exploration & Production LLCJul 14, 2016Jul 25, 2016Aug 11, 201616,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 23, 2016Pecos State 46 G-10-286876Phantom (Wolfcamp)WPX Energy Permian LLCProducing10,296
Dec 23, 2016Pecos State 46 O-10-45627Phantom (Wolfcamp)WPX Energy Permian LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Bell Canyon3,238-443
Cherry Canyon4,197-1,402
Brushy Canyon5,424-2,629
Bone SpringBONE SPRINGS7,011-4,216
Wolfcamp10,148-7,353
AtokaATOKA - HIGH PRESSURE——
Delaware——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
10,13314,908Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37586217.5765 S
9.6253,25412.25600 S
9.6253,49612.25600 S
711,4058.75895 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. 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
00Aug 5, 2019May 14, 2019Yes
00Jun 9, 2017Apr 5, 2017Yes

Well logs

2 logs loaded from the RRC's log index, 2 of them with a digital LAS file, the latest received Aug 23, 2019. While drilling (MWD). These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Measure While Drilling (MWD)Spans Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring, WolfcampLAS + TIFF1,137 to 15,085Aug 23, 20190.76 + 33.8
Measure While Drilling (MWD)Spans Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring, WolfcampLAS + TIFF2,500 to 15,085Apr 24, 20190.76 + 13.8

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30132970, documented in the API reference.