WELL · 42-181-31208 · DISTRICT 9

Hipke Reast #1A

Shut in

Grayson County · Sandusky West (Penn.) field · Shut IN  · Vertical

Hipke Reast #1A (API 42-181-31208) is a well in Grayson County operated by Felderhoff Production Company, completed August 23, 1996 and listed as shut in on the RRC schedule, shut in January 1, 1998.

The RRC has issued 2 drilling permits between 1987 and 1996, permitted to 7,992 ft.

Completion filings report 3 formation tops, including Pennsylvanian, Foster Sand, Oil Creek.

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

Operator of record

Felderhoff Production Company

Based in
Muenster, TX
P-5 status
Active (A)
P-5 last filed
Mar 31, 2026
Permits on file
468
Phone
(940) 759-3631

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsFelderhoff Production Companythrough Apr 2026
Latest permitFelderhoff Production Co.Jul 19, 1996
7,992
total depth, ft
2
permits on file
Jul 19, 1996
last permit issued
Aug 23, 1996
completed
158K
cumulative oil, bbl
36.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1996 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 23, 1996
Shut in
Jan 1, 1998
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Hipke Reast O-13-29063Sandusky, West (Penn.)Felderhoff Production Company2158K36.4KJan 1996 – Jul 2026

Oil, barrels lease total

Last 12 months 2,628 · prior 12 2,506(+5%)

0100200300202420252026

Chain of custody

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

  1. 1Felderhoff Production CompanyJan 1996 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
450384-99ReenterFelderhoff Production Co.Jul 15, 1996Jul 19, 1996Aug 14, 19966,500
339506-99DrillFelderhoff Production Co.Dec 1, 1987Dec 3, 1987—8,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 23, 1996Hipke Reast O-13-29063Sandusky West (Penn.)Felderhoff Production CompanyShut IN · shut in Jan 1, 19987,992

Formation tops

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

FormationMD ftSubsea
PennsylvanianPENN SAND6,080-5,336
Foster Sand6,450-5,706
Oil Creek7,900-7,156

Perforations

Perforated and open-hole intervals.

FromToType
6,0806,084Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62540812.25310 S
4.56,3477.875230 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
00Sep 30, 1996Sep 16, 1996—
00Sep 20, 1996——

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