TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.0 miles end to end. Depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. 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 →

Download
700600500400300200100-0SUBSEA FTA1,587 FT ELB1,530 FT EL

shaded: a formation down to the next one filed in both wellsfiled in one well onlyhover a top or a name to pick out one formation

Tops by well

Subsea feet, with measured depth beneath; a dash where the well has no top filed for the formation.

FormationAStasney Ranch 63BCook Ranch 54A
Base Dothan Limestone—766MD 764
B Dothan LS735MD 852—
Top Noodle Creek Limestone—708MD 822
Top Lower Frye Sandstone—580MD 950
T Tannehill LS503MD 1,084—
T Saddle Creek LS447MD 1,140—
T Cook SD297MD 1,290—

Add wells nearby

Around
Loading the map…
In the sectionMatchesFiltered out

Only wells with a location on file can be found by distance; a well with tops but no location can still be added by name or API number.

The tops, as filed

AStasney Ranch 63 #25 42-417-39764

Stasney Well Service, LLC · Shackelford · 1,587 ft elevation · 2,000 ft TD

FormationMD ftSubsea
B Dothan LS852735
T Tannehill LS1,084503
T Saddle Creek LS1,140447
T Cook SD1,290297

BCook Ranch 54A #9 42-417-39665

Stasney Well Service, LLC · Shackelford · 1,530 ft elevation · 2,000 ft TD

FormationMD ftSubsea
Base Dothan Limestone764766
Top Noodle Creek Limestone822708
Top Lower Frye Sandstone950580

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.