WELL · 42-263-32009 · DISTRICT 8

Double Mountain 57 #1

Y

Kent County · Double Mountain (Canyon Sand) field · Water Supply  · Vertical

Double Mountain 57 #1 (API 42-263-32009) is a well in Kent County operated by Sharp Image Energy Inc., completed March 23, 2018 and listed as water supply on the RRC schedule.

The RRC has issued one drilling permit, issued May 14, 2012, permitted to 7,700 ft.

Completion filings report 3 formation tops, including Stockwether, Noodle Creek, Canyon.

Its lease has reported 6.87K barrels of oil since July 2012, last reporting in July 2026.

Operator of record

Sharp Image Energy Inc.

Big Spring, TX · P-5 Active, filed Jul 16, 2026 · 665 permits on file · (432) 267-3126

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSharp Image Energy Inc.
Production reportsSharp Image Energy, Inc.through Jan 2016
Latest permitSharp Image Energy, Inc.May 14, 2012
7,700
total depth, ft
1
permits on file
May 14, 2012
last permit issued
Mar 23, 2018
completed
6.87K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 23, 2018
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
Double Mountain 57 O-11-69912Double Mountain (Canyon Sand)Sharp Image Energy, Inc.16.87K0Jul 2012 – 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. 1Sharp Image Energy, Inc.Aug 2012 → Jan 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
739677-99DrillSharp Image Energy, Inc.May 1, 2012May 14, 2012May 20, 20127,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-69912————

Formation tops

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

FormationMD ftSubsea
Stockwether4,265-2,140
Noodle Creek4,568-2,443
CanyonCANYON MARKER5,860-3,735
CanyonCANYON "B" SS6,011-3,886
CanyonCANYON "C" SS6,052-3,927
CanyonCANYON "D" SS6,192-4,067

Perforations

Perforated and open-hole intervals.

FromToType
6,0196,023Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531917.5375 S
8.6251,833111,175 S
5.56,2887.875800 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
00Dec 21, 2018Oct 9, 2018—
00Jan 31, 2013Jul 24, 2012Yes

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000112099H-1 InjectionNot activated5,0003,0056,010–6,220

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