TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 0.2 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,500SUBSEA FTA1,012 FT ELB1,010 FT ELCiscoCiscoGunsight LimeGunsight LimeGunsight SandGunsight SandCanyonCanyonStrawnStrawnKMAKMA

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.

  • AFirst National #107
  • BFirst National #110
FormationAB
Cisco-130 MD 1,14262 MD 948
Tannehill—-170 MD 1,180
Gunsight Lime-791 MD 1,803-751 MD 1,761
Gunsight Sand-834 MD 1,846-759 MD 1,769
Thomas Sand—-1,410 MD 2,420
Canyon-1,860 MD 2,872CANYON SAND-1,862 MD 2,872CANYON SAND
Strawn-2,691 MD 3,703-2,384 MD 3,394
Bluff Creek Sand—-2,698 MD 3,708
KMA-2,820 MD 3,832-2,691 MD 3,701

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.