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
2,0001,000-0-1,000-2,000-3,000SUBSEA FTA3,215 FT ELB3,207 FT ELRed BluffRed BluffDelawareDelawareBell CanyonBell CanyonCherry CanyonCherry Canyon

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.

FormationAN. Aermotor C25-8 SWDBAermotor SWD
Red Bluff2,274MD 9412,617MD 590
Delaware-2,191MD 5,406-2,206MD 5,413
Bell Canyon-2,221MD 5,436-2,270MD 5,477
Cherry Canyon-3,179MD 6,394-3,197MD 6,404

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

Boyd, D. K. Oil and Gas Co.,inc. · Loving · 3,215 ft elevation · 7,360 ft TD

FormationMD ftSubsea
Red Bluff9412,274
Delaware5,406-2,191
Bell Canyon5,436-2,221
Cherry Canyon6,394-3,179

BAermotor SWD #2 42-301-33894

Boyd, D. K. Oil and Gas Co.,inc. · Loving · 3,207 ft elevation · 7,410 ft TD

FormationMD ftSubsea
Red Bluff5902,617
Delaware5,413-2,206
Bell Canyon5,477-2,270
Cherry Canyon6,404-3,197

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.