Here are some of the cases reported last week that involved the use of emergency distress beacons and the SARSAT (Search and Rescue Satellite-Aided Tracking) System.
A SARSAT rescue is counted when a beacon alert was the primary means of notification or primary locating method for a rescue.
3 July 2009: A 406 MHz EPIRB was activated 13 miles east of Indian River Inlet, Delaware. A mayday call also was received about the same time by the Coast Guard from a crew member after the boat capsized. A position was determined by the Rescue 21 System and Emergency Positioning Indicating Radio Beacon (EPIRB). The Coast Guard Lantarea used both the EPIRB data and the Rescue 21 system to get a good location of the vessel. Lantarea launched a helicopter and a rescue boat from Station Indian River to the scene. The rescue boat recovered the three people. Three SARSAT Rescues.
6 July 2009: A 406 MHz distress signal was activated 5 NM west of Sarasota, Florida. A sailing vessel with one person on board, had run aground. Coast Guard District 7 received the alert and contacted the owner’s wife. His wife stated that the vessel was in route from Barrington Beach to Titusville, Florida. Coast Guard launched a helicopter and a small boat to the scene which located the grounded vessel. The small boat recovered the person from the vessel. One SARSAT Rescue.
3 July 2009: A 406 MHz EPIRB was activated 13 miles east of Indian River Inlet, Delaware. A mayday call also was received about the same time by the Coast Guard from a crew member after the boat capsized. A position was determined by the Rescue 21 System and Emergency Positioning Indicating Radio Beacon (EPIRB). The Coast Guard Lantarea used both the EPIRB data and the Rescue 21 system to get a good location of the vessel. Lantarea launched a helicopter and a rescue boat from Station Indian River to the scene. The rescue boat recovered the three people. Three SARSAT Rescues.
6 July 2009: A 406 MHz distress signal was activated 5 NM west of Sarasota, Florida. A sailing vessel with one person on board, had run aground. Coast Guard District 7 received the alert and contacted the owner’s wife. His wife stated that the vessel was in route from Barrington Beach to Titusville, Florida. Coast Guard launched a helicopter and a small boat to the scene which located the grounded vessel. The small boat recovered the person from the vessel. One SARSAT Rescue.
8 July 2009: A 406 MHz distress signal was activated in the Bering Sea, 41 NM northwest of Point Hope, Alaska. A Norwegian row boater became exhausted when he encountered high winds and high seas. He called via satellite phone to Alaska State Troopers and gave approximate coordinates. The Troopers then sent the distress to the Alaska Rescue Coordination Center (AKRCC). AKRCC received Sarsat alert coordinates and then sent the message to Coast Guard District 17 (CGD17). The AKRCC and CGD17 sent rescue teams to the scene. Both fixed wing and helicopters with Pararescuemen were sent to the scene. The boater was rescued and flown back to Norton Sound Medical Center. One SARSAT Rescue.
4 July 2009: A 406 MHz ELT activated on Ocean City Municipal Airport, NJ. On takeoff, the pilot swerved on the runway to avoid geese. The aircraft departed the runway and blew a tire. Air Force Rescue Coordinate Center (AFRCC) used the registration information to contact owner. Based on information from the owner, the AFRCC contacted the airport tower which had witnessed the incident and had already notified the nearby emergency crews. The Firefighters put out the flames on aircraft. One person was in distress and rescued. NOT A SARSAT RESCUE
4 July 2009: A 406 MHz ELT activated on Ocean City Municipal Airport, NJ. On takeoff, the pilot swerved on the runway to avoid geese. The aircraft departed the runway and blew a tire. Air Force Rescue Coordinate Center (AFRCC) used the registration information to contact owner. Based on information from the owner, the AFRCC contacted the airport tower which had witnessed the incident and had already notified the nearby emergency crews. The Firefighters put out the flames on aircraft. One person was in distress and rescued. NOT A SARSAT RESCUE
07 Jul 2009: A 406 MHz ELT activated at Winder-Barrow Airport, GA, when the pilot made a hard landing on the runway and came to a stop at a grass field area nearby the airport. Personnel at the airport tower witnessed the incident and sent an emergency crew to the crash site. Air Force Rescue Coordinate Center was later notified of the distress alert. When AFRCC called nearby airport of crash site, pilot had been rescued and aircraft had already been secured. NOT A SARSAT RESCUE
There are currently 247,460 beacons registered in NOAA's 406 MHz Beacon Registration Database. If you own or use a beacon, ensure it is properly registered.
There are currently 247,460 beacons registered in NOAA's 406 MHz Beacon Registration Database. If you own or use a beacon, ensure it is properly registered.
Posts
0 comments:
Post a Comment
We welcome your comments on postings at all Coast Guard sites/journals. These are sponsored by the U.S. Coast Guard to provide a forum to talk about our work providing maritime safety, security and stewardship for the American people to secure the homeland, save lives and property, protect the environment, and promote economic prosperity.
All comments submitted are moderated and will be reviewed before posting. The Coast Guard retains the discretion to determine which comments it will post and which it will not. We expect all contributors to be respectful. We will not post comments that contain personal attacks of any kind; refer to Coast Guard or other employees by name; contain offensive terms that target specific ethnic or racial groups, or vulgar language. We will also not post comments that are spam, are clearly off topic or that promote services or products.
We will make our best effort to promptly post those comments that are consistent with the Comment Policy, but given the need to manage federal resources, moderating and posting of comments will occur only during regular business hours, Monday through Friday. Comments submitted outside of business hours will be read and posted as quickly as possible.