WELL · 42-295-32513 · DISTRICT 10

Piper Ola P. #6321

Shut in

Lipscomb County · Lipscomb (Cleveland) field · Temp Abandoned  · Vertical

Piper Ola P. #6321 (API 42-295-32513) is a well in Lipscomb County operated by Highmark Energy Operating LLC, completed December 14, 1999 and listed as temp abandoned on the RRC schedule, shut in October 1, 2024.

The RRC has issued one drilling permit, issued September 8, 1999, permitted to 10,300 ft.

It was permitted by Manti Operating Company and has since transferred to Highmark Energy Operating LLC on the wellbore schedule.

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

Operator of record

Highmark Energy Operating LLC

Permitted by Manti Operating Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Mar 9, 2026
Permits on file
23
Phone
(469) 214-5299

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHighmark Energy Operating LLC
Production reportsHighmark Energy Operating, LLCthrough Sep 2024
Latest permitManti Operating CompanySep 8, 1999

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

10,300
total depth, ft
1
permits on file
Sep 8, 1999
last permit issued
Dec 14, 1999
completed
0
cumulative oil, bbl
451K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 14, 1999
Shut in
Oct 1, 2024
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
Piper, Ola P. G-14-178621Lipscomb (Cleveland)Highmark Energy Operating, LLC10451KDec 1999 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 1,551(-100%)

05001K1.5K202420252026

Chain of custody

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

  1. 1Exxon Mobil CorporationMay 2000 → Jun 2013
  2. 2XTO Energy Inc.Jul 2013 → Sep 2022
  3. 3Highmark Energy Operating, LLCOct 2022 → Sep 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
487369-99DrillManti Operating CompanySep 8, 1999Sep 8, 1999Sep 15, 199911,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 14, 1999Piper Ola P. G-14-178621Lipscomb (Cleveland)Highmark Energy Operating LLCTemp Abandoned · shut in Oct 1, 202410,300

Perforations

Perforated and open-hole intervals.

FromToType
7,7727,792Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,82011563 S
4.510,2807.875630 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
00Oct 26, 2000Sep 11, 2000Yes
00Sep 29, 2000——

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