TOOLS · CROSS-SECTION · TEXAS
2 wells, subsea datum
West to east, under 0.1 miles end to end. Subsea datum.
How to read it →How to read it ↓
Each column is a well, lettered in the order drawn: west to east when every well has a location, or the order you list them (drag a well in the list, or switch to "As listed"). A well with no tops filed is listed but not drawn.
Under the subsea datum depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. When not every well reports an elevation the section is in measured depth and the columns are not datum-aligned.
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 →Section · 2 wells drawn
shaded: a formation down to the next one filed in both wellsfiled in one well onlypoint at or tap a top to read it
Tops by well
Subsea feet, with measured depth beneath; the name as filed where it differs; a dash where the well has no top filed for the formation.
- ALasca Butler Searcy Trust #8
- BLasca Butler Searcy Trust #6
| Formation | A | B |
|---|---|---|
| Jackson | -1,092 MD 1,448JACKSON-YEGUA - DISPOSAL | -1,074 MD 1,430JACKSON-YEGUA - DISPOSAL |
| Cook Mountain | -1,944 MD 2,300 | -1,968 MD 2,324 |
| Queen City | -2,966 MD 3,322 | -2,978 MD 3,334 |
| Wilcox | -4,257 MD 4,613 | -4,290 MD 4,646 |
| Austin Chalk | -11,128 MD 11,484 | -11,107 MD 11,463 |
| Eagle Ford | -11,294 MD 11,650EAGLE FORD - H2S | -11,178 MD 11,534EAGLE FORD - H2S |
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.