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-2,000-4,000-6,000-8,000-10,000SUBSEA FTA537 FT ELB533 FT ELNavarroNavarroAnacachoAnacachoAustin ChalkAustin ChalkEagle FordEagle Ford

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.

  • AMunson Ranch #24H
  • BBoedeker Lease #20H
FormationAB
Reklaw—-3,164 MD 3,697
Wilcox—-3,555 MD 4,088WILCOX - DISPOSAL
Carrizo—-3,602 MD 4,135
Navarro-8,412 MD 8,949-8,559 MD 9,092
Olmos-8,944 MD 9,481—
Anacacho-9,877 MD 10,414-9,851 MD 10,384
Austin Chalk-10,102 MD 10,639AUSTIN CHALK - H2S-10,215 MD 10,748AUSTIN CHALK - H2S
Eagle Ford-10,768 MD 11,305EAGLE FORD - H2S-10,791 MD 11,324EAGLE FORD - H2S

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.