TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.4 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,201 FT ELB3,182 FT ELDelawareDelawareRed BluffRed BluffBell CanyonBell CanyonCherry 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.

  • APowder Keg E #415H
  • BBoyd 2503 SWD #1
FormationAB
Red Bluff-699 MD 3,900-718 MD 3,900
Delaware-2,209 MD 5,410182 MD 3,000
Bell Canyon-2,238 MD 5,439-2,210 MD 5,392
Cherry Canyon-3,068 MD 6,269-3,065 MD 6,247
Brushy Canyon-4,625 MD 7,826—
Bone Spring-6,087 MD 9,288—
First Bone Spring-7,269 MD 10,470—
Second Bone Spring-7,802 MD 11,003—
Third Bone Spring-8,233 MD 11,434—
Wolfcamp-9,213 MD 12,414—

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.