TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 3.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-1,000-2,000-3,000-4,000SUBSEA FTA397 FT ELB355 FT ELAustin ChalkAustin ChalkWoodbineWoodbine

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.

  • AHawkins Field Unit #1138
  • BHawkins Field Unit #3698
FormationAB
Mdwy-1,190 MD 1,587—
Nacatoch-1,931 MD 2,328—
Nacotoch—-1,992 MD 2,347
Pcgp-2,714 MD 3,111—
Pecan Gap—-2,774 MD 3,129
Tylr-2,854 MD 3,251—
Ltm_ozan-3,306 MD 3,703—
Pecan Gap B—-3,311 MD 3,666
Blsm-3,484 MD 3,881—
Austin Chalk-3,792 MD 4,189-3,820 MD 4,175AUSTIN
Ectr-3,909 MD 4,306—
Egfd-3,984 MD 4,381—
Eagle Ford—-4,081 MD 4,436
Woodbine-4,151 MD 4,548-4,098 MD 4,453

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.