WELL · 42-399-35304 · DISTRICT 7

Sansom #2D

N

Runnels County  · Vertical

Sansom #2D (API 42-399-35304) is a permitted well in Runnels County filed by Imperial Gas Resources LLC; no completion report is on file yet.

The RRC has issued 3 drilling permits between 2011 and 2019, permitted to 5,000 ft.

Completion filings report 3 formation tops, including Gray, Caddo, Ellenburger.

Its 2 leases have reported 5.8K barrels of oil since March 2012, last reporting in December 2022. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Imperial Gas Resources LLC

Austin, TX · P-5 Y, filed Jan 5, 2026 · 115 permits on file · (817) 366-8383

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsImperial Gas Resources LLCthrough Jun 2019
Latest permitImperial Gas Resources LLCApr 1, 2019
5,000
total depth, ft
3
permits on file
Apr 1, 2019
last permit issued
—
completed
5.8K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2012 THROUGH Dec 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

32.052211, -99.733671

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Runnels County.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sansom O-8-31056Goldsboro (Gray)Imperial Gas Resources LLC15.8K0Mar 2012 – Dec 2022
Sansom O-8-32333Goldsboro (Gardner)Imperial Gas Resources LLC100Mar 2017 – Feb 2022

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. 1Imperial Gas Resources LLCMar 2012 → Jun 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
851676-99RecompletionImperial Gas Resources LLCApr 1, 2019Apr 1, 2019—4,060
754831-99RecompletionImperial Gas Resources LLCJan 15, 2013Jan 18, 2013—5,000
726946-99DrillImperial Gas Resources LLCOct 25, 2011Oct 31, 2011Jan 26, 20125,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-31056————
—— O-8-32333————

Formation tops

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

FormationMD ftSubsea
Gray4,066-2,029
Gray4,086-2,049
Caddo4,267-2,230
Ellenburger4,552-2,515
Ellenburger4,582-2,545

Perforations

Perforated and open-hole intervals.

FromToType
3,9483,958Perforated
3,9603,966Perforated
4,0904,093Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37512017165 S
8.6251,52312.25750 S
4.54,9797.875260 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, 2019Feb 27, 2019—
00Nov 29, 2012Aug 17, 2012Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Amos42-399-34752

1.2 KM · Imperial Gas Resources LLC · Section with this well →

Gardner3,974-1,937
Gray SD4,122-2,085
Caddo4,290-2,253

Amos42-399-34757

1.2 KM · Imperial Gas Resources LLC · Section with this well →

Fry3,744-1,715
Gardner3,933-1,904
Goldsboro (Gray)4,166-2,137

Gray Line Gray Sand Unit42-441-05226

6.2 KM · Quail Well Service, Inc. · Section with this well →

Coleman Junction1,240681
Saddle Creek1,800121
Palo Pinto3,130-1,209
Goen3,660-1,739
Gardner Lime3,740-1,819
Gray Sand3,918-1,997
Cisco—
Hope Lime - Disposal—

13 TOPS · FIRST 8

Gray Line Gray Sand Unit42-441-01810

6.6 KM · Quail Well Service, Inc. · Section with this well →

Coleman Junction1,240704
Saddle Creek1,800144
Palo Pinto3,130-1,186
Cisco—
King Sand - Disposal—
Swastika - Disposal—
Unidentified-County Regular - DI—
Hope Lime - Disposal—

10 TOPS · FIRST 8

Richey, J.E.42-083-36242

6.7 KM · Rhyne, J.V. · Section with this well →

Coleman Junction7621,233
Canyon3,625-1,630
Capps Lime - Disposal4,010-2,015
Tannehill—
Cook Sand - Disposal—
Crosscut Upper - Disposal—
King Sand - Disposal—
Overall - Disposal—

10 TOPS · FIRST 8

Gray Line Gray Sand Unit42-441-80568

6.8 KM · Quail Well Service, Inc. · Section with this well →

Coleman Junction1,220
Saddle Creek1,780
Flippen - Disposal2,110
Cook - Disposal2,180
Hope Lime - Disposal2,360
King Sand - Disposal2,430
Cisco2,630
Palo Pinto3,110

10 TOPS · FIRST 8

Gray Line Gray Sand Unit42-441-34692

6.8 KM · Quail Well Service, Inc. · Section with this well →

Coleman Junction1,224
Flippen - Disposal1,426
Saddle Creek1,812
Cook - Disposal2,085
Hope Lime - Disposal2,150
King Sand - Disposal2,214
Palo Pinto2,695
Cisco3,125

10 TOPS · FIRST 8

Gray Line Gray Sand Unit42-441-34727

7.1 KM · Quail Well Service, Inc. · Section with this well →

Coleman Junction1,224
Flippen - Disposal1,496
Saddle Creek1,816
Cook - Disposal2,194
Hope Lime - Disposal2,336
Cisco2,622
Swastika - Disposal2,689
Palo Pinto3,121

10 TOPS · FIRST 8

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