TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.6 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,000-12,000SUBSEA FTA442 FT ELB476 FT ELYeguaYeguaWilcoxWilcoxAustin 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.

  • AG Klein C D-Wsch a Ulw D #1
  • BGreen A #14H
FormationAB
Frio—-319 MD 795FRIO - DISPOSAL
Yegua-1,448 MD 1,890-1,224 MD 1,700YEGUA - DISPOSAL
Queen City—-3,403 MD 3,879
Reklaw—-3,599 MD 4,075
Carrizo—-4,409 MD 4,885
Wilcox-4,552 MD 4,994-4,590 MD 5,066WILCOX - DISPOSAL
Austin Chalk-11,287 MD 11,729-11,269 MD 11,745AUSTIN CHALK - H2S
Eagle Ford-11,612 MD 12,054-11,573 MD 12,049EAGLE 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.