TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.1 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,5001,000500-0-500-1,000SUBSEA FTA2,668 FT ELB2,664 FT ELRustlerRustlerYatesYatesSeven RiversSeven RiversQueenQueenGrayburgGrayburg

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 #3330
  • BWaddell TR A #1598
FormationAB
Rustler2,247 MD 4212,252 MD 412
Yates1,096 MD 1,5721,094 MD 1,570
Seven Rivers875 MD 1,793869 MD 1,795
Queen312 MD 2,356319 MD 2,345
Grayburg60 MD 2,608GRAYBURG - ACTIVE CO2 FLOOD37 MD 2,627
Judkins—-139 MD 2,803
San Andres-145 MD 2,813SAN ANDRES - USABLE QUALITY WATE—
McKnight—-638 MD 3,302
San Angelo-978 MD 3,646—
Clear Fork-1,327 MD 3,995—

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.