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 →
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.
| Formation | ATyson Fee 44 | BTyson Fee 44 |
|---|---|---|
| Cherry Canyon | -114MD 3,228 | -114MD 3,228 |
| Brushy Canyon | -1,309MD 4,423 | -1,309MD 4,423 |
| Bone Spring | -2,814MD 5,928 | -2,814MD 5,928 |
| Wolfcamp | -5,805MD 8,919 | -5,805MD 8,919 |
Add wells nearby
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
ATyson Fee 44 #3H 42-109-33995
Capitan Energy, Incorporated · Culberson · 3,114 ft elevation · 12,000 ft TD
| Formation | MD ft | Subsea |
|---|---|---|
| Cherry Canyon | 3,228 | -114 |
| Brushy Canyon | 4,423 | -1,309 |
| Bone Spring | 5,928 | -2,814 |
| Wolfcamp | 8,919 | -5,805 |
BTyson Fee 44 #4H 42-109-33998
Capitan Energy, Incorporated · Culberson · 3,114 ft elevation · 12,000 ft TD
| Formation | MD ft | Subsea |
|---|---|---|
| Cherry Canyon | 3,228 | -114 |
| Brushy Canyon | 4,423 | -1,309 |
| Bone Spring | 5,928 | -2,814 |
| Wolfcamp | 8,919 | -5,805 |
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.