WELL · 42-125-30661 · DISTRICT 8

Horn #2

Plugged

Dickens County  · Vertical

Horn #2 (API 42-125-30661) is a plugged well in Dickens County, plugged October 11, 1997, last operated by T & G Energy LLC.

The RRC has issued 2 drilling permits between 1997 and 2007, permitted to 5,000 ft.

Completion filings report 3 formation tops, including Clear Fork, Cisco, Tannehill.

Its lease has reported 1.84K barrels of oil since August 2008, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

It holds an active disposal or injection permit.

Operator of record

T & G Energy LLC

Dallas, TX · P-5 Y, filed Sep 4, 2025 · 8 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsD.J.F. Services, Inc.through Dec 2021
Latest permitT & G Energy LLCJun 28, 2007
5,000
total depth, ft
2
permits on file
Jun 28, 2007
last permit issued
—
completed
1.84K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Oct 11, 1997

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
Horn O-11-69391Navigator (Tannehill B)D.J.F. Services, Inc.21.84K0Aug 2008 – 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. 1T & G Energy LLCJul 2009 → Apr 2010
  2. 2D.J.F. Services, Inc.May 2013 → Dec 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
641111-99ReenterT & G Energy LLCJun 20, 2007Jun 28, 2007Jun 29, 20075,000
466149-99DrillEastern Energy CorporationAug 12, 1997Aug 12, 1997Oct 2, 19974,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-69391————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK1,840359
CiscoCISCO REEF3,900-1,701
TannehillTANNEHILL B4,444-2,245

Perforations

Perforated and open-hole intervals.

FromToType
4,4444,452Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62564012.25580 S
4.54,6097.875475 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
00Oct 16, 2015Aug 19, 2015—
00Mar 6, 2015Mar 4, 2015Yes

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
58.1K
bbl, all reported
Apr 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000112358H-1 InjectionActive7502,2224,444–4,452

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120242025

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