TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.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,000SUBSEA FTA2,765 FT ELB2,752 FT ELYatesYatesSan AndresSan AndresSpraberrySpraberryDeanDean

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.

  • ABrittany 43-07 #1H
  • BThriller #2DH
FormationAB
Santa Rosa—1,707 MD 1,045
Yates375 MD 2,390432 MD 2,320
Queen—-313 MD 3,065
Grayburg—-948 MD 3,700
San Andres-1,275 MD 4,040SAN ANDRES - ACTIVE CO2 FLOOD; H-1,152 MD 3,904SAN ANDRES - ACTIVE CO2 FLOOD; H
Clear Fork—-2,518 MD 5,270
Spraberry-4,610 MD 7,375-4,343 MD 7,095
Dean-5,985 MD 8,750-5,857 MD 8,609
Wolfcamp-6,135 MD 8,900—

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.