WELL · 42-461-31754 · DISTRICT 7

Hanks B #2

Plugged

Upton County · Spraberry (Trend Area) field  · Vertical

Hanks B #2 (API 42-461-31754) is a plugged well in Upton County, plugged December 27, 1991, last operated by Smith Bros. Casing Pullers Inc..

The RRC has issued one drilling permit, issued April 8, 1981, permitted to 9,300 ft.

It was permitted by Saxon Oil Company and has since transferred to Smith Bros. Casing Pullers Inc. on the wellbore schedule.

Its 2 leases have reported 31.3K barrels of oil and 75K mcf of gas since January 1993, last reporting in February 2023. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Smith Bros. Casing Pullers Inc.

Permitted by Saxon Oil Company; the EWA schedule now lists a different operator.

Midland, TX · P-5 Inactive, filed May 5, 1998 · (432) 683-9722

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSmith Bros. Casing Pullers Inc.
Production reportsParsley Energy Operations, LLCthrough Jun 2015
Latest permitSaxon Oil CompanyApr 8, 1981

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

9,300
total depth, ft
1
permits on file
Apr 8, 1981
last permit issued
Jul 1, 1982
completed
31.3K
cumulative oil, bbl
75K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 1, 1982
Shut in
—
Plugged
Dec 27, 1991

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hanks "B" O-9-9577Spraberry (Trend Area)Pioneer Natural Res. USA, Inc.231.3K75KJan 1993 – Feb 2023
— O-9-13159——000—

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. 1Hallwood Energy CorporationJan 1993 → Nov 1994
  2. 2Hallwood Petroleum, Inc.Dec 1994 → Dec 2001
  3. 3Hec Petroleum, Inc.Jan 2002 → Mar 2006
  4. 4Chevron Midcontinent, L.P.Apr 2006 → Sep 2013
  5. 5Parsley Energy Operations, LLCOct 2013 → Jun 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
114269-99DrillSaxon Oil CompanyApr 8, 1981Apr 8, 1981Apr 10, 19829,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-9577————
—— O-9-13159————

Perforations

Perforated and open-hole intervals.

FromToType
7,4658,951Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37545017.5450 S
8.6254,55011200 S
2.3758,499——
4.59,1507.875700 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
00Jan 12, 1984Jul 8, 1982—

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) and the University Lands library. 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/46131754, documented in the API reference.