TOOLS · CROSS-SECTION · TEXAS
2 wells, subsea datum
West to east, 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 | ASeminole San Andres Unit | BSeminole San Andres Unit |
|---|---|---|
| Rustler | 1,247MD 2,057 | — |
| Tansill | 274MD 3,030 | — |
| Yates | 144MD 3,160 | 131MD 3,154 |
| 1ST Limestone | — | -913MD 4,198 |
| 2ND Limestone | — | -1,203MD 4,488 |
| San Andres | — | -1,387MD 4,672 |
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
ASeminole San Andres Unit #5505R 42-165-34945
OXY USA Inc. · Gaines · 3,304 ft elevation · 6,000 ft TD
| Formation | MD ft | Subsea |
|---|---|---|
| Rustler | 2,057 | 1,247 |
| Tansill | 3,030 | 274 |
| Yates | 3,160 | 144 |
BSeminole San Andres Unit #5529 42-165-33191
OXY USA Inc. · Gaines · 3,285 ft elevation · 6,000 ft TD
| Formation | MD ft | Subsea |
|---|---|---|
| Yates | 3,154 | 131 |
| 1ST Limestone | 4,198 | -913 |
| 2ND Limestone | 4,488 | -1,203 |
| San Andres | 4,672 | -1,387 |
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.