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 →

ALinn #015 tops×BTHS Unit #22 tops×
Download
400200-0-200-400-600SUBSEA FTA990 FT ELB959 FT ELTrinity Water Sandsn - …Trinity Water Sandsn - High WashPennsylvanianPennsylvanian

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.

FormationALinnBTHS Unit
Canyon465MD 525—
Trinity Water Sandsn - High Wash540MD 450459MD 500
Strawn240MD 750—
Caddo-80MD 1,070—
Pennsylvanian164MD 826-641MD 1,600

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

ALinn #01 42-097-34745

V & H Oil, L.P. · Cooke · 990 ft elevation · 2,100 ft TD

FormationMD ftSubsea
Trinity Water Sandsn - High Wash450540
Canyon525465
Strawn750240
PennsylvanianPENNSYLVANIAN SAND826164
CaddoCADDO LIME1,070-80

BTHS Unit #2 42-097-34751

Miller, Glenn J. · Cooke · 959 ft elevation · 1,999 ft TD

FormationMD ftSubsea
Trinity Water Sandsn - High Wash500459
PennsylvanianPENNSYLVANIAN SAND1,600-641

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.