TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 2.3 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,500-5,000-7,500-10,000-12,500-15,000SUBSEA FTA201 FT ELB246 FT ELGlen RoseGlen RosePettitPettitTravis PeakTravis Peak

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.

FormationARockies Gas UnitBDenali Gas Unit
Glen Rose-7,594MD 7,795-7,753MD 7,999
Pettit-9,946MD 10,147-10,186MD 10,432
Travis Peak-10,801MD 11,002-11,030MD 11,276
Haynesville—-15,603MD 15,849

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

ARockies Gas Unit #1H 42-005-30416

BP America Production Company · Angelina · 201 ft elevation · 19,500 ft TD

FormationMD ftSubsea
Glen Rose7,795-7,594
PettitPETTET10,147-9,946
Travis Peak11,002-10,801

BDenali Gas Unit #2HB 42-005-30461

Aethon Energy Operating LLC · Angelina · 246 ft elevation · 16,500 ft TD

FormationMD ftSubsea
Glen Rose7,999-7,753
PettitPETTET10,432-10,186
Travis Peak11,276-11,030
Haynesville15,849-15,603

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.