WELL · 42-093-31523 · DISTRICT 9

Riley #1

Plugged

Comanche County · Newark East (Barnett Shale) field  · Vertical

Riley #1 (API 42-093-31523) is a plugged well in Comanche County, plugged January 31, 2024, last operated by Allgood Oil And Gas LLC.

The RRC has issued one drilling permit (amended once), issued August 8, 2005, permitted to 3,100 ft.

It was permitted by Infinity Oil & Gas Of TX, Inc. and has since transferred to Allgood Oil And Gas LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Marble Falls, Barnett, Ellenburger.

Operator of record

Allgood Oil and Gas LLC

Permitted by Infinity Oil & Gas of TX, Inc.; the EWA schedule now lists a different operator.

Weatherford, TX · P-5 Y, filed Feb 4, 2026 · (254) 631-1021

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAllgood Oil and Gas LLC
Production reportsHale Drilling & Production, Incthrough Apr 2017
Latest permitInfinity Oil & Gas of TX, Inc.Aug 8, 2005

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

3,100
total depth, ft
2
permits on file
Aug 8, 2005
last permit issued
May 22, 2006
completed
0
cumulative oil, bbl
7.11K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 22, 2006
Shut in
—
Plugged
Jan 31, 2024

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
Riley G-13-222204Newark, East (Barnett Shale)Allgood Oil and Gas, LLC107.11KMay 2006 – 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. 1Infinity Oil & Gas of TX, Inc.May 2006 → Jun 2007
  2. 2Hale Drilling & Production, IncJun 2011 → Apr 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
604209-98DrillInfinity Oil & Gas of TX, Inc.Oct 11, 2006Aug 8, 2005Apr 10, 20063,100
604209-99DrillInfinity Oil & Gas of TX, Inc.Jul 29, 2005Aug 8, 2005—2,870

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-222204————

Formation tops

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

FormationMD ftSubsea
Marble FallsUPPER MARBLE FALLS2,477-1,123
Marble FallsLOWER MARBLE FALLS2,674-1,320
Barnett2,850-1,496
Ellenburger2,955-1,601

Perforations

Perforated and open-hole intervals.

FromToType
2,8602,870Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62540512.25225 S
4.53,0067.875190 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
00Mar 21, 2007Aug 23, 2006Yes
00Nov 28, 2006——

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