WELL · 42-495-32242 · DISTRICT 8

Hondo-7- #2

Plugged

Winkler County · Kermit field  · Vertical

Hondo-7- #2 (API 42-495-32242) is a plugged well in Winkler County, plugged May 17, 1995, last operated by Custer & Wright Operating Inc..

The RRC has issued one drilling permit (amended once), issued January 11, 1989, permitted to 2,900 ft.

It was permitted by Hillin-Simon Oil Company and has since transferred to Custer & Wright Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Tansill, Yates.

Its lease has reported 294 barrels of oil and 9.67K mcf of gas since January 1993, last reporting in June 1995.

Operator of record

Custer & Wright Operating Inc.

Permitted by Hillin-Simon Oil Company; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Aug 4, 2025 · 249 permits on file · (432) 687-1565

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCuster & Wright Operating Inc.
Production reportsCuster & Wright Operating, Inc.through May 1995
Latest permitHillin-Simon Oil CompanyJan 11, 1989

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

2,900
total depth, ft
2
permits on file
Jan 11, 1989
last permit issued
Apr 12, 1989
completed
294
cumulative oil, bbl
9.67K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 12, 1989
Shut in
—
Plugged
May 17, 1995

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
Hondo-7- O-10-32260KermitCuster & Wright Operating, Inc.12949.67KJan 1993 – Jun 1995

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. 1Hillin-Simon Oil CompanyJan 1993 → Oct 1993
  2. 2Custer & Wright Operating, Inc.Nov 1993 → Apr 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
355028-98DrillHillin-Simon Oil CompanyMay 16, 1989Jan 11, 1989—2,900
355028-99DrillHillin-Simon Oil CompanyJan 10, 1989Jan 11, 1989Jan 20, 19892,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-32260————

Formation tops

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

FormationMD ftSubsea
Tansill2,370478
Yates2,484364

Perforations

Perforated and open-hole intervals.

FromToType
2,5082,764Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62561412.25350 S
4.52,8507.875260 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
00Jun 8, 1989May 15, 1989Yes
00Jun 1, 1989——

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) and the University Lands library. 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/49532242, documented in the API reference.