TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, under 0.1 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 FTA326 FT ELB326 FT ELCatahoulaCatahoulaFrioFrioVicksburgVicksburgYeguaYeguaWilcoxWilcoxAustin 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.

  • AElder B #18H
  • BStulgis A #12H
FormationAB
Catahoula-535 MD 861-508 MD 834
Frio-1,211 MD 1,537-1,172 MD 1,498
Vicksburg-1,946 MD 2,272-1,906 MD 2,232
Yegua-2,968 MD 3,294-1,906 MD 2,232
Wilcox-4,429 MD 4,755-4,456 MD 4,782
Austin Chalk-11,203 MD 11,529-11,164 MD 11,490
Eagle Ford-11,730 MD 12,056-11,699 MD 12,025

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.