TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.8 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-1,000-2,000-3,000-4,000-5,000-6,000SUBSEA FTA3,070 FT ELB3,070 FT ELDelawareDelawareCherry CanyonCherry CanyonBone SpringBone SpringWolfcampWolfcamp

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.

  • AAlice Fee 34 #3H
  • BHay Maddilyn #0011WA
FormationAB
Delaware613 MD 2,457631 MD 2,439
Ford-Delaware556 MD 2,514—
Cherry Canyon-356 MD 3,426-263 MD 3,333
Bone Spring-3,045 MD 6,115BONE SPRINGS-2,991 MD 6,061
First Bone Spring Upper—-3,913 MD 6,983
Second Bone Spring Upper—-4,561 MD 7,631
Third Bone Spring—-5,658 MD 8,728
Wolfcamp-6,045 MD 9,115-5,974 MD 9,044

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.