TEXAS · WELLS · MIDLAND COUNTY · SCHARBAUER C 36/37 F LEASE · API 42-329-41098 · DISTRICT 08

Scharbauer C 36/37 F #3632H

Permitted

Midland County  · Horizontal

Scharbauer C 36/37 F #3632H (API 42-329-41098) is a horizontal well in Midland County operated by Chevron U. S. A. Inc., completed June 1, 2017.

The RRC has issued one drilling permit (amended once), issued August 4, 2016, permitted to 11,000 ft.

Completion filings report 9 formation tops, including Santa Rosa, Yates, Seven Rivers, Queen.

Its lease has reported 296K barrels of oil and 622K mcf of gas since June 2017, last reporting in July 2026.

Operator of record

Chevron U. S. A. Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Jan 30, 2026
Permits on file
9,293
Phone
(866) 212-1212

SOURCE · LATEST PERMIT (NO EWA RECORD)

What each RRC source says

Wellbore scheduleChevron U. S. A. Inc.
Production reportsChevron U. S. A. Inc.through Apr 2026
Latest permitChevron U. S. A. Inc.Aug 4, 2016
11,000
total depth, ft
2
permits on file
Aug 4, 2016
last permit issued
—
completed
296K
cumulative oil, bbl
622K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2017 THROUGH Jul 2026

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
Scharbauer C 36/37 F O-10-49456Parks (Consolidated)Chevron U. S. A. Inc.1296K622KJun 2017 – Jul 2026

Gas, mcf lease total

Last 12 months 116,600 · prior 12 61,065(+91%)

010K20K30K202420252026

Oil, barrels lease total

Last 12 months 6,548 · prior 12 14,051(-53%)

01K2K202420252026

Chain of custody

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

  1. 1Chevron U. S. A. Inc.Jun 2017 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
817218-98DrillChevron U. S. A. Inc.Aug 25, 2016Aug 4, 2016Jan 13, 201711,000
817218-99DrillChevron U. S. A. Inc.Jul 21, 2016Aug 4, 2016Jan 13, 201711,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 1, 2017Scharbauer C 36/37 F O-10-49456Parks (Consolidated)Chevron U. S. A. Inc.Producing9,554

Formation tops

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

FormationMD ftSubsea
Santa Rosa9821,816
Yates2,799-1
Seven Rivers3,132-334
Queen3,926-1,128
Grayburg4,618-1,820
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO4,981-2,183
Glorieta6,099-3,301
Clear ForkCLEARFORK7,000-4,202
Spraberry8,385-5,587
SpraberrySPRABERRY UPPER-DEAN9,164-6,366

Perforations

Perforated and open-hole intervals.

FromToType
9,77316,373Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37539517.5450 S
9.6255,95812.251,490 S
516,5516.251,119 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
00Jan 15, 2025Nov 4, 2024—
00Mar 2, 2018Nov 29, 2017Yes

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