WELL · 42-163-32956 · DISTRICT 1

Hildebrand Ira P. #3

Plugged

Frio County · Pearsall (Austin Chalk) field  · Horizontal

Hildebrand Ira P. #3 (API 42-163-32956) is a plugged horizontal well in Frio County, plugged June 4, 2003, last operated by Hec Petroleum Inc..

The RRC has issued one drilling permit, issued January 28, 1991, permitted to 8,625 ft.

It was permitted by Exxon Corp. and has since transferred to Hec Petroleum Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Midway, Olmos, Anacacho, Austin Chalk.

Its lease has reported 128K barrels of oil and 35.4K mcf of gas since January 1993, last reporting in August 2003. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Hec Petroleum Inc.

Permitted by Exxon Corp.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Mar 3, 2006

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHec Petroleum Inc.
Production reportsHec Petroleum, Inc.through Dec 2002
Latest permitExxon Corp.Jan 28, 1991

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

8,625
total depth, ft
1
permits on file
Jan 28, 1991
last permit issued
May 23, 1991
completed
128K
cumulative oil, bbl
35.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 23, 1991
Shut in
—
Plugged
Jun 4, 2003

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hildebrand, Ira P. O-1-12501Pearsall (Austin Chalk)Hec Petroleum, Inc.3128K35.4KJan 1993 – Aug 2003

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. 1Exxon Corp.Jan 1993 → Jul 1994
  2. 2Cox Resources Corp.Aug 1994 → Aug 2000
  3. 3Hallwood Petroleum, Inc.Sep 2000 → Dec 2001
  4. 4Hec Petroleum, Inc.Jan 2002 → Dec 2002

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
382484-99DrillExxon Corp.Dec 17, 1990Jan 28, 1991Apr 20, 19918,625

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-12501————

Formation tops

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

FormationMD ftSubsea
MidwayMIDWAY SHALE3,967-3,370
OlmosOLMOS SAND5,591-4,994
Anacacho6,964-6,367
Austin Chalk7,170-6,573

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7588014.75510 S
7.6254,2599.875615 S
2.8756,8007.875—
7.625—9.875750 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
00Oct 21, 1991Sep 9, 1991Yes
00Oct 16, 1991——

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