TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

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

ADeets 33 #12H4 tops×BDeets 33 #11H4 tops×
Download
1,000-0-1,000-2,000-3,000SUBSEA FTA2,648 FT ELB2,649 FT ELGrayburgGrayburgSan AndresSan AndresSpraberrySpraberryWolfcampWolfcamp

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.

FormationADeets 33BDeets 33
Grayburg1,273MD 1,3751,274MD 1,375
San Andres938MD 1,710939MD 1,710
Spraberry-1,565MD 4,213-1,564MD 4,213
Wolfcamp-3,491MD 6,139-3,431MD 6,080

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

ADeets 33 #12H 42-235-36398

Foreland Operating, LLC · Irion · 2,648 ft elevation · 9,600 ft TD

FormationMD ftSubsea
Grayburg1,3751,273
San Andres1,710938
Spraberry4,213-1,565
Wolfcamp6,139-3,491

BDeets 33 #11H 42-235-36397

Foreland Operating, LLC · Irion · 2,649 ft elevation · 9,600 ft TD

FormationMD ftSubsea
Grayburg1,3751,274
San Andres1,710939
Spraberry4,213-1,564
Wolfcamp6,080-3,431

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.