TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.2 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,000SUBSEA FTA2,926 FT ELB2,924 FT ELSanta RosaSanta RosaYatesYatesQueenQueenGrayburgGrayburgSan AndresSan AndresSpraberrySpraberry

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.

  • AUL 2631 W1 #09SC
  • BUL 2631 #08WB
FormationAB
Santa Rosa1,419 MD 1,5071,419 MD 1,505
Yates-187 MD 3,113-146 MD 3,070
Queen-1,163 MD 4,089-1,126 MD 4,050
Grayburg-1,750 MD 4,676-1,676 MD 4,600
San Andres-1,932 MD 4,858SAN ANDRES - ACTIVE CO2 FLOOD; H-1,921 MD 4,845SAN ANDRES - ACTIVE CO2 FLOOD; H
Spraberry-5,450 MD 8,376-5,482 MD 8,406
Dean—-6,724 MD 9,648
Wolfcamp—-6,925 MD 9,849

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.