TEXAS · WELLS · ANDREWS COUNTY · API 42-003-03720 · DISTRICT 7B

Peay Tom #1

Plugged

Andrews County · Nolley (Wolfcamp) field  · Vertical

Peay Tom #1 (API 42-003-03720) is a plugged well in Andrews County, plugged December 2, 1988, last operated by Crescent Energy Operating LLC.

The RRC has issued 2 drilling permits between 1986 and 1988, permitted to 14,000 ft.

It was permitted by Mobil Producing TX. & N.M. Inc. and has since transferred to Crescent Energy Operating LLC on the wellbore schedule.

Operator of record

Crescent Energy Operating LLC

Permitted by Mobil Producing TX. & N.M. Inc.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Aug 28, 2025
Permits on file
54
Phone
(713) 337-4600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCrescent Energy Operating LLC
Production reportsnone
Latest permitMobil Producing TX. & N.M. Inc.Jan 11, 1988

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

14,000
total depth, ft
2
permits on file
Jan 11, 1988
last permit issued
Mar 30, 1988
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 30, 1988
Shut in
—
Plugged
Dec 2, 1988

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.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
341276-99RecompletionMobil Producing TX. & N.M. Inc.Jan 11, 1988Jan 11, 1988—14,000
322667-99RecompletionMobil Producing TX. & N.M. Inc.Nov 3, 1986Nov 4, 1986—14,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 30, 1988Peay Tom O-10-4533Nolley (Wolfcamp)Crescent Energy Operating LLCPlugged—
—Peay Tom O-10-4533Nolley (Wolfcamp)Crescent Energy Operating LLCPlugged—
—Peay Tom O-10-4533Nolley (Wolfcamp)Crescent Energy Operating LLCPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
8,1768,194Perforated
9,2279,300Perforated
—9,227Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.375365—375 S
9.6255,192—400 S
7.6255,192—400 S
2.3759,136——
79,309—1,425 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
00May 9, 1988Apr 21, 1988Yes
00Apr 6, 1988Mar 21, 1988—
00Jan 12, 1984Aug 14, 1959—
00Jan 12, 1984——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.

Find logs withinmiles of this well:List →Map →

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
1.28M
bbl, all reported
Jun 1991
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000018973H-1 InjectionPlugged Jan 25, 19893,0001,6009,227–9,800

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0119901991

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