View Categories

Corsair

3 min read

Identification & Site Information

Vessel Name: Corsair

Type: Schooner

Location: Lake Huron, off Highlands Sauble, Saginaw Bay

Date of Loss: October 2, 1872

Cause of Loss: Heavy gale, foundering

Cargo: Approximately 50 tons of iron ore (some stowed on Deck)

Depth: Not specified

Vessel Type Description

The Corsair was a Schooner, a versatile and commonly used vessel type on the Great Lakes in the 19th century. Designed for bulk cargo transport, schooners like the Corsair were equipped to handle iron ore, grain, and coal while navigating the challenging waters of the lakes. Despite their robust design, these vessels were often at the mercy of the unpredictable and severe weather that frequently struck the Great Lakes region.

History

Final Voyage:

•On the night of October 2, 1872, the Corsair encountered a severe storm while navigating Lake Huron, near Thunder Bay Light.

•The Schooner began to take on water due to the gale’s intensity. Despite the crew’s efforts to pump out the water, the situation worsened.

•In a desperate attempt to save the vessel, the captain steered toward Tawas Bay, seeking shelter.

•The crew jettisoned iron ore from the Deck to lighten the load, but their efforts proved futile. The Schooner ultimately Foundered and sank.

Survivors:

•Two crew members, Mr. Grady and Thomas B. Foley, managed to survive by clinging to debris, including a piece of Deck and a boat shell.

•After enduring 36 hours adrift, they were rescued by the Propeller Steamer City of Boston, whose captain and crew provided care.

•The remaining crew, including Captain G.H. Snow, tragically perished in the disaster.

Final Disposition

The Corsair sank in Saginaw Bay, a region notorious for treacherous waters and shipwrecks. It joined the ranks of several other vessels lost in the same storm, which resulted in widespread maritime destruction and significant loss of life.

Located By & Date

The wreck of the Corsair has not been conclusively located, and no precise coordinates are available. Its remains are presumed to rest at an undetermined depth within Saginaw Bay.

Current Condition & Accessibility

Condition: The site is believed to be uncharted and unexplored, with the wreck’s exact state unknown. Due to the age of the wreck, any remains are likely heavily deteriorated, buried under sediment, or scattered across the lakebed.

Accessibility: The absence of specific location data makes this site inaccessible for divers and researchers at this time.

Notices to Mariners (NOTMARs)

There are no current NOTMARs associated with the Corsair. Mariners should exercise caution when navigating in Saginaw Bay, a historically hazardous area, particularly during storms or in low Visibility conditions.

Historical Significance

The sinking of the Corsair highlights the perilous nature of maritime navigation on the Great Lakes in the 19th century. The vessel’s loss underscores the challenges faced by schooners transporting heavy cargoes under adverse weather conditions. This tragedy serves as a somber reminder of the risks sailors undertook to sustain the region’s vital trade routes.

Resources & Links

Maritime History of the Great Lakes Database: maritimehistoryofthegreatlakes.ca

David Swayze Shipwreck File: Repository of historical Great Lakes shipwrecks.

Conclusion

The Corsair’s loss during the gale of October 1872 epihttps://shotlinediving.com/wp-content/uploads/52895851813_b64678c0f7_c.jpgizes the dangers of Great Lakes sailing in an era before modern forecasting and navigation technology. Its story, marked by heroism and tragedy, contributes to the maritime history of Lake Huron and the broader Great Lakes region. Although its exact location remains a mystery, the legacy of the Corsair and its ill-fated crew endures.

Tags:

#CorsairSchooner #LakeHuronShipwreck #SaginawBayDisaster #GreatLakesStorm #MaritimeHistory


Discover more from Shotline Diving - The Great Lakes Goto

Subscribe to get the latest posts sent to your email.

Powered by BetterDocs

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.