TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 4.5 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 →

AMurphy-Kruse GU #13 tops×BRupp #53 tops×
Download
-0-2,000-4,000-6,000-8,000-10,000SUBSEA FTA116 FT ELB99 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.

FormationAMurphy-Kruse GUBRupp
Falfurrias B-6,874MD 6,990—
Atlee B-7,284MD 7,400—
Catahoula-7,584MD 7,700—
Frio—-8,651MD 8,750
Vicksburg VI—-10,319MD 10,418
Vicksburg VII—-10,661MD 10,760

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

AMurphy-Kruse GU #1 42-047-32489

EOG Resources, Inc. · Brooks · 116 ft elevation · 9,200 ft TD

FormationMD ftSubsea
Falfurrias B6,990-6,874
Atlee B7,400-7,284
CatahoulaCATAHOULA-ANAHUAC7,700-7,584

BRupp #5 42-047-32052

Crimson Exploration Oper., Inc. · Brooks · 99 ft elevation · 12,500 ft TD

FormationMD ftSubsea
Frio8,750-8,651
VicksburgVICKSBURG VI10,418-10,319
VicksburgVICKSBURG VII10,760-10,661

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.