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,074 FT ELB3,081 FT ELCherry CanyonCherry CanyonBrushy CanyonBrushy CanyonBone Spring LimeBone Spring Lime

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.

  • AKyle 24 #R801
  • BKyle 24 #F001
FormationAB
Cherry Canyon-2,849 MD 5,923-2,626 MD 5,707
Delaware—-3,896 MD 6,977
Brushy Canyon-4,071 MD 7,145-3,896 MD 6,977
Avalon Upper-5,753 MD 8,827—
Avalon Lower-6,338 MD 9,412—
First Bone Spring-6,605 MD 9,679—
Bone Spring Lime-5,726 MD 8,800-6,691 MD 9,772BONE SPRINGS
Second Bone Spring Upper (Shale)-6,900 MD 9,974—
Wolfcamp—-8,696 MD 11,777

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.