TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

AChaffin #292 tops×BVestal #365 tops×
Download
400300200100-0SUBSEA FTA970 FT ELB941 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.

FormationAChaffinBVestal
Trinity Water Sandsn - High Wash470MD 500476MD 465
Canyon—436MD 505
Strawn—191MD 750
Serratt Sand—81MD 860
Pennsylvanian110MD 860-19MD 960

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

AChaffin #29 42-097-34752

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

FormationMD ftSubsea
Trinity Water Sandsn - High Wash500470
PennsylvanianPENNSYLVANIAN SAND860110

BVestal #36 42-097-34685

V & H Oil, L.P. · Cooke · 941 ft elevation · 1,999 ft TD

FormationMD ftSubsea
Trinity Water Sandsn - High Wash465476
Canyon505436
Strawn750191
Serratt Sand86081
PennsylvanianPENNSYLVANIAN SAND960-19

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.