TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.5 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,536 FT ELB2,603 FT ELBase CretaceousBase CretaceousYatesYatesSeven 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 #35G38
  • BYates Field Unit #25D33
FormationAB
Base Cretaceous2,022 MD 5142,057 MD 546BASE CRETACEOUS
Base (Cretaceous)2,022 MD 514—
Yates (Smith Sand)—1,865 MD 738
Yates1,822 MD 714YATES (SMITH SAND)1,865 MD 738
Seven Rivers1,733 MD 8031,773 MD 830
Queen1,275 MD 1,2611,291 MD 1,312
Grayburg1,243 MD 1,2931,270 MD 1,333
San Andres1,175 MD 1,3611,219 MD 1,384

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.