TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.3 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,332 FT ELB2,592 FT ELBase (Creataceous)Base (Creataceous)QueenQueenGrayburgGrayburgSan 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 #47A01
  • BYates Field Unit #47A15
FormationAB
Base Cretaceous (marker)—2,052 MD 540BASE CRETACEOUS
Base1,950 MD 382—
Base (Creataceous)1,950 MD 3822,052 MD 540
Yates Smtih Sand—1,851 MD 741
Smith Sand—1,851 MD 741
Yates (Smith Sand)—1,851 MD 741
Seven Rivers—1,763 MD 829
Queen1,319 MD 1,0131,328 MD 1,264
Grayburg1,287 MD 1,0451,292 MD 1,300
San Andres1,262 MD 1,0701,270 MD 1,322

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.