WELL · 42-235-33864 · DISTRICT 7

Sugg 1896 #1

Plugged

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

Sugg 1896 #1 (API 42-235-33864) is a plugged well in Irion County, plugged April 19, 2011, last operated by Dove Creek Energy Inc..

The RRC has issued one drilling permit, issued April 9, 2003, permitted to 6,800 ft.

It was permitted by Samson Lone Star, LLC and has since transferred to Dove Creek Energy Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Clear Fork, T/Wolfcamp, Canyon.

Its lease has reported 10.8K barrels of oil and 27.3K mcf of gas since May 2003, last reporting in October 2011.

Operator of record

Dove Creek Energy Inc.

Permitted by Samson Lone Star, LLC; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Mar 4, 2026 · 18 permits on file · (713) 254-0978

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDove Creek Energy Inc.
Production reportsOXY USA Inc.through May 2010
Latest permitSamson Lone Star, LLCApr 9, 2003

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

6,800
total depth, ft
1
permits on file
Apr 9, 2003
last permit issued
May 24, 2003
completed
10.8K
cumulative oil, bbl
27.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2003 THROUGH Oct 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 24, 2003
Shut in
—
Plugged
Apr 19, 2011

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
Sugg "1896" O-9-15390Andrew A. (Canyon)Dove Creek Energy, Inc.110.8K27.3KMay 2003 – Oct 2011

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. 1TXP, IncorporatedMay 2003 → Dec 2003
  2. 2Pogo Producing CompanyJan 2004 → Jan 2008
  3. 3Pogo Producing Company LLCFeb 2008 → Feb 2008
  4. 4OXY USA Inc.Mar 2008 → Mar 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
530498-99DrillSamson Lone Star, LLCApr 9, 2003Apr 9, 2003Apr 23, 20036,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-15390————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK3,240-1,071
T/Wolfcamp4,746-2,577
Canyon6,400-4,231

Perforations

Perforated and open-hole intervals.

FromToType
6,4046,508Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62543811200 S
4.56,6007.875425 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
00Jun 18, 2003May 30, 2003Yes
00Jun 10, 2003——

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