TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 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,000-0-2,000-4,000SUBSEA FTA3,033 FT ELB3,030 FT ELDelawareDelawareCherry 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.

  • ADakar 53-2 Lov Unit #1108H
  • BCopperhead 53-14 #B103HC
FormationAB
Rustler—2,464 MD 566
Salado—2,048 MD 982
Bell Canyon1,164 MD 1,869—
Castile—144 MD 2,886
Lamar—-1,863 MD 4,893LAMAR LIME
Delaware1,185 MD 1,848-1,900 MD 4,930
Cherry Canyon164 MD 2,869-2,893 MD 5,923
Brushy Canyon-1,027 MD 4,060-4,242 MD 7,272
Wolfcamp-5,563 MD 8,596—
Bone Spring-2,631 MD 5,664BONE SPRINGS-5,679 MD 8,709

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.