TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.2 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,199 FT ELB3,200 FT ELBell CanyonBell CanyonCherry CanyonCherry CanyonBrushy CanyonBrushy CanyonBone SpringBone Spring

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.

  • AQueen Robyn E2W2 T #112H
  • BQueen Robyn W2E2 I #216H
FormationAB
Delaware—-2,173 MD 5,373
Bell Canyon-2,131 MD 5,330-2,196 MD 5,396
Cherry Canyon-3,181 MD 6,380-3,133 MD 6,333
Brushy Canyon-4,691 MD 7,890-4,685 MD 7,885
1ST Bone Spring Sand—-7,153 MD 10,353
Bone Spring-7,171 MD 10,370-6,061 MD 9,261
2ND Bone Spring Sand—-7,810 MD 11,010
3RD Bone Spring Sand—-8,915 MD 12,115

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.