1715 Spanish Plate Fleet

Verdict summary

PinPoint Treasure lists 1715 Spanish Plate Fleet as partially recovered. A hurricane sank an entire Spanish treasure fleet off Florida's Treasure Coast — and storms still wash up gold today. A source-origin review has not been completed for this case, so the earliest traceable teller is UNKNOWN. The published search constraint is Treasure Coast — Sebastian to Fort Pierce, Florida. Estimated value is reported as stated by its source: $400+ million (significant remainder unrecovered).

On July 31 1715, a hurricane sank 11 of 12 Spanish Plate Fleet ships off Florida's east coast. Hundreds of millions in gold and silver have been recovered since 1928, but significant amounts remain. Storms regularly redistribute beach finds.

Case overview: estimated value $400+ million (significant remainder unrecovered); current status partially-recovered; era 1715.

Search area: Treasure Coast — Sebastian to Fort Pierce, Florida

Best modern approach: Post-storm beach detecting (legal below mean high tide) + admiralty-contracted offshore work.

Evidence and provenance: Spanish 1715 manifest records; Real Eight Corp recoveries (1960s–present); 1715 Fleet Society active recoveries; Routine post-storm beach recoveries.

Legal notes: Onshore: legal below mean high tide. Offshore: admiralty contracts and Florida state archaeology law apply.

Source origin: a source-origin review has not been completed for this case, so the earliest traceable teller is recorded as UNKNOWN.

Why this case is worth researching: 1715 Spanish Plate Fleet pairs a documented historical event with an unrecovered-cache claim, which is what the PinPoint Treasure pipeline is built to test — cross-referencing archival sources, geology, mining records, and 1-meter LiDAR terrain where coverage exists. Every claim on this page carries an evidence grade, and grades are never raised to fill a gap.

Recommended workflow for the 1715 Spanish Plate Fleet case: (1) read the primary sources and establish which of them are independent of each other, (2) run the cipher engine on any coded material, (3) scan the highest-probability bounding box with LiDAR where coverage exists, (4) cross-check anomalies against NDVI vegetation stress and iron-oxide satellite signatures, and (5) confirm land status before any field work.