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

2,0001,000-0-1,000-2,000-3,000SUBSEA FTA3,726 FT ELB3,725 FT ELDelawareDelawareCherry CanyonCherry CanyonBone SpringBone SpringBone Spring 1Bone Spring 1Bone Spring 2Bone Spring 2Bone Spring 3Bone Spring 3

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.

  • ADr State Wise Unit 1 #0252TB
  • BDr State Wise Unit 1 #0254TB
FormationAB
Delaware2,128 MD 1,5982,127 MD 1,598
Cherry Canyon1,273 MD 2,4531,272 MD 2,453
Bone Spring-2,156 MD 5,882-2,175 MD 5,900
Bone Spring 1-2,156 MD 5,882-2,175 MD 5,900
Bone Spring 2-2,606 MD 6,332-2,616 MD 6,341
Bone Spring 3-3,755 MD 7,481-3,775 MD 7,500

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.