WELL · 42-151-32744 · DISTRICT 7

Gannaway C #22

Y

Fisher County · Keeler-Wimberly (Canyon Sd.) field · Shut IN  · Vertical

Gannaway C #22 (API 42-151-32744) is a well in Fisher County operated by Double M Petroproperties Inc., completed January 15, 2009 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued October 23, 2008, permitted to 4,999 ft.

It was permitted by Titan Energy, Inc. and has since transferred to Double M Petroproperties Inc. on the wellbore schedule.

Completion filings report one formation top, including Canyon.

Its lease has reported 22.5K barrels of oil and 60.9K mcf of gas since January 2009, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Double M Petroproperties Inc.

Permitted by Titan Energy, Inc.; the EWA schedule now lists a different operator.

Haskell, TX · P-5 Y, filed Nov 4, 2025 · 110 permits on file · (325) 201-4788

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDouble M Petroproperties Inc.
Production reportsTitan Energy, Inc.through Nov 2015
Latest permitTitan Energy, Inc.Oct 23, 2008

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

4,999
total depth, ft
1
permits on file
Oct 23, 2008
last permit issued
Jan 15, 2009
completed
22.5K
cumulative oil, bbl
60.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 15, 2009
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gannaway "C" O-8-30256Keeler-Wimberly (Canyon Sd.)Double M Petroproperties, Inc.222.5K60.9KJan 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. 1Titan Energy, Inc.Jan 2009 → Nov 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
673449-99DrillTitan Energy, Inc.Oct 20, 2008Oct 23, 2008Dec 12, 20084,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-30256————

Formation tops

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

FormationMD ftSubsea
Canyon4,382-2,590

Perforations

Perforated and open-hole intervals.

FromToType
4,3824,392Perforated
4,4404,458Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62516012.25120 S
4.54,5077.875775 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
00Apr 8, 2009Jan 30, 2009Yes
00Feb 17, 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/15132744, documented in the API reference.