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
-0-1,000-2,000-3,000-4,000SUBSEA FTA2,240 FT ELB2,236 FT ELColeman JunctionColeman JunctionWolfcampWolfcamp

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.

FormationARibeye 88BTomahawk E 88-65
Wichita-Albany—-619MD 2,855
Coleman Junction-1,598MD 3,838-1,434MD 3,670
Wolfcamp-4,635MD 6,875-3,744MD 5,980

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

ARibeye 88 #1H 42-415-35528

Browning Oil Company, Inc. · Scurry · 2,240 ft elevation · 7,700 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - POSSIBLE LOST3,838-1,598
Wolfcamp6,875-4,635

BTomahawk E 88-65 #2H 42-415-35569

Browning Oil Company, Inc. · Scurry · 2,236 ft elevation · 7,700 ft TD

FormationMD ftSubsea
Wichita-AlbanyWICHITA2,855-619
Coleman JunctionCOLEMAN JUNCTION - POSSIBLE LOST3,670-1,434
Wolfcamp5,980-3,744

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.