TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

1,000-0-1,000-2,000-3,000-4,000-5,000SUBSEA FTA2,397 FT ELB2,235 FT ELSan AndresSan AndresSan AngeloSan AngeloClear ForkClear ForkColeman JunctionColeman JunctionCiscoCiscoCanyonCanyon

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.

  • ATeague 9 #18
  • BTurner Ranch T.D. 8 #1
FormationAB
San Andres1,525 MD 8721,485 MD 750
San Angelo1,229 MD 1,1681,210 MD 1,025
Clear Fork1,185 MD 1,2121,125 MD 1,110
Coleman Junction-823 MD 3,220-967 MD 3,202
Wolfcamp—-2,095 MD 4,330
Cisco-3,507 MD 5,904-3,687 MD 5,922
Canyon-4,255 MD 6,652-4,279 MD 6,514
Fusselman—-4,751 MD 6,986
Strawn-4,893 MD 7,290—

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.