WELL · 42-107-30837 · DISTRICT 8

Hoople G. W. #17

Y

Crosby County · Hoople (Clear Fork) field · Producing  · Vertical

Hoople G. W. #17 (API 42-107-30837) is a well in Crosby County operated by Chi Operating Inc., completed August 29, 1985 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 25, 1985, permitted to 4,600 ft.

It was permitted by Duncan Drilling CO. and has since transferred to Chi Operating Inc. on the wellbore schedule.

Completion filings report one formation top, including Clear Fork.

Its lease has reported 537K barrels of oil and 196 mcf of gas since January 1993, last reporting in July 2026. The lease carries 11 wells, so these are lease totals, not this well alone.

Operator of record

Chi Operating Inc.

Permitted by Duncan Drilling Co.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Apr 4, 2026 · 126 permits on file · (432) 557-8773

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChi Operating Inc.
Production reportsChi Operating, Inc.through Apr 2026
Latest permitDuncan Drilling Co.Jun 25, 1985

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

4,600
total depth, ft
1
permits on file
Jun 25, 1985
last permit issued
Aug 29, 1985
completed
537K
cumulative oil, bbl
196
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 29, 1985
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hoople, G. W. O-11-61664Hoople (Clear Fork)Chi Operating, Inc.11537K196Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 17,678 · prior 12 18,836(-6%)

01K2K202420252026

Chain of custody

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

  1. 1Duncan Drilling Co.Jan 1993 → Aug 2024
  2. 2Chi Operating, Inc.Sep 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
278715-99DrillDuncan Drilling Co.Jun 24, 1985Jun 25, 1985Aug 16, 19854,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-61664————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK4,410-1,344

Perforations

Perforated and open-hole intervals.

FromToType
4,4104,440Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62531611275 S
4.54,5707.875450 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 4, 1985Sep 23, 1985Yes
00Oct 1, 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/10730837, documented in the API reference.