WORLDWIDE DISPATCH - 1 MAY 2008 - 0150 UTC
--------------------------------------------------------------------------------------------------------
Dedicated to Emergency Communications by RADIO
EMCOMM
MONTHLY
Official
Journal of the World Radio Relay League
www.wrrl.org
--------------------------------------------------------------------------------------------------------
VOL. 4 -- No. 12 ONLINE:
www.emcomm.org/em
MAY 2008
--------------------------------------------------------------------------------------------------------
"RADIOS DON'T COMMUNICATE. PEOPLE COMMUNICATE!"
--------------------------------------------------------------------------------------------------------
TABLE OF CONTENTS
The EM
PHILOSOPHY - MAYDAY!
SHORT CIRCUITS - News and Announcements
The EM
ADVISOR - "Q and A"
ICS
PERSPECTIVES - by
WRRL
NEWS and NETS
TRAFFIC HANDLING - ERROR
CORRECTION?
NETWORK NEWS - "N.E.T.S." (Update)
SHOW US YOUR SHACK
FEATURE
- "ARE YOU FIXED, MOBILE, or PORTABLE?"
EMCOMM SPECIALTY ITEMS - Stuff for
NEW SUBSCRIBERS and CONTRIBUTORS
SUPPORT OUR SUPPORTERS
REFERENCE and RESOURCE SECTION
∙
-
∙
-
∙
The EM PHILOSOPHY
MAYDAY!
MAYDAY is the internationally recognized call for extreme distress on voice
radio. When heard, it instantly sends a chill up one's spine, and even the most
seasoned radio operator's adrenal glands instantly release a bolus of adrenalin
into the bloodstream as all your senses and responses go on HIGH ALERT.
All of your skills and training must be recalled immediately, but you must
remain cool, calm and collected!
I have never heard an actual MAYDAY or an SOS, the international call for
extreme distress in Morse (except in movies). Most of us probably never will.
But I have heard "I have EMERGENCY traffic" or "BREAK, BREAK" (also a distress
call). A few of those times there actually was a legitimate emergency, but
most of the times it was not. But whether or not it was a real emergency,
those words will definitely get your attention!
I once heard "I have EMERGENCY traffic" on my county repeater linked system.
The calling person was reporting a traffic accident with injuries. The
calling operator's own family was involved. The call sign given was
non-U.S. but /W6 (stoke W6). This visitor to the U.S. spoke with a distinct
foreign accent, but he remained calm and knew and used proper operating
procedure including ITU phonetics.
Before I could key and respond, an operator replied to his distress call.
What followed was an embarrassment to all of amateur radio. The "assisting
operator" did not know ITU phonetics, and when the calling operator attempted to
report the accident's location (using ITU phonetics), the assisting operator
fumbled the spellings terribly. This (coupled with the caller's heavy
accent), confused the nice old gentlemen ham who wanted so-badly to help.
I sensed the frustration in the voices of both operators.
As a general rule, it is proper procedure to allow the first station that
responds to handle the traffic, and it is not a good practice to interrupt a
situation like this. At least two other operators interrupted and further
complicated the situation. My own frustration grew. It took all the
restraint I could muster to keep from butting in!
I was able to understand the calling person's location, dialed 9-1-1, and
reported the accident while the incompetent hams continued to fumble.
Within 15 minutes, the calling operator said that a fire/rescue unit was on
scene and thanked "all who helped". I never made one transmission.
ARE
YOU PREPARED? I hear operators every day who still do not
know, or refuse to use, ITU phonetics. I say that all hams should know and
use all proper operating procedures, even for routine traffic and nets and
even for hobby communications. Both on voice and Morse.
GET IN
THE HABIT! You never know when you may be called upon
to assist someone in distress. --
Editor
OPERATING PROCEDURES: www.wrrl.org/operating/
∙
-
∙
-
∙
SHORT CIRCUITS
IN THE BEGINNING...THERE WAS SPARK...
The link below is to an 32 minute (Windows Player) audio file of what maritime
traffic sounded like on the North Atlantic on the 600 meter band in the 1920's.
It's an audio file created by George Ahrens, W5JN who also provides some VOM
(Voice Over Morse ;-) comments. --
Contributed
by Peter Rosenberg, AC7SB
http://www.ootc.us/W5JN%20QCWA%20Ch41.mp3
EMCOMMWEST®'08 - MAY 2-4, 2006
"The Biggest Little Ham Convention in the World"
http://www.emcommwest.org/
-
∙ ∙ ∙ -
EMCOMM EAST - MARK YOUR CALENDARS!
•
Location:
St. John Fisher College, Rochester, New York
•
Date: Saturday, September 20, 2008.
EmComm East is an amateur radio emergency communications
conference, where amateur radio operators involved in EmComm can attend training
sessions on technical topics, purchase equipment and supplies from vendors,
learn from served agencies, obtain VE testing for license upgrades, and interact
with other EmComm operators from all over the area. The EmComm East
Conference Committee encourages amateur radio operators, served agencies, and
others involved in emergency communication to submit presentation proposals for
general interest sessions. $30 pre-registration required,
continental breakfast and lunch included. For more information, please
visit our website at:
www.emcommeast.org
(Via Jeff Wigal, WY7Q, Emergency Coordinator, Monroe County, NY ARES®
-
∙ ∙ ∙ -
EMCOMM NET LIST AVAILABLE
EM
maintains a list of active
NATIONAL and
REGIONAL VHF and HF EMCOMM NETS at:
www.wrrl.org/n_e_t_s_.asp
-
∙ ∙ ∙ -
EMCOMM "LICENSE PLATES"
For your vehicle, shack or mobile emcomm unit.
View at:
http://www.emcomm.org:80/products/
∙
-
∙
-
∙
THE EM ADVISOR
The staff of
EMCOMM
MONTHLY is happy to answer your questions to the best of our
ability. Some are
"FAQs" (Frequently Asked Questions) and others are of a specific nature.
Each month, we will answer questions that may have value to other emcomm radio
operators. Technical questions are forwarded to our Technical Advisor, Ed
Ewell, K7DXV. Questions about our ARCT program or NIMS/ICS are forwarded to
Before submitting a question, we ask our readers to check the FAQ page
first...your question may have been asked before. Also, please consider
checking our site search page at:
http://www.emcomm.org/search.htm to see
if your question may have been previously addressed in
EMCOMM
MONTHLY. Thank you.
-
∙ ∙ ∙ -
Q:
There has been significant discussion lately among our members regarding quick
and inexpensive antennas for use in local HF communications. But some of those
who are experienced enough to have the "know-how" usually indicate the antennas
don't work, or are more bother to build than they are worth. Your article
seems to strongly dispute that opinion and as a new jam I would like to bring
some documentation to the discussion. I would like to make copies of the
NVIS antenna project for members of our Lincoln Trail Amateur Radio Club in
Hardin County Kentucky.
NVIS - (Near Vertical Incidence Skywave) at:
http://www.emcomm.org/antenna/default.asp and
http://www.emcomm.org/projects/default.asp
Thank you. - David VanderMolen, AI4VF, Elizabethtown, KY
A: Permission
is hereby granted per your request below, provided that it is not for profit.
Please mention this credit: "Reproduced courtesy of
EMCOMM
MONTHLY and the
WRRL."
Thank you for asking. While NVIS is a
technique that usually performs well, some days the ionosphere just doesn't seem
to want to cooperate. Waiting a few hours will usually make a difference
and except for EMERGENCY traffic, waiting a few hours to pass a message is
certainly acceptable. Also keep in mind that signals via VHF SIMPLEX (e.g.
- six and two meters) can easily be received 100 miles or more, providing that
the stations have good antennas and sufficient power. I do not recommend
putting all your "eggs" in the "repeater basket." Please let us know how
well your tests and/or experiments work. -
EM
-
∙ ∙ ∙ -
Q:
I was looking at the ARCT Program requirements and saw reference to ICS/NIMS as
a requirement. Are ICS 100 & 200 required and are 300 and 400 also? Other than
NIMS 700, what others are needed? Agencies in Utah require ICS 100 & 200
and NIMS 700 to enter an EOC during an exercise or real event. Do the
agencies in California also require them or is there additional ones? - Jim
Samuels, K6TUG, WRRL 168, Salt Lake City, UT
A:
TYPE I ARCTs deployed by the WRRL must meet all applicable current FEMA and NIMS
requirements. This includes any and all additional requirements imposed by
state or local agencies or private organizations (e.g. - Red Cross, etc.)
This will no doubt vary from place-to-place, time-to-time, and probably will
vary between incidents, depending upon the IC or coordinating agency.
WRRL leaves it up to the individual ARCT leader(s), to know what all is required
for emcomm operators for a specific agency and or operation, and ensure that any
additional (non-WRRL) requirements are complied with. Unfortunately, most
of these additional requirements have little to do with an ARCT's or an
individual operator's ability to provide emergency communications.
Re. " Do the agencies in California also require them or are there
additional ones?"
The short answer is, We don't know and doubt that anyone knows. Overall
the whole process is still in the formative stages and in a state of flux.
It depends upon who, where, and when you ask. For the time being, it must be
handled on a case-by-case basis. In events where an emcomm operator may
have to enter an EOC or other restricted area, he/she will have to meet whatever
requirements may be in effect.
If emcomm operators are not authorized to enter an EOC, the emcomm field
station should be located near the EOC (or other command area.) Message
traffic can then be handed to a courier (an authorized person) for delivery to
an addressee inside, and outbound traffic can always be hand-carried out to the
emcomm station for dispatch.
The Red Cross (and other private organizations) also may have special
requirements as to who may, or who may not, enter their facilities. The
ARCT leader should know who on any given ARCT is authorized, and for what (e.g.
- pre-registered ARC volunteers). This of course reduces the flexibility
of the team and can creates additional work for emcomm leader(s).
Advance planning and ongoing liaison with other agencies will alleviate many of
these problems.
∙
-
∙
-
∙
ICS PERSPECTIVES
By Jerry Boyd, N7WR, Associate Editor and ICS Advisor
I continue to receive questions and comments about a subject that has been
covered in EM in the past. While we continue to make the argument that
radio message traffic should be passed using the Radiogram format, a number of
emcomm operators insist that, for a variety of reasons, ICS form 213 (General
Message Form) ought to be used. Some emcomm operators indicate that their
“served agencies” insist that ICS 213 be used for all messages.
Let’s re-visit this subject and see, worst case, if some compromise might be
achieved. The universal Radiogram is designed for message traffic intended
to be passed by radio. It has fields in which to record important
information such as: Date, time, precedence, handling instructions, word
count, address and addressee, etc. What is the purpose for recording such
information? It is to document for purposes of accuracy and (potentially)
liability what exactly was sent, to whom, by whom, etc.
ICS 213, on the other hand was designed and intended to serve as an “interoffice
memo form”, i.e. it is defined as a general message form. It fails to
capture much of the important documentation called for in the Radiogram.
Thus, if traffic passed using ICS 213 is ever called into question or challenged
(or a lawsuit develops in which reference to the “message” becomes an important
issue) much important documentation may be found to be missing.
Some have told me that they agree the Radiogram is better suited to passing
traffic by radio than the ICS 213 format is….but they are “required” to use
ICS-213. Here’s the compromise. Use the ICS 213 format but add
(simple enough to do) the additional information called for in a Radiogram on a
single line just below the subject line on the ICS 213. In fact, I know of
a few good traffic handlers who have had a self-inking stamp made so they can
add that line expeditiously to the ICS 213 form. I also know of some
entities that have put the ICS 213 from on a computer and have added the
Radiogram information so that when they print the document all required fields
are already present.
Those who have modified ICS 213 to accommodate critical information contained in
the Radiogram have not reported any objections or resistance on the part of
their “served agencies”. - From NE Oregon 73 de N7WR
WRRL NEWS and NETS
∙ REGIONAL
EMCOMM NETS
(ALL SERIOUS EMCOMM STATIONS WELCOME):
Pacific (and Mountain) Time Zones: PTZNN (aka Jefferson Noon Net/JNN)
daily at 1200 PTZ on 7214± kHz (3911± kHz alternate)
Central (and Eastern) Time Zones: CTZNN Mondays, Wednesdays and Fridays at
1200 CTZ
on
7214± kHz
∙ WRRL NET
on MONDAYS on 14.280 MHz USB (Alternate: 14.270 or somewhere "in between.")
2000Z (SUMMER) 2100Z (WINTER)
∙ WRRL
STATION MAP UPDATE
Map showing the location of WRRL stations can be viewed at: http://www.wrrl.org/map/
∙
-
∙
-
∙
TRAFFIC
HANDLING
“For want of
a letter, a word was lost.
For want of a word, a message was lost.
For want of a message, a life was lost.”
--------------------------------------------------------------------------------------------------------
"Record Message Traffic, by skilled operators, and by RADIO (only)!"
It's about Dependability, Accuracy and Accountability!
NET and TRAFFIC HANDLING
(An EM advanced studies training module)
During a recent on-the-air RADIOGRAM practice session, a participant asked what
to do if you receive a message (either for relay or delivery) that contains what
you believe to be erroneous information. Should you forward or deliver the
message exactly as you received it? Or, should you send a "service the
message" back to the originating station and/or the originator for
clarification?
This question comes up from time-to-time. It is one of those questions
that many wouldn't touch with the proverbial "ten-foot-pole!" Regular EM
reader's know that we tend to venture where others may fear to tread...and
so...with great trepidation, we'll try to address this very real issue.
First and foremost, we will re-state one of this commandment:
Traffic handlers must NEVER, EVER, make any change(s) to a message and forward
it. (This includes the preamble, address, text and signature.)
There are, however, exceptions to every "rule," and if you receive a
message that you believe contains a serious and/or critical error, you then must
make a judgment call as to whether to:
1 - Forward the message (exactly as you received it), or return the message to
the station of origin as a service message* for confirmation and/or correction.
For routine (R) inconsequential messages, the best rule
of thumb is to simply forward it.
2 - However, for welfare (W), priority (P), and EMERGENCY traffic, you are
convinced that an inaccurate message could affect the safety of human life or
property,
you may decide to (for safety's sake) "service it back"
(using same precedence as the original message) to make sure that it is correct
(or not). Depending upon
the situation, it might be better to take the time to
clarify the message than to nforward and/or deliver a "mixed-up" or unclear
message that could have disastrous
consequences. "ACCURACY TRUMPS
SPEED!"
Consider this hypothetical situation:
Suppose you receive a message for relay that involves a distress or some other
request for assistance. (A ship dead in the water, lost or stranded
vehicle in the desert, etc.) The TEXT includes a latitude and longitude.
The message (as received) places the POSN (position) at a south latitude.
However, you have recent knowledge that the vessel (or stranded party) is at a
north latitude.
Or, a message may include a location on a USFS road and the relay operator (you)
knows the road number stated is incorrect or non-existent. And you believe
that if either message is delivered with the incorrect latitude, or other
location coordinates, a rescue party will be directed, to the wrong location,
possibly hundreds of miles off course.
Of course, you could hold the traffic and originate a service message back to
the originator to confirm north or south latitude. But this would only
delay the traffic. Imagine a court trial where an operator has to defend
delaying a message or relaying what he/she knew was incorrect.
We put the question to Ed "FB" Trump, AL7N, WRRL 6 who is our resident authority
on traffic handling. This is what he says:
"First of all, the CONTENT of any message is the province of only two
parties: The originator, and the recipient.
"The ONLY place any question should EVER be asked about the CONTENT of a message
is when it is presented by the originator for transmission at the originating
station, and then only to the extent required to make sure the message text is
EXACTLY as the originator wishes it to read.
"This is especially crucial in the case of EMERGENCY, PRIORITY or WELFARE
message traffic. This important "joint" responsibility of BOTH the
originator and the station of origin to make sure the message text is accurate
and as it should be sent is too often overlooked or neglected by originating
stations and/or their counterpersons.
"Outside of something obviously illegal, which should never be allowed to get to
the radio operator for transmission in the first place, the message should then
be transmitted as originated.
"Any station/operator subsequently handling the message is obliged to transmit
it or relay it EXACTLY as written by the originator. It may not "make
sense". It doesn't have to.
"Same goes for a message that might appear to be "in error". Relaying or
delivering operators MUST NOT judge messages on their content. The only
safe course is to relay it expeditiously and accurately...period.
"However, things can and will get screwed up and it IS possible that something
in the message text obviously in error is discovered by some other station
"closer to" the destination. That type of situation would best be handled,
in my opinion, by attaching an "op note" to the message AFTER the signature to
"flag" the possible error.
EXAMPLES:
OP NOTE LATITUDE POSSIBLY SHOULD BE NORTH INSTEAD OF SOUTH
or,
OP NOTE FS ROAD 279 DOES NOT EXIST POSSIBLE SHUD BE FS 2779
"Therefore, I would relay/deliver the message "as received" as long as I was
sure I had made no error in receiving it from the distant station, and append
the "op note" to address the perceived error after the message signature.
"It is indeed a judgment call, and one of the situations when the "rule" must be
"bent" a little.
"The message originator and the first station to put any message on a circuit
both have a responsibility to prevent this sort of thing at the outset. If due
diligence
is given at origination, the possibility that something would look improper or
incorrect down the line is minimized."
*See June 2007 EM at:
www.emcomm.org/em/2007/june2007.htm
REMEMBER: "ACCURACY TRUMPS SPEED!"
TO
HELP KEEP YOU FROM SOUNDING LIKE AN UNTRAINED OPERATOR GO TO:
• OPERATING PROCEDURES: www.wrrl.org/operating/
============================================
TAKE THE TRAFFIC HANDLER'S CHALLENGE AT:
http://www.emcomm.org/thc/
TRAFFIC HANDLER'S SUPPLIES:
http://www.emcomm.org:80/products/
∙
-
∙
-
∙
THE “TRAFFIC HANDLER’S MANTRA”
(Recite often to help remember the eight parts in preamble):
“No
• Prepared • Ham • Should • Copy • Priority • Traffic • Delayed”
NUMBER • PRECEDENCE
•
HX
(Handling Instructions) •
STATION OF
ORIGIN •
CHECK
•
PLACE OF
ORIGIN •
TIME
•
DATE
To help you to memorize the eight parts of the preamble,
RECITE
the
"Traffic Handlers Mantra" often:
“No
• Prepared • Ham • Should • Copy • Priority • Traffic • Delayed”
ASSESS your current traffic handling skill. Take the
"TRAFFIC HANDLER’S CHALLENGE" at:
www.emcomm.org (main page)
∙
-
∙
-
∙
NATIONAL EMCOMM TRAFFIC SERVICE (N.E.T.S.)
The NATIONAL EMCOMM TRAFFIC SERVICE
uses designated watch and calling frequencies. Public service
amateur radio operators everywhere are invited to monitor these frequencies
whenever possible. But when disasters or other incidents occur, emcomm
operators are asked to warm up their radios and "light up" the NATIONAL EMCOMM
TRAFFIC SERVICE..."24/7". Active operators know which bands are most
likely to be "open" depending upon the time of day, season, etc.
During disasters and for other emergencies, the frequencies are "open nets".
When traffic becomes heavy, they will become "command and control"
frequencies with a net control station "triaging traffic" and directing stations
with traffic to another (traffic) frequency. (At least 5 kHz away.)
Proper net procedures are essential.
NETS
does not maintain regular schedules and does not handle routine "make work"
messages such as birthday greetings, "your license is about to expire", "book
messages", etc. NETS
is intended to
supplement
and
fortify other networks by providing a vehicle for emcomm
operators to originate, relay and deliver legal radio message traffic (i.e. -
"first class mail") of any precedence, at any time, from and to anyone and
anywhere--especially during disasters or other crises. NETS
stations will cooperate and use other networks that are known to be capable of
accurately and efficiently handling RADIOGRAMS.
NATIONAL EMCOMM TRAFFIC SERVICE (NETS) WATCH • MONITOR • CALLING • TRAFFIC
FREQUENCIES
All
listed frequencies (except 60 meters) are nominal. Actual nets may be up or
down as much as 20 kHz
SSB:
• 1982 kHz
• 3911 kHz RADIO RESCUE (SSB and CW)
• 5332 kHz "Up" to other 60M channels as necessary. 50W maximum ERP.
(Activated during actual incidents.)
• 7204 kHz
• 14280 kHz
•
CW:
• 1911 kHz
• 3540 kHz
• 3911 kHz RADIO RESCUE (SSB and CW)
• 7111 kHz
• 10119 kHz
• 14050 kHz
•
•
GULF STATES (LA, MS, TX, AL)
- 7111
kHz 1100Z-2300Z / 3570 kHz 2300Z-1100Z
During EMERGENCIES: 7111 kHz daytime, 3570 kHz nighttime.
(Times approximate depending on band conditions and changes in sunrise/sunset.)
VHF/UHF FM
• LOCAL EMCOMM SIMPLEX - 146.55 MHz
• RED CROSS EMCOMM SIMPLEX - 147.42 MHz
• NATIONAL CALLING SIMPLEX - 146.52 MHz
Frequencies listed may be on or near other established net frequencies.
As a matter of operating courtesy, always move up or down a few kHz to avoid QRM when a frequency is in use.
∙
-
∙
-
∙
"SHOW US YOUR SHACK"
•
"SHOW US YOUR SHACK"
is at: http://www.emcomm.org/em/shacks/
• Send a picture of you
AND
your shack (all in one frame and in JPG or JPEG format) to:
k6soj@wrrl.org
∙
-
∙
-
∙
FEATURE SECTION
No new "FEATURE"
this month.
Instead, please focus on
NET and
TRAFFIC HANDLING above.
Or review this item from the October 2007 issue of EM. (We still hear
a lot of misuse of these terms on the air.)
ARE YOU FIXED, MOBILE, or PORTABLE?
An EM basic studies
training module)
Although it is no longer an FCC requirement to state if your are operating
"mobile" or "portable" when identifying, these terms are still often used. But
when used, they are commonly incorrectly used after a call sign. To help
alleviate some of the confusion (and misuse) we offer this:
The terms
mobile
and
portable
have nothing to do with the type of radio being used. If you are at your
home location (the location given on your FCC license), you are not "mobile"
even if you're in your car in the driveway or parked on the street in front of
your house. Also, you are not "portable" if you are using a Handie-Talkie in
your back yard.
Here is how the terms have been traditionally defined*:
Fixed
operation: Radio communications conducted from a specific
geographical land location shown on the station license. Normally, your
home "shack".
Portable operation: Radio communications conducted from a
specific geographical location other than that shown on the station license.
For example,
a vacation home, or a friend's house. A portable station is a solitary
hiker using an HT camping at Beaver Lake for a few days. Or, it could be a
multi-band, multi-mode, multi-operator Field Day Station, with multiple tents,
numerous antennas and several transmitters running up to full legal power with a
12 kW diesel generator running 24 hours a day!
Mobile
operation: Radio communications conducted while in motion
or during halts at unspecified locations. (Note: It's important to make
the distinction between portable and mobile operation.
Mobile
refers to talking on your 2-meter rig while driving your pick-up truck, while
jogging or while backpacking. Portable
means operation for an extended period of time at a specific, definable
location, such as your retreat cabin."
Maritime mobile and aeronautical mobile are occasionally heard. You
may also hear pedestrian mobile,
wheel chair mobile, bicycle mobile, equestrian mobile, railroad mobile, or
other such definitive terms. These terms attract attention, add to the interest
and the
magic of radio, and are fun to contact.
Sadly, amateur radio (like many other things in today's world) has embraced
a “laissez faire” (anything goes) approach to what was once a proud discipline.
I, for one, still prefer "the old ways" and still try to follow the
traditional good operating procedures. -- Editor
*Source: The FCC Rule Book. A Guide to the FCC Regulations. ARRL
1989
-
∙ ∙ ∙ -
======================================================
EMCOMM SPECIALTY PRODUCTS
Features D. W. Thorne, K6SOJ, as the instructor. The session was taped
live at the U.S.F.S. facility at
Send check payable to:
EMCOMM,
VIEW MORE EMCOMM SPECIALTY PRODUCTS AT:
http://www.emcomm.org:80/products/
======================================================
NEW SUBSCRIBERS
• John W. Phillip, KE7OMP, Mosier, OR - RACES, ARES®
• Jay Brackin, W3NUR, Townsend, DE - ARES®
• Ronald Hayes, NØVKJ, Joplin, MO - ARES®, Missouri Traffic Net, MoKan Emergency
Preparedness
• Len Fulbright, K5WFW, Santee, CA -ARES®, RED CROSS
• Bob Burdick, NB8N, Ellijay, GA - ARES®, MARS
• Ken Cohen, KI6HRH, El Cajon, CA - ARES®
• Don Doud, K7DRD, Redmond, WA - ARES®
• Jay Bookwalter, KC8GNL, Mansfield, OH - ARES® DEC Ohio District six
• Dean Jacobsen, W6DBJ, Vista, California - ARES®
• Walt Hasselback, AB3FW, Ephrata, PA - RACES
• Robert Andrews, KØRDA, Rochester, MN - ARES®
• Cory Golob, N1URA, Sabattus, ME - ARES®, EC
• Brent Cameron, N9NJS, Mascoutah, IL
• Nick Proy, AB3HJ, Baltimore, MD
• Kirk Illian, KG6HPF, San Marino, CA - ARES®, REACT
• Mark Cantrell, KD4IMA, Asheville, NC - ARES®
• Jeff Moore, KE7ACY, Bend, OR - ARES®
• Devlin Kirchman, KC5LTU, Caddo Mills, TX
RECENT CONTRIBUTOR$ - Thank you for your support!
(The individuals listed below have recently made monetary contributions to help EMCOMM MONTHLY
and
EMCOMM.ORG survive.)
• Will du
Later
• Les Caire
• Ima Lid
EMCOMM MONTHLY and EMCOMM.ORG are private
(non-government, non-commercial) endeavors and are funded by
donations from emcomm operators who are concerned about preserving the ability
of amateur radio operators to be prepared to provide skilled, accurate and
efficient emergency communications during times of disaster or other events
where normal channels of communication may be interrupted or overloaded.
If you have benefited from our efforts, and would like to support this work in a
tangible way, you may do so by sending a check or money order payable to:
EMCOMM.
Mail to: EMCOMM,
SORRY: We have no PayPal®, credit card, or other methods to accept the
electronic transfer of funds. "We do it the old fashioned way!"
SOS -
SUPPORT OUR SUPPORTERS
When contacting these fine vendors... tell them
EMCOMM MONTHLY
sent you!
Auxiliary Emergency Radio Organization (AERO)
Contact:
www.wcf.com/aero/fun/
(Headsets, books, other items.)
Proceeds go to support AERO.
EmComm Products LLC
Robin (N7GSU) and Kathy (KD7OTY) Faulkner
http://www.EmComm-Products.com/
(541) 763-3890
PO Box 383
703 Sixth Street
Fossil, OR 97830-0383
(Manufacturer of the RADS 9-11® Rapid Antenna Deployment System ®)
EMCOMM MONTHLY is
free of paid commercial advertising and "pop-ups". However, we list
commercial vendors who offer products specifically of interest or value to the
emcomm community and who make periodic contributions. If you would like
your company to be listed in
SOS -
SUPPORT OUR SUPPORTERS send a brief mention of your company and
its products (see examples above) and a donation to: EMCOMM,
REFERENCE and RESOURCE SECTION
• ICS-ARCT GUIDE:
www.emcomm.org/ARCT/
• WRRL ARCT Page
www.wrrl.org/arct_program/
• TRAFFIC HANDLER’S CHALLENGE:
http://www.emcomm.org/thc/
• OPERATING PROCEDURES: www.wrrl.org/operating/
• PHONETICS:
www.wrrl.org/operating/itu_phonetics.htm
• RADIOTELEPHONE PROCEDURES:
www.wrrl.org/operating/icao_radiotelephony.htm
• GEAR AND EQUIPMENT LIST:
www.emcomm.org (Click on GEAR CHECK LIST)
• FEMA TRAINING COURSES:
http://training.fema.gov/emiweb/IS/crslist.asp
• FEMA TRAINING COURSE IS-700 (NIMS): http://training.fema.gov/emiweb/IS/is700.asp
• ARRL FSD-218. The famous “pink card” that contains (almost) “everything
you ever needed to know about RADIOGRAMS”.
An electronic version of FSD-218 is at:
http://www.arrl.org/FandES/field/forms/#fsd-218
• NTS page by W7ARC:
http://www.w7arc.com/nts/
• NATIONAL TRAFFIC SYSTEM (NTS) Methods and Practices Guidelines:
http://www.arrl.org/FandES/field/nts-mpg/
• PACIFIC AREA TRAFFIC NETS:
http://home.earthlink.net/~k7bfl/nwnets.html
• MARITIME MOBILE SERVICE NETWORK:
http://mmsn.org/
• BEAUFORT WINDSPEED SCALE: http://www.zetnet.co.uk/sigs/weather/Met_Codes/beaufort.htm
• NOAA/NWS WINDCHILL CHART:
http://www.weather.gov/os/windchill/index.shtml
• STANDARD TIME ZONE SCALE: http://www.travel.com.hk/region/timezone.htm
• HOSPITAL DISASTER SUPPORT COMMUNICATIONS SYSTEM (HDSCS):
http://members.aol.com/emcom4hosp
• U. S. AIR FORCE Search and Rescue SURVIVAL MANUAL MIRROR SIGNALING (AFM 64-5
Aug. 1969)
http://www.emcomm.org/drawings/Mirror_Signaling_mid.jpg
SUBSCRIBE TO
EMCOMM
MONTHLY
www.emcomm.org/subscription.htm -- IMPORTANT:
Many internet service providers (ISPs) are installing "SPAM filters" in their
system that may block
EMCOMM
MONTHLY both inbound or outbound (if you try to forward it to
someone). To ensure that you receive
EM
and
SPECIAL BULLETINS add: @cot.net, @wrrl.org, and @emcomm.org to
your "Whitelist" with your ISP. Contact your ISP if you have any questions.
ABOUT ADDRESS CHANGES:
Every month, a varying number of
EM
are returned as "undeliverable addressee unknown" or "rejected due to containing
possible objectionable material". Our very limited, all-volunteer staff does
not have the time, energy, or desire to track down everyone who changes their
email address and forgets to notify us. Also, if a subscriber installs a "spam
filter" or a "parental control device" and neglects to tell the filter that it's
"OK to let EM
pass through", we do not have time or patience to jump through secret hoops, or
solve puzzles, to allow us to send email to you.
If you change your email address,
be sure to notify us at: www.emcomm.org/subscription.htm ...
that is, if you want to continue to receive
EM.
EMCOMM MONTHLY
is originated in
10, 12, 14,
and 18 point Arial font and transmitted in
HTML
format. Occasionally, selected portions are set up in the
Lucida
Console font. HOWEVER...we have received a few reports that on
some computer screens...EM
appears unformatted in
Plain Text
or
FUBAR. ("Fouled Up Beyond All Recognition.") If this
happens to you, you can always view
EM,
as it is intended to appear, at:
www.emcomm.org/em
Upon request
EMCOMM MONTHLY will
be transmitted in
plain text
format to visually impaired subscribers who use an email-to-audio conversion
program, and/or other subscribers whose computers do not process email in HTML
format.
EMCOMM MONTHLY archives:
www.emcomm.org/em
SEARCH FEATURE AT EMCOMM.ORG
www.emcomm.org
The opinions expressed by individual contributors do not necessarily reflect the
EM
philosophy, the editorial position of
EM,
or its staff.
ARES®
and
Amateur Radio Emergency Service® are registered service marks of
the
American Radio Relay League Inc., and
are used with permission.
For
permission to reproduce material in EMCOMM MONTHLY
contact: D. W. Thorne at:
k6soj@wrrl.org or write:
EMCOMM MONTHLY,
EM STAFF:
D. W. Thorne, K6SOJ - Editor and Publisher -
k6soj@wrrl.org
Bill Frazier, W7ARC - Associate Editor and Webmaster -
w7arc@wrrl.org
Ed Ewell, K7DXV - Technical Advisor -
k7dxv@wrrl.org
Ed Trump, AL7N - Traffic Editor and Alaska Correspondent -
al7n@wrrl.org
∙
-
∙
-
∙
IN THE JUNE
ISSUE OF EMCOMM MONTHLY:
• "GET READY FOR FIRE AND
HURRICANE
SEASON"
• NEWS...
FEATURES... FEEDBACK.... QSH... and MORE!
EMCOMM MONTHLY -- The Official Journal of the World Radio Relay League - WRRL®
Copyright (c) 2008 - All rights reserved.
-
∙
-
∙ ∙
-
∙ ∙
