WELL · 42-363-33139 · DISTRICT 7

Hardoncourt A #4

Y

Palo Pinto County · Palo Pinto Co. Reg. (Gas) field · Domestic Use Well  · Vertical

Hardoncourt A #4 (API 42-363-33139) is a well in Palo Pinto County operated by Hardoncourt Frances D., completed October 25, 1987 and listed as domestic use well on the RRC schedule.

The RRC has issued one drilling permit, issued July 12, 1983, permitted to 2,000 ft.

It was permitted by Wes-Mor Drilling, Inc. and has since transferred to Hardoncourt Frances D. on the wellbore schedule.

Completion filings report one formation top, including Strawn.

No lease production has been reported under this well’s leases.

Operator of record

Hardoncourt Frances D.

Permitted by Wes-Mor Drilling, Inc.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 New, filed Oct 8, 1993

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHardoncourt Frances D.
Production reportsnone
Latest permitWes-Mor Drilling, Inc.Jul 12, 1983

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

2,000
total depth, ft
1
permits on file
Jul 12, 1983
last permit issued
Oct 25, 1987
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 25, 1987
Shut in
—
Plugged
—

Operator's P-5 on the schedule: S

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hardoncourt A G-8-108081Palo Pinto Co. Reg. (Gas)Hardoncourt, Frances D.100Jan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
201129-99DrillWes-Mor Drilling, Inc.Jul 12, 1983Jul 12, 1983—2,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-108081————

Formation tops

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

FormationMD ftSubsea
Strawn1,172-54

Perforations

Perforated and open-hole intervals.

FromToType
1,1721,175Perforated
1,7301,736Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62520611120 S
2.3751,650——
4.51,8536.5200 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
00Dec 30, 1987Dec 1, 1987Yes
00Jan 12, 1984Nov 29, 1983—

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

6K
bbl, last 12 reported months
11K
bbl, all reported
Apr 1985
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000050978W-14 DisposalCanceled Feb 14, 1991001,730–1,736

MONTHLY INJECTED, BBL · H-10 · LAST 10 REPORTED MONTHS

Last 12 months 11,010

01K2K19841985

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