WELL · 42-135-07517 · DISTRICT 8

Kloh D-9 #2

N

Ector County  · Vertical

Kloh D-9 #2 (API 42-135-07517) is a permitted well in Ector County filed by Stanolind Operating LLC; no completion report is on file yet.

The RRC has issued 2 drilling permits between 2009 and 2013, permitted to 6,000 ft.

Completion filings report 3 formation tops, including Yates, San Andres, Clear Fork.

Its 2 leases have reported 39.6K barrels of oil and 72.1K mcf of gas since January 1993, last reporting in September 2025. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Stanolind Operating LLC

Midland, TX · P-5 Y, filed Jan 6, 2017 · 53 permits on file · (432) 425-7411

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsMemorial Production Oper. LLCthrough Jun 2015
Latest permitStanolind Operating LLCApr 19, 2013
6,000
total depth, ft
2
permits on file
Apr 19, 2013
last permit issued
—
completed
39.6K
cumulative oil, bbl
72.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2025

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Kloh D-9 O-10-18563Goldsmith, N. (San Andres, Con.)Boaz Energy II Operating, LLC230.7K42KJan 1993 – Sep 2025
Kloh D-9 O-10-39714Goldsmith (Clear Fork)Boaz Energy II Operating, LLC18.93K30.1KOct 2009 – Sep 2025

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. 1Conoco Inc.Jan 1993 → Jan 1995
  2. 2Floyd Operating CompanyFeb 1995 → Jun 1997
  3. 3M & J Energy, Inc.Jul 1997 → Nov 2012
  4. 4Stanolind Operating LLCDec 2012 → Sep 2013
  5. 5Memorial Production Oper. LLCOct 2013 → Jun 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
760865-99RecompletionStanolind Operating LLCApr 16, 2013Apr 19, 2013—5,950
684686-99RecompletionM & J Energy, Inc.Sep 1, 2009Sep 9, 2009Sep 18, 20096,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-18563————
—— O-10-39714————

Formation tops

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

FormationMD ftSubsea
Yates2,796542
San Andres4,205-867
Clear ForkCLEARFORK5,510-2,172

Perforations

Perforated and open-hole intervals.

FromToType
5,5085,877Perforated
—4,500Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.625318—175 S
5.54,3997.875475 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
00Mar 22, 2010Oct 28, 2009Yes
00Feb 22, 2010——
00Jan 12, 1984——

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