TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.9 miles end to end. Subsea datum.

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

-0-2,000-4,000-6,000-8,000SUBSEA FTA3,214 FT ELB3,237 FT ELBell CanyonBell CanyonDelawareDelawareCherry CanyonCherry CanyonBrushy CanyonBrushy CanyonBone SpringBone Spring

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.

  • ABrunson E 805 #1H
  • BEl Patron Unit #522H
FormationAB
Red Bluff-686 MD 3,900—
Bell Canyon-2,183 MD 5,397-2,143 MD 5,380
Cherry Canyon-2,966 MD 6,180-3,145 MD 6,382
Delaware-3,286 MD 6,500-2,143 MD 5,380
Brushy Canyon-4,514 MD 7,728-4,836 MD 8,073
Bone Spring-6,085 MD 9,299BONE SPRINGS-6,206 MD 9,443
Wolfcamp-9,136 MD 12,350—

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.