WELL · 42-291-32556 · DISTRICT 3

Humphreys #2

N

Liberty County · Hardin SW. (H. Daniel Sand) field  · Directional

Humphreys #2 (API 42-291-32556) is a well in Liberty County operated by Smith Production Inc., completed October 10, 2004.

The RRC has issued 2 drilling permits (amended once) between 2004 and 2006, permitted to 11,000 ft.

Its 2 leases have reported 9.74K barrels of oil and 2.59M mcf of gas since October 2004, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Smith Production Inc.

Based in
The Woodlands, TX
P-5 status
Active (A)
P-5 last filed
Nov 12, 2025
Permits on file
433
Phone
(281) 296-5600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSmith Production Inc.
Production reportsApache Corporationthrough Aug 2011
Latest permitSmith Production Inc.Sep 6, 2006

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

11,000
total depth, ft
3
permits on file
Sep 6, 2006
last permit issued
Oct 10, 2004
completed
9.74K
cumulative oil, bbl
2.59M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 10, 2004
Shut in
—
Plugged
—

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
Humphreys O-3-24926Hardin, SW. (Cook Mountain #1)Hughes Oil Operating, LLC19.74K30KJul 2006 – Jul 2026
Humphreys G-3-206426Hardin, SW. (H. Daniel Sand)Smith Production Inc.102.56MOct 2004 – Sep 2006

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. 1Smith Production Inc.Nov 2004 → Dec 2006
  2. 2Edge Petroleum Oper. Co., Inc.Jan 2007 → Nov 2010
  3. 3Apache CorporationDec 2010 → Aug 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
625293-99RecompletionSmith Production Inc.Aug 31, 2006Sep 6, 2006Jun 30, 20069,252
550830-98DrillSmith Production Inc.Sep 13, 2004Sep 10, 2004Sep 13, 200411,000
550830-99DrillSmith Production Inc.Sep 10, 2004Sep 10, 2004—11,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-206426————
—— O-3-24926————

Perforations

Perforated and open-hole intervals.

FromToType
8,8988,964Perforated
8,9819,015Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,22312.251,389 S
5.59,2528.75320 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
00May 14, 2007Jan 29, 2007—
00Apr 24, 2007Oct 10, 2006Yes
00Dec 21, 2006——
00May 9, 2005Nov 29, 2004Yes
00Feb 28, 2005——

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