TOOLS · CROSS-SECTION · TEXAS

2 wells, measured depth

West to east, 0.2 miles end to end. Measured depth: not every well has an elevation.

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

02,0004,0006,0008,00010,000MD FTANO ELEVATIONB2,694 FT ELSanta RosaSanta RosaYatesYatesQueenQueenGrayburgGrayburgSan AndresSan AndresClear ForkClear ForkSpraberrySpraberry

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

Measured depth, feet; the name as filed where it differs; a dash where the well has no top filed for the formation.

  • ACosper 37-48 WSL #251
  • BCosper 37-48 'C1' #231
FormationAB
Santa Rosa1,033 960
Rustler—1,575
Yates2,435 2,435
Seven Rivers—2,660
Queen3,376 3,376
Grayburg3,779 4,065
San Andres4,118 SAN ANDRES - HIGH FLOWS, H2S, CO4,436 SAN ANDRES - HIGH FLOWS, H2S, CO
Glorieta—5,365
Clear Fork6,334 6,370
Spraberry7,291 7,294

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.