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

2,0001,5001,000500-0SUBSEA FTA2,348 FT ELB2,440 FT ELBase (Cretaceous)Base (Cretaceous)YatesYatesSeven RiversSeven RiversQueenQueenGrayburgGrayburgSan AndresSan Andres

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.

  • AYates Field Unit #214KD1
  • BYates Field Unit #214K46
FormationAB
Base (Cretaceous)1,986 MD 3622,014 MD 426BASE CRETACEOUS
Base Cretaceous1,986 MD 362—
Yates1,690 MD 658YATES (SMITH SAND)1,767 MD 673YATES (SMITH SAND)
Seven Rivers1,609 MD 7391,695 MD 745
Queen1,160 MD 1,1881,231 MD 1,209
Grayburg1,128 MD 1,2201,202 MD 1,238
San Andres1,088 MD 1,2601,166 MD 1,274

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.