TOOLS · CROSS-SECTION · TEXAS

2 wells, measured depth

West to east, under 0.1 miles end to end. Shown in measured depth because not every well reports an elevation, so the columns are not datum-aligned. 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 →

ABrown Trust #86H5 tops×BBrown Trust #88H4 tops×
Download
02,0004,0006,0008,00010,000MD FTANO ELEVATIONBNO ELEVATIONWilcoxWilcoxEscondidoEscondidoOlmosOlmosEagle 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

Measured depth, feet; a dash where the well has no top filed for the formation.

FormationABrown TrustBBrown Trust
Wilcox3,3093,038
Escondido5,8325,845
Olmos6,7486,765
Austin Chalk8,655—
Eagle Ford9,0479,040

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

ABrown Trust #86H 42-283-37137

Callon (Eagle Ford) LLC · La Salle · no elevation on file · 11,000 ft TD

FormationMD ftSubsea
WilcoxWILCOX - DISPOSAL3,309—
Escondido5,832—
OlmosOLMOS - DISPOSAL6,748—
Austin Chalk8,655—
Eagle FordEAGLE FORD - H2S9,047—

BBrown Trust #88H 42-283-37139

Callon (Eagle Ford) LLC · La Salle · no elevation on file · 11,000 ft TD

FormationMD ftSubsea
WilcoxWILCOX - DISPOSAL3,038—
Escondido5,845—
OlmosOLMOS - DISPOSAL6,765—
Eagle FordEAGLE FORD - H2S9,040—

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.