TEXAS · WELLS · LOVING COUNTY · MOCAP 56-T1-25 LEASE · API 42-301-32298 · DISTRICT 7B

Mocap 56-T1-25 #1H

Y

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

Mocap 56-T1-25 #1H (API 42-301-32298) is a horizontal well in Loving County operated by Bpx Operating Company, completed January 24, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 30, 2014, permitted to 11,048 ft.

It was permitted by Bhp Billiton Pet(Txla OP) CO and has since transferred to Bpx Operating Company on the wellbore schedule.

Completion filings report 9 formation tops, including Delaware, Lamar, Bell Canyon, Red Bluff.

Its lease has reported 395K barrels of oil and 1.58M mcf of gas since January 2015, last reporting volume in April 2026.

Operator of record

BPX Operating Company

Permitted by BHP Billiton Pet(txla OP) Co; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Active – Extension (X)
P-5 last filed
Jun 24, 2026
Permits on file
1,576
Phone
(720) 439-5104

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBPX Operating Company
Production reportsBPX Operating Companythrough Apr 2026
Latest permitBHP Billiton Pet(txla OP) CoAug 30, 2014

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

11,048
total depth, ft
1
permits on file
Aug 30, 2014
last permit issued
Jan 24, 2015
completed
395K
cumulative oil, bbl
1.58M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2015 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 24, 2015
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
Mocap 56-T1-25 G-10-281029Phantom (Wolfcamp)BPX Operating Company1395K1.58MJan 2015 – Apr 2026

Gas, mcf lease total

Last 12 months 73,708 · prior 12 80,601(-9%)

05K10K15K202420252026

Chain of custody

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

  1. 1BHP Billiton Pet(txla OP) CoJan 2015 → Jul 2019
  2. 2BPX Operating CompanyAug 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
793104-99DrillBHP Billiton Pet(txla OP) CoJul 31, 2014Aug 30, 2014Sep 30, 201414,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 24, 2015Mocap 56-T1-25 G-10-281029Phantom (Wolfcamp)BPX Operating CompanyProducing11,048

Formation tops

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

FormationMD ftSubsea
Delaware3,000-46
Lamar3,601-647
Bell Canyon3,636-682
Red Bluff3,900-946
Bell Canyon3,936-982
Cherry Canyon4,521-1,567
Brushy Canyon6,038-3,084
Bone SpringBONE SPRINGS7,514-4,560
AvalonMIDDLE AVALON LIMESTONE8,073-5,119
Base Avalaon Shale8,460-5,506
AvalonBASE AVALON SHALE8,460-5,506
Bone Spring2ND BONE SPRING SAND9,054-6,100
Bone Spring3RD BONE SPRING10,280-7,326

Perforations

Perforated and open-hole intervals.

FromToType
11,12016,256Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
11.751,00814.751,362 S
9.6254,99310.625470 S
710,7068.75622 S
516,4476.25872 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
00Apr 12, 2017Jan 17, 2017Yes
00Oct 20, 2016Jan 29, 2016Yes

Well logs

3 logs loaded from the RRC's log index, the latest received Jan 2, 2019. Gamma ray, 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
Gamma RaySpans Delaware, Lamar, Bell Canyon, Red Bluff, Cherry Canyon, Brushy Canyon, Bone Spring, Avalon, Base Avalaon ShaleTIFF0 to 10,894Jan 2, 20190.86
Gamma RaySpans Brushy Canyon, Bone Spring, Avalon, Base Avalaon ShaleTIFF6,500 to 16,461Dec 4, 20180.69
Measure While Drilling (MWD)Spans Cherry Canyon, Brushy Canyon, Bone Spring, Avalon, Base Avalaon ShaleTIFF5,058 to 16,461Oct 20, 201723.5

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