[Elecraft] Cruise Lines

[jeff griffin]

Try a different cruise line. Last year AMSAT had their annual meeting on a cruise ship. Radio operation was allowed on HF VHF and UHF without any issues from the ships officers. 

73 Jeff kb2m

-----Original Message-----
From: elecraft-bounces at mailman.qth.net [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Joseph Shuman via Elecraft
Sent: Wednesday, October 16, 2019 10:48 AM
To: Elecraft Mail Server
Subject: [Elecraft] Cruise Lines

Going on a cruise in a few months, so I emailed the cruise line about operating at sea with a KX2.  Here is the reply:  “Ham Radios, Shortwave Radios or Satellite Radios (portable or standalone) may not be brought on board as they pose a risk of interfering with onboard navigational equipment.”  OK!  The line has a right to say no. But...

I have operated my KX2 QRP 40m portable with a GPS and Laptop in the transmission RF envelope with no interference problems.  I know maritime uses mostly 156-162 MHz for ship to ship or ship to shore, some specific HF frequencies (outside of our bands) are allocated for emergency communications and satellite navigation is typically 1150-1610 MHz.  Most ships now have WiFi and rely on phone apps for on-board communication, so there are a few thousand phones on board operating in the GHz range that are no problem.  Also, as a USN Sub Service vet I learned a few things about at-sea comms 40-some years ago, and considering the improvements in our technology...

Sorry if I seem to be ranting, but opportunities to operate at sea (for a OM in Ohio) are rare and this cruise line’s position seems to me to be the easy answer: ban all Hams outright.

Keeping Watch-
shu KE8KJZ

Joe Shuman
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to kb2m at arrl.net