WELL · 42-235-35783 · DISTRICT 7

Cravens 18 #2

Y

Irion County · Andrew A. (Canyon) field · Producing  · Vertical

Cravens 18 #2 (API 42-235-35783) is a well in Irion County operated by Thp Operating LLC, completed May 29, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued April 16, 2014, permitted to 7,000 ft.

It was permitted by Txp, Incorporated and has since transferred to Thp Operating LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Grayburg, San Andres, Clear Fork, Spraberry.

Its lease has reported 7.58K barrels of oil and 22.5K mcf of gas since May 2014, last reporting in July 2026.

Operator of record

THP Operating LLC

Permitted by TXP, Incorporated; the EWA schedule now lists a different operator.

Santa Anna, TX · P-5 Y, filed Mar 4, 2026 · (325) 656-0788

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleTHP Operating LLC
Production reportsTHP Operating LLCthrough Apr 2026
Latest permitTXP, IncorporatedApr 16, 2014

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

7,000
total depth, ft
1
permits on file
Apr 16, 2014
last permit issued
May 29, 2014
completed
7.58K
cumulative oil, bbl
22.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 29, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Cravens 18 O-9-18537Andrew A. (Canyon)THP Operating LLC17.58K22.5KMay 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 16 · prior 12 4(+300%)

0246202420252026

Chain of custody

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

  1. 1TXP, IncorporatedJun 2014 → Jun 2019
  2. 2THP Operating LLCSep 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
783374-99DrillTXP, IncorporatedMar 28, 2014Apr 16, 2014Apr 21, 20147,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-18537————

Formation tops

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

FormationMD ftSubsea
Grayburg9301,352
San Andres1,510772
Clear ForkCLEARFORK2,310-28
Spraberry3,280-998
Wolfcamp5,050-2,768
Canyon6,270-3,988
Fusselman——

Perforations

Perforated and open-hole intervals.

FromToType
6,4726,503Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535311150 S
5.56,6147.875350 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
00Jul 30, 2014Jun 27, 2014Yes

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