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
2,000-0-2,000-4,000SUBSEA FTA3,282 FT ELB3,283 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.

FormationAMustang State UnitBMustang State Unit
Rustler2,932MD 350—
Delaware1,058MD 2,2241,045MD 2,238
Cherry Canyon50MD 3,23250MD 3,233
Bone Spring-2,522MD 5,804-2,535MD 5,818
Wolfcamp-5,554MD 8,836-5,510MD 8,793

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

Carrizo (Permian) LLC · Culberson · 3,282 ft elevation · 11,000 ft TD

FormationMD ftSubsea
Rustler3502,932
Delaware2,2241,058
Cherry Canyon3,23250
Bone SpringBONE SPRINGS5,804-2,522
Wolfcamp8,836-5,554

Carrizo (Permian) LLC · Culberson · 3,283 ft elevation · 11,000 ft TD

FormationMD ftSubsea
Delaware2,2381,045
Cherry Canyon3,23350
Bone SpringBONE SPRINGS5,818-2,535
Wolfcamp8,793-5,510

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.