TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.8 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 FTA226 FT ELB251 FT ELYeguaYegua

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.

FormationAWess 4-Slgtr- Ecrr (SA) B6BEscondido Creek
Frio-422MD 648—
Yegua-2,114MD 2,340-1,710MD 1,961
Queen City-4,501MD 4,727—
Reklaw-5,633MD 5,859—
Carrizo-5,803MD 6,029—
Wilcox-5,853MD 6,079—
Austin Chalk-12,812MD 13,038—

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

Statoil Texas Onshore Prop LLC · Karnes · 226 ft elevation · 15,000 ft TD

FormationMD ftSubsea
FrioFRIO - DISPOSAL648-422
YeguaYEGUA - DISPOSAL2,340-2,114
Queen City4,727-4,501
Reklaw5,859-5,633
Carrizo6,029-5,803
WilcoxWILCOX - DISPOSAL6,079-5,853
Austin ChalkAUSTIN CHALK - H2S13,038-12,812

BEscondido Creek #5 42-255-35534

Patterson Energy Corporation · Karnes · 251 ft elevation · 4,100 ft TD

FormationMD ftSubsea
Yegua1,961-1,710

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.