TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.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 FTA2,900 FT ELB2,908 FT ELDelawareDelawareBell 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.

  • ATonopah 53-2-27 Lov #7H
  • BTonopah 53-2-27 Lov #2H
FormationAB
Delaware-1,757 MD 4,657-1,780 MD 4,688
Bell Canyon-1,781 MD 4,681-1,813 MD 4,721
Cherry Canyon-2,775 MD 5,675-2,799 MD 5,707
Brushy Canyon-3,966 MD 6,866-3,985 MD 6,893
Bone Spring-5,500 MD 8,400-5,533 MD 8,441
Bone Spring 1ST-6,439 MD 9,339—
Bone Spring 2ND-7,074 MD 9,974—
Wolfcamp-8,403 MD 11,303—

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.