WELL · 42-329-31388 · DISTRICT 8

Scharbauer #1019H

N

Midland County  · Horizontal

Scharbauer #1019H (API 42-329-31388) is a permitted horizontal well in Midland County filed by Heritage Resources, Inc.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 1984 and 2001, permitted to 13,500 ft.

Completion filings report 2 formation tops, including Strawn, Devonian.

Its 2 leases have reported 16.6K barrels of oil and 97.4K mcf of gas since January 1993, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Heritage Resources, Inc.

Dallas, TX · P-5 Y, filed Oct 3, 2008 · 54 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsHeritage Standard Corporationthrough Feb 2007
Latest permitHeritage Resources, Inc.Aug 23, 2001
13,500
total depth, ft
3
permits on file
Aug 23, 2001
last permit issued
—
completed
16.6K
cumulative oil, bbl
97.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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
Scharbauer O-10-29832Parks (Pennsylvanian)Heritage Standard Corporation116.6K97.4KJan 1993 – Jul 2026
Scharbauer O-10-29605Warfield (Strawn)Heritage Standard Corporation100Jan 1993 – Oct 2011

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. 1Heritage Resources, Inc.Jan 1993 → Oct 2001
  2. 2Heritage Standard CorporationNov 2001 → Feb 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
512915-99RecompletionHeritage Resources, Inc.Aug 23, 2001Aug 23, 2001—13,500
273462-99RecompletionHeritage Resources, Inc.Apr 29, 1985Apr 26, 1985—13,500
250428-99DrillHeritage Resources, Inc.Feb 5, 1985Sep 5, 1984—13,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-29605————
—— O-10-29832————

Formation tops

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

FormationMD ftSubsea
Strawn10,168-7,345
Devonian11,722-8,899

Perforations

Perforated and open-hole intervals.

FromToType
10,18110,189Perforated
10,50910,564Perforated
12,57912,657Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37540017.5450 S
9.6255,11312.251,925 S
713,2068.51,150 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
00Aug 31, 1985May 16, 1985Yes
00Jun 3, 1985May 16, 1985—
00May 25, 1985——
00Mar 12, 1985Feb 13, 1985—
00Mar 12, 1985Feb 4, 1985Yes
00Mar 5, 1985——

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