TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, under 0.1 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,000-5,000-6,000SUBSEA FTA3,233 FT ELB3,233 FT ELDelawareDelawareCherry CanyonCherry CanyonBone SpringBone SpringWolfcampWolfcamp

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.

FormationAAuthentic 13 a StateBAuthentic 13 D State
Delaware795MD 2,438795MD 2,438
Cherry Canyon-82MD 3,315-122MD 3,355
Bone Spring-2,825MD 6,058-2,865MD 6,098
Wolfcamp-5,907MD 9,140-6,152MD 9,385

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

Cimarex Energy Co. · Culberson · 3,233 ft elevation · 15,000 ft TD

FormationMD ftSubsea
Delaware2,438795
Cherry Canyon3,315-82
Bone Spring6,058-2,825
Wolfcamp9,140-5,907

Cimarex Energy Co. · Culberson · 3,233 ft elevation · 15,000 ft TD

FormationMD ftSubsea
Delaware2,438795
Cherry Canyon3,355-122
Bone Spring6,098-2,865
Wolfcamp9,385-6,152

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.