North Carolina Crinoid Stem Identification
Crinoid Stem is a realistic North Carolina fossil profile built around disk-like stem segments from sea lilies in shallow marine limestone. In this state, success usually comes from learning roadcuts through limestone and shale, coal spoils, and stream gravels, then timing runoff, reservoir drawdown, surf cuts, or road work that exposes fresh fossil-bearing rock instead of hunting blindly.
Key Traits
- ●stacked columnals
- ●central hole
- ●star or wagon-wheel cross sections
- ●Check roadcuts through limestone and shale, coal spoils, and stream gravels
Era
Paleozoic
Type
echinoderm
Route stack
Turn North Carolina Crinoid Stem into a month, law, metro, and ground plan.
These links move the page out of taxonomy mode and back into trip planning, so users can answer when to go, where to start, and what legal layer to check before they leave the main species or find guide.
Timing layer
Monthly state routes
Law layer
North Carolina state guide
Fossil collecting rules in North Carolina vary by land status and fossil type. Common invertebrate fossils may be collectible on some public lands, but vertebrate fossils, protected park units, tribal lands, and cultural sites require a much higher level of care and often a permit. This is especially relevant in Triassic basins, shark teeth, and mountain stream fossils.
Open the law layer →Metro layer
City hubs in North Carolina
Place layer
Trail and ground routes
Location: Pisgah National Forest
National Forest • Seasonal edible mushrooms, Common invertebrate fossils in float
Location: Nantahala National Forest
National Forest • Seasonal edible mushrooms, Common invertebrate fossils in float
Location: Uwharrie National Forest
National Forest • Seasonal edible mushrooms, Common invertebrate fossils in float
Location: Croatan National Forest
National Forest • Seasonal edible mushrooms, Common invertebrate fossils in float
Take TroveRadar into the field
Carry the plan, the species notes, and the access checks outside.
Use the mobile app for offline reference, private find logging, route memory, and the working notes that matter after the browser window closes.