TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

2,0001,000-0-1,000-2,000SUBSEA FTA3,062 FT ELB3,058 FT ELSanta RosaSanta RosaYatesYatesQueenQueenSeven RiversSeven RiversGrayburgGrayburg

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.

  • ACowden, J. M. R/a -B- #1984
  • BNorth Cowden Unit #1101R
FormationAB
Santa Rosa2,022 MD 1,040SANTA ROSA BASE1,624 MD 1,434SANTA ROSA BASE
Yates262 MD 2,800286 MD 2,772
Seven Rivers32 MD 3,030-49 MD 3,107
Queen-498 MD 3,56074 MD 2,984
Grayburg-827 MD 3,889-838 MD 3,896
San Andres-1,241 MD 4,303SAN ANDRES - HIGH FLOWS, H2S, CO—
Holt-2,024 MD 5,086—
Glorieta-2,124 MD 5,186—
Clear Fork-2,232 MD 5,294—

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.