WELL · 42-227-36634 · DISTRICT 8

Sage #1

Plugged

Howard County · Spraberry (Trend Area) field  · Vertical

Sage #1 (API 42-227-36634) is a plugged well in Howard County, plugged July 21, 2023, last operated by Surge Operating LLC.

The RRC has issued one drilling permit, issued April 5, 2011, permitted to 11,000 ft.

It was permitted by Clear Water Inc. and has since transferred to Surge Operating LLC on the wellbore schedule.

Completion filings report 5 formation tops, including San Andres, Clear Fork, Spraberry, Dean.

Its lease has reported 5.18K barrels of oil and 34.6K mcf of gas since August 2011, last reporting in October 2023.

Operator of record

Surge Operating LLC

Permitted by Clear Water Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed May 4, 2026 · 1,229 permits on file · (832) 495-6024

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSurge Operating LLC
Production reportsSurge Operating, LLCthrough Aug 2019
Latest permitClear Water Inc.Apr 5, 2011

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

11,000
total depth, ft
1
permits on file
Apr 5, 2011
last permit issued
Aug 16, 2019
completed
5.18K
cumulative oil, bbl
34.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2011 THROUGH Oct 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 16, 2019
Shut in
—
Plugged
Jul 21, 2023

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
Sage O-10-41619Spraberry (Trend Area)Surge Operating, LLC15.18K34.6KAug 2011 – Oct 2023

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. 1Clear Water Inc.Sep 2011 → Jul 2017
  2. 2Surge Operating, LLCAug 2019 → Aug 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
713312-99DrillClear Water Inc.Mar 31, 2011Apr 5, 2011Jun 15, 201111,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-41619————

Formation tops

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

FormationMD ftSubsea
San Andres2,800-119
Clear Fork4,730-2,049
SpraberrySPRABERRY (TREND AREA)6,250-3,569
Spraberry6,286-3,605
Dean7,549-4,868
Wolfcamp8,380-5,699

Perforations

Perforated and open-hole intervals.

FromToType
6,0956,306Perforated
7,5459,920Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37533017.5350 S
8.6254,54411400 S
5.510,2887.8751,160 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 3, 2020Nov 14, 2019—
00May 9, 2019Jan 30, 2019—
00Jul 11, 2012Sep 16, 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/22736634, documented in the API reference.