TOOLS · CROSS-SECTION · TEXAS

2 wells, measured depth

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

AHanna Trust #14 tops×BCondon #35 tops×
Download
02,0004,0006,0008,000MD FTA1,382 FT ELBNO ELEVATIONColeman JunctionColeman JunctionCiscoCiscoCanyonCanyon

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.

FormationAHanna TrustBCondon
Coleman Junction150150
Cisco3,3563,351
Noble Lime3,560—
Canyon4,0404,400
Palo Pinto—4,620
Strawn—4,909

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

AHanna Trust #1 42-487-33181

Burk Royalty Co., Ltd. · Wilbarger · 1,382 ft elevation · 9,000 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON1501,232
Cisco3,356-1,974
Noble Lime3,560-2,178
Canyon4,040-2,658

BCondon #3 42-487-33145

Burk Royalty Co., Ltd. · Wilbarger · no elevation on file · 8,900 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON150—
Cisco3,351—
Canyon4,400—
Palo Pinto4,620—
Strawn4,909—

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.