TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.3 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,000SUBSEA FTA1,152 FT ELB1,136 FT ELGunsightGunsightMilham SandMilham SandCanyonCanyonPalo PintoPalo Pinto

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 Grayback SE #811SE
  • BWaggoner Grayback SE #819SE
FormationAB
Dyson Lime-788 MD 1,940—
Dyson Sand—-823 MD 1,959
Breckenridge Lime—-860 MD 1,996
Gunsight-1,082 MD 2,234GUNSIGHT LIME-1,097 MD 2,233GUNSIGHT LIME
Noble Lime—-1,245 MD 2,381
Milham Sand-1,275 MD 2,427-1,284 MD 2,420
Castlebury Lime-1,395 MD 2,547—
Canyon-1,695 MD 2,847-1,704 MD 2,840
Palo Pinto-2,141 MD 3,293-2,171 MD 3,307

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.