Lake Shore and Lake City Units Lead Successful Rescue of Sailboat Crew Near Louisa Drive
Statistics
Narrative
Fairview Township, PA – Early this morning, Fairview Fire and Rescue, Lake Shore Fire Department, and the Lake City Fire Company were dispatched for a watercraft in distress near 8200 Louisa Drive. En route, crews were informed that a 30-foot sailboat, carrying four people, was taking on water about 50 feet offshore. Lake Shore’s 508 responded to Walnut Creek Access to rendezvous with their Rescue Boat 519, while Fairview’s ambulance 527 responded to Avonia Beach. Within approximately 10 minutes of the initial dispatch, Lake City units 578 and 579 responded to Avonia Beach for a shoreline launch with their amphibious boat. Rescue 539 (Fairview) and Lake City’s drone also responded to the scene. Upon arrival, 531 confirmed that all individuals were confirmed to be wearing life jackets.
Lake Shore’s Rescue Boat 519, stationed at Walnut Creek, responded to the sailboat. Lake Shore’s 519 and Lake City’s 578 arrived at the vessel, which was in shallow water about 4 feet deep. Lake City’s drone provided aerial overwatch during the rescue operations. Lake City’s 578 was able to navigate close enough to transfer all four individuals safely onto their boat. The individuals were then transferred to 519, which transported them to the Walnut Creek Access. A small boat from the Coast Guard Station Erie also arrived on scene shortly after all souls were transferred onto 519. The XPO from Coast Guard Erie was on the shore side communicating with county-based assets.
Lake City’s 578 remained on the scene for a short time to ensure the sailboat was secured until a towing company could arrive. All units returned to the Walnut Creek Access without incident, and no injuries were reported.
This response highlights effective communication, strategic use of assets, and the seamless coordination between multiple agencies to ensure a successful rescue operation.
Response Timeline
Disclaimer: The timeline provided is for illustrative purposes only and may not be entirely accurate due to potential errors in recorded transmissions. Consequently, this timeline should not be used to evaluate responses to incidents. If you notice a significant discrepancy, please contact [email protected].