TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.6 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
-0-1,000-2,000-3,000-4,000-5,000-6,000SUBSEA FTA2,732 FT ELB2,772 FT ELBrushy CanyonBrushy 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.

FormationAFalcon State UnitBJones SWD
Red Bluff—-1,128MD 3,900
Bell Canyon—-1,928MD 4,700
Cherry Canyon-2,436MD 5,168—
Delaware—-3,528MD 6,300
Brushy Canyon-3,759MD 6,491-3,228MD 6,000
Bone Spring-6,080MD 8,812—

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

AFalcon State Unit #2H 42-301-33495

Apache Corporation · Loving · 2,732 ft elevation · 15,000 ft TD

FormationMD ftSubsea
Cherry Canyon5,168-2,436
Brushy Canyon6,491-3,759
Bone SpringBONE SPRINGS8,812-6,080

BJones SWD #1 42-301-33405

Mesquite SWD Inc · Loving · 2,772 ft elevation · 6,500 ft TD

FormationMD ftSubsea
Red Bluff3,900-1,128
Bell Canyon4,700-1,928
Brushy Canyon6,000-3,228
Delaware6,300-3,528

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.