<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Is there someone in the area that can give him a call and help
him set it up correctly? <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
aprssig-bounces@tapr.org [mailto:aprssig-bounces@tapr.org] <b>On Behalf Of </b>Greg
D.<br>
<b>Sent:</b> Saturday, March 14, 2009 5:43 PM<br>
<b>To:</b> aprssig@tapr.org<br>
<b>Subject:</b> Re: [aprssig] emergency beacon called wide1-1 today<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Last position (about 30 min ago) shows the
plane in front of the hangar at the Anoka County airport. Presumably
he'll be home soon. Google says it's about a 20 minute commute.<br>
<br>
Greg KO6TH<br>
<br>
<br>
> From: ve7gdh@rac.ca<br>
> To: aprssig@tapr.org<br>
> Date: Sat, 14 Mar 2009 13:17:29 -0700<br>
> Subject: Re: [aprssig] emergency beacon called wide1-1 today<br>
> <br>
> Chuck W3YNI wrote...<br>
> <br>
> Subject: Re: [aprssig] emergency beacon called wide1-1 today<br>
> <br>
> > Actually spoke to some folks from CAP. Gave them what I believed<br>
> > was the tailnumber at the time (now confirmed) along with last known<br>
> > coordinates from the beacon.<br>
> ><br>
> > Guy I spoke to is a ham and knew what APRS is - he sent it up the<br>
> > chain.<br>
> <br>
> and posted by Rusty (K1GGS?)...<br>
> <br>
> > WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10:`tR7+{A'/"S)}KD0CVN-1
RV-9A<br>
> <br>
> The odd thing is that the "callsign" is WIDE1-1 and N789PH
(presumably<br>
> the tail number) is the destination instead of the "callsign".
The<br>
> owners callsign appears to be KD0CVN as indicated in the status text.<br>
> Don't know why he would include an SSID there! Also according to the<br>
> status text, it's an RV-9A.<br>
> <br>
> I know the above doesn't show a path of WIDE1-1, but looking at the<br>
> tracker that IS using a "callsign" of N789PH...<br>
> <br>
> http://aprs.fi/?c=raw&call=N789PH&limit=1000<br>
> <br>
> it is using a path of WIDE1-1,WIDE2-1. Surely if it really is a plane<br>
> wouldn't use a path of WIDE1-1,WIDE2-1 - hi!<br>
> <br>
> Also, looking at http://aprs.fi/?c=raw&call=WIDE1-1&limit=50<br>
> it is possible that there is more than one station with a misconfigured<br>
> "callsign" of WIDE1-1.<br>
> <br>
> 2009-03-14 14:36:43 UTC:<br>
> WIDE1-1>N789PH,WIDE2-1,qAR,W9DRR-10<br>
> :`tR7+{A'/"S)}KD0CVN-1 RV-9A [Invalid characters in mic-e packet]<br>
> <br>
> There's that "KD0CVN-1 RV-9A" again... or possibly it's one and
the same<br>
> beacon. What a tangled web it is!<br>
> <br>
> The callsign of WIDE1-1 must have been programmed in accidentally. While <br>
> it is possible that a mangled MIC-E packet may be involved for the <br>
> "emergency" beacon, perhaps it would be a good recommendation
for planes <br>
> to not use MIC-E to lessen the chance of a mangled MIC-E packet making <br>
> it look like an emergency beacon. Just a thought.<br>
> <br>
> 73 es cul - Keith VE7GDH<br>
> --<br>
> "I may be lost, but I know exactly where I am!"<br>
> <br>
> <br>
> _______________________________________________<br>
> aprssig mailing list<br>
> aprssig@tapr.org<br>
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Windows
Live™ Groups: Create an online spot for your favorite groups to meet. <a
href="http://windowslive.com/online/groups?ocid=TXT_TAGLM_WL_groups_032009"
target="_new">Check it out.</a><o:p></o:p></span></p>
</div>
</body>
</html>