MicroHAMS Club Meeting - January 19, 2016

MicroHAMS Club Meeting
Tuesday, January 19th at 6:00 PM

Agenda
Mike Mraz, N6MZ

Mike_N6MZ

DXpedition to Navassa 2015
When it comes to DXpeditions, our own Mike Mraz leads the way. Come hear about his recent adventure at Navassa island.

This is an invitation to our next MicroHAMS meeting coming up Tuesday, January 19, 2015 (always the 3rdTuesday) at 6:00 PM  at Microsoft Building 35 (see this map or the picture below), Conference Room 4561. Building 35 is near the intersection of 159th Ave NE and NE 40th St on the southeast corner. Parking is available near the front of the building at ground level.

MeetingMap

146.58 MHz simplex will be monitored for anyone who needs help finding the site or for access to the building. (Monitoring is done with handhelds, so range is limited.) Tim’s cell phone number is +1 (425) 898-3815 for those who are not yet licensed or do not have a ham radio. If you’re running late and are locked out, please call us on the radio or phone. We’ll send someone to let you in.

 

PLEASE NOTE: Anyone who is not currently badged for unescorted access to Microsoft buildings MUST be escorted into Building 35 and to conference room 4561 by a badged MicroHAMS member. Do NOT under any circumstances attempt to “tag” onto or “tailgate” Microsoft employees entering Building 35. Please congregate about five minutes before the meeting at the front entrance of the building, which is where the orange circle with the number 1 appears on the map picture above.

 

MicroHAMS meetings are open to club members, those interested in joining the club (see club membership policy at http://www.microhams.com), and guests of club members. Others may also attend a club meeting by sending email to the club at least seven days prior to the meeting. Space for guests is limited.

 

73,

 

Tim Myers, KK7TM

MicroHAMS Secretary

kk7tm@kk7tm.com

Subscribe to MicroHAMS Amateur Radio Club

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe