WELL · 42-399-35167 · DISTRICT 7

Ashley #1

Y

Runnels County · Paul Thomas (Goen) field · Shut IN  · Vertical

Ashley #1 (API 42-399-35167) is a well in Runnels County operated by Cedar Oil Company, completed April 6, 2009 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued March 13, 2009, permitted to 5,000 ft.

It was permitted by Sha-Jam Operating Corp. and has since transferred to Cedar Oil Company on the wellbore schedule.

Completion filings report 3 formation tops, including B/Coleman Junction, T/King Sand, T/Goen.

Its lease has reported 49K barrels of oil and 27.1K mcf of gas since April 2009, last reporting in July 2026.

Operator of record

Cedar Oil Company

Permitted by Sha-Jam Operating Corp.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Dec 4, 2025 · 76 permits on file · (325) 665-3325

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCedar Oil Company
Production reportsCedar Oil Companythrough Sep 2018
Latest permitSha-Jam Operating Corp.Mar 13, 2009

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

5,000
total depth, ft
1
permits on file
Mar 13, 2009
last permit issued
Apr 6, 2009
completed
49K
cumulative oil, bbl
27.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 6, 2009
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
Ashley O-9-16886Paul Thomas (Goen)Cedar Oil Company149K27.1KApr 2009 – Jul 2026

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. 1Sha-Jam Operating Corp.Apr 2009 → Jul 2009
  2. 2Fremont Exploration, Inc.Aug 2009 → Oct 2009
  3. 3Gaedeke Oil & Gas Operating, LLCNov 2009 → Aug 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
679213-99DrillSha-Jam Operating Corp.Mar 5, 2009Mar 13, 2009Mar 24, 20095,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-16886————

Formation tops

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

FormationMD ftSubsea
B/Coleman Junction2,058-112
T/King Sand3,018-1,072
T/Goen4,420-2,474

Perforations

Perforated and open-hole intervals.

FromToType
4,4204,422Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62523812.25150 S
5.54,4977.875200 S
5.5——450 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
00May 13, 2009Apr 15, 2009Yes
00Apr 23, 2009——

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