TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

Download
-0-2,000-4,000-6,000-8,000-10,000SUBSEA FTA377 FT ELB372 FT ELAustin ChalkAustin ChalkEagle FordEagle Ford

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.

FormationANapoo BBBeckett-Guerra Unit A
Carrizo-10,301MD 10,678—
Wilcox-10,301MD 10,678—
Austin Chalk-10,435MD 10,812-10,464MD 10,836
Eagle Ford-10,605MD 10,982-10,649MD 11,021

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

ANapoo B #2H 42-255-38103

Verdun Oil & Gas LLC · Karnes · 377 ft elevation · 11,360 ft TD

FormationMD ftSubsea
Carrizo10,678-10,301
WilcoxWILCOX - DISPOSAL10,678-10,301
Austin ChalkAUSTIN CHALK - H2S10,812-10,435
Eagle FordEAGLE FORD - H2S10,982-10,605

Verdun Oil & Gas LLC · Karnes · 372 ft elevation · 11,300 ft TD

FormationMD ftSubsea
Austin ChalkAUSTIN CHALK - H2S10,836-10,464
Eagle FordEAGLE FORD - H2S11,021-10,649

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.