TOOLS · CROSS-SECTION · TEXAS

2 wells, measured depth

West to east, 0.4 miles end to end. Measured depth: not every well has an elevation.

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

01,0002,0003,0004,000MD FTA2,446 FT ELBNO ELEVATIONYatesYatesSeven RiversSeven RiversSan AndresSan AndresGlorietaGlorietaClear 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

Measured depth, feet; the name as filed where it differs; a dash where the well has no top filed for the formation.

  • AOwen-Chalk #69
  • BChalk, G. O. #27
FormationAB
Tansill—1,127
Yates1,220 1,231
Seven Rivers1,306 1,321
Queen—1,508
Grayburg—1,809
San Andres2,102 SAN ANDRES - HIGH FLOWS, H2S, CO2,117 SAN ANDRES - HIGH FLOWS, H2S, CO
Glorieta2,633 2,642
Clear Fork3,018 CLEARFORK - SEVERE WATER FLOWS2,990 CLEARFORK - SEVERE WATER FLOWS
Tubb—3,651

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.