TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.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,000SUBSEA FTA2,748 FT ELB2,750 FT ELYatesYatesQueenQueenGrayburgGrayburgSan 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.

  • ABessie 44-41 B #10LS
  • BBessie 44-41 (Alloc-1NH) #5LB
FormationAB
Santa Rosa—1,769 MD 981
Yates299 MD 2,449377 MD 2,373
Queen-420 MD 3,168-674 MD 3,424
Grayburg-791 MD 3,539-1,166 MD 3,916
San Andres-1,239 MD 3,987SAN ANDRES - ACTIVE CO2 FLOOD; H-1,328 MD 4,078SAN ANDRES - ACTIVE CO2 FLOOD; H
Clear Fork-3,501 MD 6,249—
Spraberry-4,537 MD 7,285-4,475 MD 7,225
Dean—-5,782 MD 8,532
Wolfcamp—-5,993 MD 8,743

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.