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 FTA397 FT ELBNO ELEVATIONFrioFrioYeguaYeguaQueen CityQueen CityReklawReklawWilcoxWilcoxCarrizoCarrizoAustin ChalkAustin Chalk

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.

  • AKilimanjaro Unit #105H
  • BColleen Unit #20H
FormationAB
Queen City2,856 2,986
Frio3,200 FRIO - DISPOSAL500 FRIO - DISPOSAL
Reklaw3,259 3,389
Yegua4,000 YEGUA - DISPOSAL2,082 YEGUA - DISPOSAL
Wilcox3,979 WILCOX - DISPOSAL4,109 WILCOX - DISPOSAL
Carrizo4,055 4,185
Austin Chalk10,539 AUSTIN CHALK - H2S10,664 AUSTIN CHALK - H2S
Eagle Ford—10,879 EAGLE FORD - H2S

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.