TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.4 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,000SUBSEA FTA2,630 FT ELB2,624 FT ELGrayburgGrayburgJudkinsJudkins

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.

  • AWaddell TR A #4821H
  • BWaddell TR A #480
FormationAB
Yates1,002 MD 1,628—
Seven Rivers759 MD 1,871—
Queen226 MD 2,404—
McElroy—203 MD 2,421
Grayburg-31 MD 2,661GRAYBURG - ACTIVE CO2 FLOOD-40 MD 2,664
San Andres-224 MD 2,854SAN ANDRES - USABLE QUALITY WATE—
Judkins-329 MD 2,959-255 MD 2,879
McKnight—-726 MD 3,350
San Angelo—-995 MD 3,619
Clear Fork—-1,439 MD 4,063
Tubb—-1,815 MD 4,439
Wichita-Albany—-2,328 MD 4,952
Wolfcamp—-3,094 MD 5,718

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.