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 →

AWaggoner 4N1 #103 tops×BPudge #12 tops×
Download
250-0-250-500-750-1,000-1,250SUBSEA FTA1,134 FT ELB1,121 FT ELColeman JunctionColeman JunctionDyson SandDyson Sand

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.

FormationAWaggoner 4N1BPudge
Coleman Junction259MD 875269MD 852
Dyson Sand-816MD 1,950-779MD 1,900
Milham Sand-1,358MD 2,492—

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

AWaggoner 4N1 #10 42-487-33174

Covenant Operating, LLC · Wilbarger · 1,134 ft elevation · 3,000 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON875259
Dyson Sand1,950-816
Milham Sand2,492-1,358

BPudge #1 42-487-33293

Burk Royalty Co., Ltd. · Wilbarger · 1,121 ft elevation · 2,000 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON852269
Dyson Sand1,900-779

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.