TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, under 0.1 miles end to end. Subsea datum.

How to read it →

Each column is a well, lettered in the order drawn: west to east when every well has a location, or the order you list them (drag a well in the list, or switch to "As listed"). A well with no tops filed is listed but not drawn.

Under the subsea datum depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. When not every well reports an elevation the section is in measured depth and the columns are not datum-aligned.

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 →

Section · 2 wells drawn

-0-2,000-4,000-6,000-8,000SUBSEA FTA3,006 FT ELB3,006 FT ELBell CanyonBell CanyonDelawareDelawareRed BluffRed BluffCherry CanyonCherry Canyon

shaded: a formation down to the next one filed in both wellsfiled in one well onlypoint at or tap a top to read it

Tops by well

Subsea feet, with measured depth beneath; the name as filed where it differs; a dash where the well has no top filed for the formation.

  • AMosaic 28-0-19-30 D #14H
  • BSovereign 28-0-18-7 G #17H
FormationAB
Bell Canyon-2,269 MD 5,275-2,288 MD 5,294
Delaware-2,269 MD 5,275-2,288 MD 5,294
Red Bluff-3,229 MD 6,235-3,223 MD 6,229
Cherry Canyon-3,289 MD 6,295-3,294 MD 6,300
Brushy Canyon—-4,595 MD 7,601
Bone Spring—-6,094 MD 9,100
2ND Bone Spring—-7,374 MD 10,380
3RD Bone Spring—-7,926 MD 10,932
Wolfcamp—-8,940 MD 11,946

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.