WELL · 42-127-33748 · DISTRICT 1

Circle T #1H

Plugged

Dimmit County · Briscoe Ranch (Eagleford) field  · Horizontal

Circle T #1H (API 42-127-33748) is a plugged horizontal well in Dimmit County, plugged December 30, 2020, last operated by Sage Energy Company.

The RRC has issued one drilling permit, issued September 1, 2010, permitted to 9,000 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Sage Energy Company on the wellbore schedule.

Completion filings report 3 formation tops, including Anacacho, Austin Chalk, Eagle Ford.

Its lease has reported 22.8K barrels of oil and 144K mcf of gas since December 2010, last reporting in July 2021.

Operator of record

Sage Energy Company

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

San Antonio, TX · P-5 Y, filed Jul 4, 2026 · 1,060 permits on file · (830) 876-8583

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSage Energy Company
Production reportsSage Energy Companythrough Oct 2020
Latest permitChesapeake Operating, Inc.Sep 1, 2010

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

9,000
total depth, ft
1
permits on file
Sep 1, 2010
last permit issued
Jun 8, 2011
completed
22.8K
cumulative oil, bbl
144K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2010 THROUGH Jul 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 8, 2011
Shut in
—
Plugged
Dec 30, 2020

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
Circle T O-1-15287Briscoe Ranch (Eagleford)Sage Energy Company122.8K144KDec 2010 – Jul 2021

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. 1Chesapeake Operating, Inc.Sep 2011 → Jun 2013
  2. 2Exco Operating Company, LPJul 2013 → Nov 2018
  3. 3Sage Energy CompanyDec 2018 → Oct 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
701453-99DrillChesapeake Operating, Inc.Aug 30, 2010Sep 1, 2010Nov 8, 20109,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-15287————

Formation tops

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

FormationMD ftSubsea
Anacacho5,007-4,478
Austin Chalk5,359-4,830
Eagle Ford6,096-5,567

Perforations

Perforated and open-hole intervals.

FromToType
6,77111,782Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,89613.5725 S
5.511,8898.52,740 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
00Feb 3, 2012Oct 3, 2011—
00May 26, 2011Mar 25, 2011Yes

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