TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.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
1,000-0-1,000-2,000-3,000-4,000-5,000SUBSEA FTA3,484 FT ELB3,379 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.

FormationAArvine 28 BBHis Eminence 27 Unit
Delaware1,333MD 2,1511,226MD 2,153
Cherry Canyon330MD 3,154204MD 3,175
Bone Spring-2,206MD 5,690-2,329MD 5,708
Wolfcamp-5,174MD 8,658-5,305MD 8,684

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

AArvine 28 B #3H 42-109-33239

Cimarex Energy Co. · Culberson · 3,484 ft elevation · 15,500 ft TD

FormationMD ftSubsea
Delaware2,1511,333
Cherry Canyon3,154330
Bone SpringBONE SPRINGS5,690-2,206
Wolfcamp8,658-5,174

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

FormationMD ftSubsea
Delaware2,1531,226
Cherry Canyon3,175204
Bone SpringBONE SPRINGS5,708-2,329
Wolfcamp8,684-5,305

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.