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

0-2,000-4,000-6,000-8,000SUBSEA FTA2,743 FT ELB2,742 FT ELSpraberry (Trend Area)Spraberry (Trend Area)

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.

  • AMcAlister '31B' #1
  • BHigh Sky N 42-43 #2414H
FormationAB
Santa Rosa—1,742 MD 1,000
Seven Rivers—1,442 MD 1,300
Yates—166 MD 2,576
Queen—-701 MD 3,443
Grayburg—-1,321 MD 4,063
San Andres—-1,515 MD 4,257SAN ANDRES - HIGH FLOWS, H2S, CO
Glorieta—-2,410 MD 5,152
Clear Fork—-3,870 MD 6,612
Spraberry-4,707 MD 7,450—
Spraberry (Trend Area)-4,707 MD 7,450-4,709 MD 7,451
Strawn-7,607 MD 10,350—
Bend-7,782 MD 10,525—
Atoka-7,882 MD 10,625—

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.