TOOLS · CROSS-SECTION · TEXAS

2 wells, subsea datum

West to east, 1.7 miles end to end. Depths are elevation minus measured depth, so tops line up regardless of surface terrain; a value above zero sits above sea level. 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 →

AMartin, Robert #24 tops×BTurnipseed #13 tops×
Download
0-1,000-2,000-3,000-4,000SUBSEA FTA1,116 FT ELB1,218 FT ELStrawnStrawn

shaded: a formation down to the next one filed in both wellsfiled in one well onlyhover a top or a name to pick out one formation

Tops by well

Subsea feet, with measured depth beneath; a dash where the well has no top filed for the formation.

FormationAMartin, RobertBTurnipseed
Palo Pinto—737MD 481
Strawn-1,808MD 2,924513MD 705
Atoka—-3,056MD 4,274
Pregnant Shale-3,359MD 4,475—
Marble Falls-3,994MD 5,110—
Ellenburger-4,664MD 5,780—

Add wells nearby

Around
Loading the map…
In the sectionMatchesFiltered out

Only wells with a location on file can be found by distance; a well with tops but no location can still be added by name or API number.

The tops, as filed

AMartin, Robert #2 42-237-39403

Oakridge Oil and Gas, LP · Jack · 1,116 ft elevation · 6,500 ft TD

FormationMD ftSubsea
StrawnMIDDLE STRAWN LIMESTONE2,924-1,808
Pregnant Shale4,475-3,359
Marble Falls5,110-3,994
EllenburgerELLENBERGER5,780-4,664

BTurnipseed #1 42-237-40264

White Knight Production LLC · Jack · 1,218 ft elevation · 7,000 ft TD

FormationMD ftSubsea
Palo Pinto481737
Strawn705513
AtokaATOKA CONGLOMERATE4,274-3,056

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.