NOAA’s Beacon Registration Database (RGDB)

1. NOAA’s Beacon Registration Database(RGDB) www.beaconregistration.noaa.gov NOAA SARSAT PROGRAM

2. Topics To Be Covered • RGDB – mass mailing efforts • SAR User Access • Creation of accounts • Resolving lock out situations • Deactivating accounts • How RGDB is updated with RCC feedbacks • SAR Usage of RGDB • Suggestions on how RCCs can help improve RGDB info

3. RGDB Mass Mailing Effort • Started in May, 2009 • Finished December, 2009 • Emailed/mailed a special letter to all registered owners with registration information to particularly pay attention to beacon id Results • NOAA surprised to learn that beacon owners made lot more mistakes on beacon id vs NOAA data entry personnel • Lots of false incorrect beacon ids – older beacons • IRT Recommendations – NOAA has started to look into ways to make changes to minimize chance of error on beacon ids by any user

4. Access to RGDB &IHDB by USCG • Anytime a new user joins the USCG RCC, the following needs to happen: • An email request needs to go to USCG headquarters to: • LCDR Kathy Niles U.S. Coast Guard Headquarters Office of Search and Rescue (CG-534) SARSAT Liaison Officer Tel: (202) 372-2089 katherine.m.niles@uscg.mil

5. Access to RGDB &IHDB by USCG • Once LCDR Niles validates the user to be added for the RGDB and IHDB, a Microsoft Excel file is sent to NOAA with the following information: • User Name • First Name • Last Name • Organization Name • Phone Number • Email Address

6. Access to RGDB &IHDB by USCG • NOAA: • creates a user account and password for each new member for RGDB and IHDB • encrypts the new output file with the password information • sends the encrypted file to LCDR Niles to be distributed to the respective USCG RCCs

7. Access to RGDB &IHDB by AFRCC • Dan Conley sends an email request: • Dan Conley, USAF AFRCC 850-283-5688 Danny.Conley@tyndall.af.mil

8. Access to RGDB &IHDB by AFRCC • NOAA: • creates a user account and password for each new member for RGDB & IHDB • relays the user ids and passwords for IHDB over the phone to Mr. Conley • an encrypted file could not be received by AFRCC • in future, hope to exchange this information electronically with AFRCC

9. Access to RGDB & IHDB by AKRCC • When a new user joins the AKRCC, the following needs to happen: • An email request comes to NOAA from: • Current alternate contact: Dan Conley, USAF • AFRCC • 850-283-5688 • Danny.Conley@tyndall.af.mil • In future who will be the permanent contact: • Capt Laird??

10. Access to RGDB &IHDB by AKRCC • NOAA: • creates a user account and password for each new member for RGDB and IHDB • relays the user ids and passwords for IHDB over the phone to Mr. Conley at this time • an encrypted file could not be received by AFRCC • hope is the ability to exchange this information electronically with AKRCC in the near future

11. Lock Out Procedure • If a RCC user is locked out of the RGDB or the IHDB system: • Only call the USMCC 24/7 at 301.817.4576 • Provide the specific user Id and subsystem and which organization the user is calling from • A new password will be issued to the user for this subsystem • Please ignore the phone number displayed on the Registration Database website when a SAR user id is locked out. • 301.817.4515 (this line is for beacon owners only and not for SAR users)

12. Inactive User Accounts • When controllers leaveNOAA needs the following to take away access to these subsystems: • An electronic file containing: • User name • First name • Last name • Organization name • Phone number • Email address

13. 406 MHz Registration Requirements • All 406 MHz beacons coded with a USA country code must be registered with NOAA • Title 47 - Parts 80, 87, and 95 in the Code of Federal Regulations • Owners should be informed of the following: • ``WARNING--failure to register their beacon with NOAA before installation could result in a monetary forfeiture being issued to the owner.''

14. 406 MHz Proof of Registration • NOAA has updated letters to state the following: • The proof of registration decal or the proof of registration data sheet provided by NOAA may be used as proof of beacon registration • Currently, this guidance only applies to ELTs when owners call us • In the future, NOAA will customize the letters by beacon registration type to satisfy the proof of registration requirement: • Decals will not be issued for ELTs • Decals will be issued for EPIRBs • Decals may be issued for PLBs

15. RCC Feedback When beacons are activated, and we get the initial feedback on a case from the RCCs, the remarks field of the RGDB is possibly updated when the registration accuracy section of the IHDB section is marked as inaccurate and the additional remarks has new useful information for the beacon registration record • It is the only field updated because we cannot update the specific fields, since the feedback is not directly from the owner / operator • The update includes: • date and source of information • changed information (Owner can change information in the “Remarks” field.) • Therefore the RCC controllers must ensure that they check the “Remarks” field

16. RCC Feedback • The RCC should provide specific new phone number information when it is different than what is listed on the registration. Having a name with a phone number is always preferred. John Doe’s new cell number is XXX-XXX-XXXX. • “NONE OF THE BEACON REGISTRATION CONTACT NUMBERS WOULD WORK.” – prefer comments such as: • tried all owner/operator phone numbers, • tried all vessel numbers, looked up the vessel by documentation number, tried all emergency point of contact numbers. They all had a recording to indicate the number is disconnected or out of service or re-assigned to someone else.

17. RCC Feedback • “Vessel was sold multiple times and is in Mexico contacted RCC Mexico to attempt to locate with negative results.” • Updated the RGDB with: • “7/1/09-per CDG07 Vessel was sold multiple times” • We updated due to the fact the decal was quite old and adding these comments could assist with the rescue. If it has a current decal, it could be misleading due to the fact the owner may still have the beacon and not the vessel and updating the comment could possibly give false hope to search for the vessel when the owner may still have the beacon.

18. RCC Feedback “OWNER RPTED SELLING VESSEL IN 2005” What happened to the beacon? Was the beacon sold with the vessel or did the owner keep it? “BEACON IS ON A DIFFERENT TAIL” If a beacon is on a different tail, indicate beacon on a different tail than on registration and also provide the current tail number. Is this a temporary change or permanent change? Is the owner planning on updating this information with NOAA if it is a permanent change?

19. RGDB Usage For Year 2009

20. RGDB Accuracy For Year 2009

21. Suggestions On How RCC Personnel Can Help • Inform new and existing beacon owners regarding the option to register, make updates to registration information or re-register the beacons via Web. • Inform the owner to make sure they list phone numbers for owner/operator information which will add value to Search and Rescue efforts if the beacon goes off • Inform the owner/operator not to list the same phone numbers under owner operator section and the emergency point of contact section • Emergency point of contacts should be someone who will not likely be involved if there is an emergency • Inform owners to make updates when information changes and not wait till the renewal time

22. Home Port State For Unlocated Alerts ELTs & EPIRBs • SRR chosen per Home Port State provided • If Home Port State not provided, RCC chosen based on mailing state PLBs • SRR chosen per mailing state

23. GeoSort 406 RGDB SRR Assignments

24. Future SRR Assignment Issues • NOAA needs to assign SRR by homeport country • The Registration Database software needs to be modified • Agreement from the RCCs what SRR to assign • Address ELT, EPIRB, PLB separately • When HomePort country is not provided, the SRR will • be provided using mailing country • Registration mechanics • Drop down list for home port/mailing country