TOOLS · CROSS-SECTION · TEXAS
2 wells, subsea datum
West to east, 0.2 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.
- AKissell #16WI
- BDonna Wright #3
| Formation | A | B |
|---|---|---|
| Coleman Junction | 108 MD 2,114COLEMAN JUNCTION - CORROSIVE, SW | 105 MD 2,095COLEMAN JUNCTION - CORROSIVE, SW |
| Saddle Creek | -711 MD 2,933SADDLE CREEK - DISPOSAL | -712 MD 2,912SADDLE CREEK - DISPOSAL |
| Flippen - Disposal | -816 MD 3,038 | -805 MD 3,005 |
| Hope Lime - Disposal | -1,007 MD 3,229 | — |
| King Sand - Disposal | -1,134 MD 3,356 | -1,130 MD 3,330 |
| Palo Pinto | -1,714 MD 3,936PALO PINTO LIME - DISPOSAL | -1,717 MD 3,917PALO PINTO LIME - DISPOSAL |
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.