TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.6 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
-0-2,000-4,000-6,000-8,000-10,000-12,000SUBSEA FTA361 FT ELB407 FT ELGlen RoseGlen RoseJames LimeJames LimeTravis PeakTravis PeakHaynesvilleHaynesville

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.

FormationASally Ride Knox 1HBSally Ride Knox 4H
Glen Rose-5,019MD 5,380-4,973MD 5,380
James Lime-7,440MD 7,801-7,394MD 7,801
Travis Peak-8,302MD 8,663-8,256MD 8,663
Haynesville-12,751MD 13,112-12,705MD 13,112

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

Aethon Energy Operating LLC · San Augustine · 361 ft elevation · 13,670 ft TD

FormationMD ftSubsea
Glen Rose5,380-5,019
James Lime7,801-7,440
Travis Peak8,663-8,302
Haynesville13,112-12,751

Aethon Energy Operating LLC · San Augustine · 407 ft elevation · 13,685 ft TD

FormationMD ftSubsea
Glen Rose5,380-4,973
James Lime7,801-7,394
Travis Peak8,663-8,256
Haynesville13,112-12,705

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.