WELL · 42-219-33691 · DISTRICT 8

Piercy Callie B #1

Plugged

Hockley County · Levelland field  · Vertical

Piercy Callie B #1 (API 42-219-33691) is a plugged well in Hockley County, plugged June 25, 2015, last operated by Momentum Operating CO. Inc..

The RRC has issued one drilling permit, issued December 14, 1982, permitted to 5,000 ft.

It was permitted by Peden, Oren Inc. and has since transferred to Momentum Operating CO. Inc. on the wellbore schedule.

Completion filings report one formation top, including San Andres.

Its lease has reported 7.14K barrels of oil and 35 mcf of gas since January 1993, last reporting in May 2017.

Operator of record

Momentum Operating Co. Inc.

Permitted by Peden, Oren Inc.; the EWA schedule now lists a different operator.

Albany, TX · P-5 Y, filed Jun 4, 2026 · 148 permits on file · (254) 559-7840

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMomentum Operating Co. Inc.
Production reportsMomentum Operating Co., Inc.through Apr 2013
Latest permitPeden, Oren Inc.Dec 14, 1982

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

5,000
total depth, ft
1
permits on file
Dec 14, 1982
last permit issued
Mar 26, 2015
completed
7.14K
cumulative oil, bbl
35
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2017

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 26, 2015
Shut in
—
Plugged
Jun 25, 2015

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
Piercy, Callie "B" O-11-64267LevellandMomentum Operating Co., Inc.17.14K35Jan 1993 – May 2017

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Peden, Oren Inc.Jan 1993 → May 2001
  2. 2Kala Oil CompanyJun 2001 → Aug 2003
  3. 3Peden EnergySep 2003 → Dec 2004
  4. 4Peden Energy, Inc.Jan 2005 → Nov 2012
  5. 5Momentum Operating Co., Inc.Jan 2013 → Apr 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
180163-99DrillPeden, Oren Inc.Dec 14, 1982Dec 14, 1982Jan 19, 19825,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-64267————

Formation tops

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

FormationMD ftSubsea
San Andres4,962-1,290

Perforations

Perforated and open-hole intervals.

FromToType
4,9464,956Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62546112.25350 S
2.3754,958——
4.54,9627.8751,500 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
00Apr 17, 2015Apr 13, 2015—
00Jan 12, 1984Mar 18, 1983—

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