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,000SUBSEA FTA2,640 FT ELB2,640 FT ELCastileCastileDelawareDelawareBell 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.

  • ATrigger 39-40 A #32H
  • BTrigger 39-40 Unit B #8H
FormationAB
Castile770 MD 1,870CASTILLE749 MD 1,891CASTILLE
Delaware-2,015 MD 4,655-2,021 MD 4,661
Bell Canyon-2,042 MD 4,682-2,043 MD 4,683
Cherry Canyon-2,957 MD 5,597-2,985 MD 5,625
Bone Spring—-5,154 MD 7,794BONE SPRINGS
Permian (undifferentiated)—-7,363 MD 10,003PERMIAN
Wolfcamp—-7,619 MD 10,259

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.