TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 3.5 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,000500-0-500SUBSEA FTA1,940 FT ELB1,731 FT ELColeman JunctionColeman Junction

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.

  • ANW Valera Unit #2P
  • BRobert Horne #5
FormationAB
Coleman Junction1,215 MD 7251,106 MD 625
Tannehill—899 MD 832TANNEHILL - DISPOSAL
King Sand - Disposal—541 MD 1,190
Winchell Lime - Disposal—-129 MD 1,860
Capps Lime - Disposal—-657 MD 2,388
Morris Sand-845 MD 2,785—

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.