TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.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

2,000-0-2,000-4,000-6,000SUBSEA FTA3,309 FT ELB3,340 FT ELRustlerRustlerDelawareDelawareFord / DelawareFord / DelawareCherry CanyonCherry 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.

  • AJavelina SWD #1
  • BDaltex Munn Unit 44-41 #28H
FormationAB
Rustler3,123 MD 1862,840 MD 500
Salado2,807 MD 502—
Castile2,273 MD 1,036CASTILE LM—
Delaware871 MD 2,438646 MD 2,694
Ford / Delaware871 MD 2,438646 MD 2,694
Cherry Canyon-117 MD 3,426-350 MD 3,690
Brushy Canyon-1,261 MD 4,570—
Bone Spring-2,652 MD 5,961-2,902 MD 6,242BONE SPRINGS
Wolfcamp—-5,774 MD 9,114

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.