TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.7 miles end to end. Depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. Each formation filed in more than one well has its own color, joined between neighboring wells and shaded down to the next formation both filed; nothing is interpolated. Where tops come from →

Download
1,5001,000500-0SUBSEA FTA2,892 FT ELB2,893 FT ELYatesYatesSeven RiversSeven RiversColby / QueenColby / Queen

shaded: a formation down to the next one filed in both wellsfiled in one well onlyhover a top or a name to pick out one formation

Tops by well

Subsea feet, with measured depth beneath; a dash where the well has no top filed for the formation.

FormationADaugherty, LumBCLS Walton
Rustler1,826MD 1,066—
Yates-6MD 2,898204MD 2,689
Seven Rivers-231MD 3,123-51MD 2,944
Colby / Queen-406MD 3,298-243MD 3,136

Add wells nearby

Around
Loading the map…
In the sectionMatchesFiltered out

Only wells with a location on file can be found by distance; a well with tops but no location can still be added by name or API number.

The tops, as filed

ADaugherty, Lum #3544W 42-495-34775

Juno Operating Company III, LLC · Winkler · 2,892 ft elevation · 3,700 ft TD

FormationMD ftSubsea
RustlerRUSTLER - POSSIBLE FLOW; POSSIBL1,0661,826
Yates2,898-6
Seven RiversSEVEN RIVERS / QUEEN3,123-231
Colby / Queen3,298-406

BCLS Walton #1536NW 42-495-34722

Juno Operating Company III, LLC · Winkler · 2,893 ft elevation · 3,700 ft TD

FormationMD ftSubsea
Yates2,689204
Seven RiversSEVEN RIVERS / QUEEN2,944-51
Colby / Queen3,136-243

About this data

Formation tops and elevations from the RRC dbf900 wellbore file (completion filings), names normalized to the formations registry; well identity from the permit record, location from the shared well record. Subsea is elevation minus measured depth. Nothing between filed tops is estimated.

New to these records? completion reports and the wellbore file

Developers: this page as JSON is GET /v1/data/cross-section, documented in the API reference.