TOOLS · CROSS-SECTION · TEXAS
Well cross-section
Formation tops for up to eight Texas wells side by side, from their completion filings.
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 · 1 well drawn
One more well with tops draws the section. Add one from the wells nearby, or search for one.
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.
- AStone Cutter D #711H
| Formation | A |
|---|---|
| Delaware | -824 MD 3,906 |
| Bell Canyon | -824 MD 3,906 |
| Cherry Canyon | -1,728 MD 4,810 |
| Brushy Canyon | -3,184 MD 6,266 |
| Bone Spring | -4,838 MD 7,920 |
| 1ST Bone Spring | -5,807 MD 8,889 |
| 1ST Bone Spring Sand | -5,807 MD 8,889 |
| 2ND Bone Spring Sand | -6,348 MD 9,430 |
| 2ND Bone Spring | -6,348 MD 9,430 |
| 3RD Bone Spring Carb | -6,874 MD 9,956 |
| 3RD Bone Spring Sand | -7,592 MD 10,674 |
| 3RD Bone Spring | -7,592 MD 10,674 |
| Wolfcamp | -7,969 MD 11,051 |
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.