TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

0-1,000-2,000-3,000-4,000SUBSEA FTA2,733 FT ELB2,738 FT ELGrayburgGrayburgSan AndresSan AndresSpraberrySpraberryJo MillJo MillDeanDean

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.

  • AHickman Allocation B #22HA
  • BRCR 180-197 Alloc 06 #25HC
FormationAB
Queen—576 MD 2,162
Grayburg357 MD 2,376356 MD 2,382
San Andres20 MD 2,713SAN ANDRES - SALTWATER FLOW, POS88 MD 2,650SAN ANDRES - SALTWATER FLOW, POS
Clear Fork—-798 MD 3,536
Spraberry-2,649 MD 5,382-2,648 MD 5,386
Jo Mill-3,527 MD 6,260JO-MILL SAND-3,522 MD 6,260JO-MILL
Dean-4,047 MD 6,780-4,041 MD 6,779
Wolfcamp-4,180 MD 6,913—

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.