TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

1,5001,000500-0-500-1,000-1,500SUBSEA FTA2,297 FT ELB2,270 FT ELYatesYatesSan AndresSan AndresClear ForkClear Fork

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.

  • ASpade 18 #3701
  • BSpade Ranch #351
FormationAB
Yates1,742 MD 555YATES - OVERPRESSURED, POSSIBLE1,700 MD 570YATES - OVERPRESSURED, POSSIBLE
Seven Rivers1,607 MD 690—
Atoka1,502 MD 795—
Queen1,217 MD 1,080—
San Andres897 MD 1,400SAN ANDRES - HIGH FLOWS, H2S, CO904 MD 1,366SAN ANDRES - HIGH FLOWS, H2S, CO
Glorieta447 MD 1,850—
Clear Fork32 MD 2,265160 MD 2,110
Wichita-Albany-858 MD 3,155WICHITA—
Wolfcamp—-1,480 MD 3,750

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.