WELL · 42-465-30724 · DISTRICT 1

Cauthorn 3 #4

Y

Val Verde County · Vinegarone (Strawn) field · Producing  · Vertical

Cauthorn 3 #4 (API 42-465-30724) is a well in Val Verde County operated by Three Forks Resources LLC, completed December 17, 2004 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 24, 2004, permitted to 10,500 ft.

It was permitted by Thompson, J. Cleo and has since transferred to Three Forks Resources LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Adwell, Jo Nell, Strawn.

No lease production has been reported under this well’s leases.

Operator of record

Three Forks Resources LLC

Permitted by Thompson, J. Cleo; the EWA schedule now lists a different operator.

Wheat Ridge, CO · P-5 Y, filed Jun 4, 2026 · (406) 539-3997

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleThree Forks Resources LLC
Production reportsThree Forks Resources, LLCthrough Mar 2026
Latest permitThompson, J. CleoAug 24, 2004

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

10,500
total depth, ft
1
permits on file
Aug 24, 2004
last permit issued
Dec 17, 2004
completed
0
cumulative oil, bbl
2.45M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 17, 2004
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cauthorn 3 G-1-207229Vinegarone (Strawn)Three Forks Resources, LLC102.45MDec 2004 – Jul 2026

Gas, mcf lease total

Last 12 months 7,363 · prior 12 8,316(-11%)

01K2K3K202420252026

Chain of custody

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

  1. 1Thompson, J. CleoDec 2004 → Sep 2020
  2. 2BRP Energy, LLCOct 2020 → Apr 2022
  3. 3Three Forks Resources, LLCMay 2022 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
542770-99DrillThompson, J. CleoMar 3, 2004Aug 24, 2004Oct 17, 200410,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-207229————

Formation tops

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

FormationMD ftSubsea
Adwell8,005-5,990
JO Nell8,604-6,589
Strawn9,515-7,500

Perforations

Perforated and open-hole intervals.

FromToType
9,7749,909Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37589617.5970 S
8.6253,00111650 S
4.510,0997.875585 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
00Aug 5, 2005Jan 31, 2005—
00Jul 20, 2005Jan 31, 2005Yes
00Apr 4, 2005——

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