WELL · 42-049-35787 · DISTRICT 7

Hathcock #2

Plugged

Brown County · Brown County Regular field  · Vertical

Hathcock #2 (API 42-049-35787) is a plugged well in Brown County, plugged December 9, 2022, last operated by K & W Vanpelt Company.

The RRC has issued one drilling permit, issued April 25, 2002, permitted to 2,350 ft.

It was permitted by Weller Production and has since transferred to K & W Vanpelt Company on the wellbore schedule.

Completion filings report one formation top, including Caddo.

Its lease has reported 1.02K barrels of oil and 20 mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

K & W Vanpelt Company

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

Portage, OH · P-5 Y, filed May 29, 2025 · 2 permits on file · (325) 636-3272

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleK & W Vanpelt Company
Production reportsMole Hole Prod.through Aug 2015
Latest permitWeller ProductionApr 25, 2002

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

2,350
total depth, ft
1
permits on file
Apr 25, 2002
last permit issued
Sep 15, 2002
completed
1.02K
cumulative oil, bbl
20
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 15, 2002
Shut in
—
Plugged
Dec 9, 2022

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hathcock O-8-16457Brown County RegularK & W Vanpelt Company21.02K20Jan 1993 – Jul 2026

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. 1Hathcock, R. F.Jan 1993 → May 2001
  2. 2Weller ProductionJun 2001 → Jun 2001
  3. 3Mullin Oil & Gas LLCJan 2010 → Oct 2010
  4. 4Eagle Energy CorporationNov 2010 → Oct 2011
  5. 5Red Dog Track, Inc.Nov 2011 → Jun 2015
  6. 6Mole Hole Prod.Jul 2015 → Aug 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
518912-99DrillWeller ProductionApr 8, 2002Apr 25, 2002Aug 16, 20022,350

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-16457————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Caddo1,705

Perforations

Perforated and open-hole intervals.

FromToType
1,7071,709Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251001155 S
4.51,7626.7570 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
00Mar 6, 2003Sep 18, 2002Yes
00Feb 6, 2003——

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