TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.5 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-500-1,000-1,500-2,000-2,500-3,000SUBSEA FTA1,056 FT ELB1,064 FT ELSaddle CreekSaddle CreekGunsightGunsight

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.

  • AWaggoner DS-East #151DS
  • BWaggoner DS-East #138T
FormationAB
Coleman Junction428 MD 628COLEMAN JUNCTION - CORROSIVE ZON—
Tannehill75 MD 981TANNEHILL SAND—
Saddle Creek-187 MD 1,243-184 MD 1,248
Breckenridge Lime-676 MD 1,732—
Gunsight-949 MD 2,005GUNSIGHT SAND-945 MD 2,009GUNSIGHT SAND
Castlebury Sand-1,361 MD 2,417—
Canyon—-1,701 MD 2,765CANYON REEF
Palo Pinto—-2,717 MD 3,781
Strawn—-2,782 MD 3,846
Kma Lime-3,135 MD 4,191—

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.