WELLS · CROSS-SECTION

2 wells, measured depth

West to east, 0.2 miles end to end. Shown in measured depth because not every well reports an elevation, so the columns are not datum-aligned. Dashed lines join the same normalized formation in neighbouring wells; nothing is interpolated. Where tops come from →

02,0004,0006,0008,000MD FTANO ELEVATIONColeman JunctionCiscoCanyonPalo PintoStrawnB1,396 FT ELColeman JunctionCiscoNoble LimeCanyonPalo Pinto

reported topsame formation, neighbouring wells

The tops, as filed

ACondon #3 42-487-33145

Slant Operating, LLC · 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—

BWhitefish B #1 42-487-33197

Slant Operating, LLC · Wilbarger · 1,396 ft elevation · 9,000 ft TD

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON1501,246
Cisco3,300-1,904
Noble Lime3,546-2,150
Canyon4,010-2,614
Palo Pinto4,560-3,164

About this data

Formation tops and elevations from the RRC dbf900 wellbore file (completion filings), names normalized to the formations registry; well identity and location from the permit 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.