TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.3 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,723 FT ELB2,713 FT EL

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.

  • ASlaughter '28' #1
  • BLB Epley 34-46 A #501LS
FormationAB
Santa Rosa—1,786 MD 927
Yates—256 MD 2,457
Seven Rivers—106 MD 2,607
Queen—-678 MD 3,391
Grayburg—-1,047 MD 3,760
San Andres—-1,341 MD 4,054SAN ANDRES - HIGH FLOWS, H2S, CO
Glorieta—-2,407 MD 5,120
Clear Fork—-3,715 MD 6,428
Spraberry—-4,607 MD 7,320
Strawn-7,505 MD 10,228—
Bend-7,657 MD 10,380—
Atoka-7,905 MD 10,628—
Devonian-8,444 MD 11,167—
Fusselman-8,982 MD 11,705—
Sylvan-9,059 MD 11,782—
Montoya-9,063 MD 11,786—

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.