TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 2.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-1,000-2,000-3,000-4,000SUBSEA FTA1,138 FT ELB1,203 FT ELGunsightGunsight

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 Ero #971ER
  • BArthur Ranch #1
FormationAB
Coleman Junction595 MD 543COLEMAN JUNCTION - CORROSIVE ZON—
Tannehill244 MD 894TANNEHILL SAND—
Saddle Creek-15 MD 1,153—
Dyson Lime-397 MD 1,535—
Cisco—-587 MD 1,790
Gunsight-742 MD 1,880GUNSIGHT SAND-301 MD 1,504
Castlebury Lime-1,082 MD 2,220—
Canyon—-1,405 MD 2,608
Strawn—-2,035 MD 3,238STRAWN SAND
Bryson—-2,723 MD 3,926BRYSON SAND
KMA-2,875 MD 4,013—
Seymour Sand-3,281 MD 4,419—
Atoka-4,062 MD 5,200—

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.