TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 2.5 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-0-500SUBSEA FTA2,146 FT ELB2,162 FT ELQueenQueenUpper Clear ForkUpper Clear Fork

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.

FormationANorth Westbrook UnitBWestbrook Southeast Unit
Yates—1,572MD 590
Seven Rivers—1,397MD 765
Queen1,142MD 1,0041,062MD 1,100
Grayburg—652MD 1,510
Glorieta—-28MD 2,190
Upper Clear Fork-290MD 2,436-278MD 2,440
Lower Clear Fork-790MD 2,936—

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

Sabinal Energy Operating, LLC · Mitchell · 2,146 ft elevation · 3,155 ft TD

FormationMD ftSubsea
Queen1,0041,142
Clear ForkUPPER CLEAR FORK2,436-290
Clear ForkLOWER CLEAR FORK2,936-790

Sabinal Energy Operating, LLC · Mitchell · 2,162 ft elevation · 3,500 ft TD

FormationMD ftSubsea
Yates5901,572
Seven Rivers7651,397
Queen1,1001,062
GrayburgGRAYBURG/SAN ANDRES1,510652
Glorieta2,190-28
Clear Fork2,440-278

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.