WELL · 42-341-32802 · DISTRICT 10

Lane W. P. #2

Y

Moore County · Texas Hugoton field · Producing  · Vertical

Lane W. P. #2 (API 42-341-32802) is a well in Moore County operated by Pantera Energy Company, completed April 4, 2002 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 5, 2001, permitted to 4,500 ft.

It was permitted by Amoco Production Company and has since transferred to Pantera Energy Company on the wellbore schedule.

Completion filings report 4 formation tops, including Glorieta, Panhandle Lime, Panhandle/Lm Mkr, Brown Dolomite.

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

Operator of record

Pantera Energy Company

Permitted by Amoco Production Company; the EWA schedule now lists a different operator.

Amarillo, TX · P-5 Y, filed Aug 4, 2025 · 359 permits on file · (806) 673-9438

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePantera Energy Company
Production reportsPantera Energy Companythrough Apr 2026
Latest permitAmoco Production CompanyDec 5, 2001

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

4,500
total depth, ft
1
permits on file
Dec 5, 2001
last permit issued
Apr 4, 2002
completed
0
cumulative oil, bbl
429K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 4, 2002
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Lane, W. P. G-14-188958Texas HugotonPantera Energy Company10429KApr 2002 – Jul 2026

Gas, mcf lease total

Last 12 months 8,819 · prior 12 11,014(-20%)

05001K1.5K202420252026

Chain of custody

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

  1. 1BP America Production CompanyApr 2002 → Aug 2014
  2. 2Pantera Energy CompanyJan 2015 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
515843-99DrillAmoco Production CompanyDec 5, 2001Dec 5, 2001Mar 20, 20024,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-188958————

Formation tops

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

FormationMD ftSubsea
Glorieta1,1352,348
Panhandle Lime2,580903
Panhandle/LM MKR2,985498
Brown Dolomite3,138345

Perforations

Perforated and open-hole intervals.

FromToType
3,0113,215Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62557112.25291 S
5.53,0117.875145 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
00Jul 10, 2002May 30, 2002Yes
00Jun 12, 2002——

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