[aprssig] N666BK-1 no legal call what so ever...
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toSun Apr 15 20:41:42 UTC 2012
- Previous message: [aprssig] N666BK-1 no legal call what so ever...
- Next message: [aprssig] N666BK-1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It shows as >APBL10 which is "APBLxx BigRedBee BeeLine" according to http://www.aprs.org/aprs11/tocalls.txt I don't know if this device is capable of it, but remember that you can meet the ID requirement by sending it out in CW. So unless you were monitoring the frequency by ear, you cannot be sure that the station truly wasn't meeting the legal ID requirements. That said, Google is still your friend: http://bit.ly/HKrNP3 http://www.airport-data.com/aircraft/N666BK.html http://flightaware.com/live/flight/N666BK http://s447.photobucket.com/albums/qq197/N666BK/?start=all Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 4/15/2012 10:30 AM, Kriss A Kliegle wrote: > Happend to be on HF and watching my APRSDOS screen... couldn't help to > notice N666BK-1 bombing around NH without any legal callsign in it's > transmissions. > Yet another appliance operator occupying bandwidth. > Anyone know this one? > 73 de Kriss KA1GJU-X > > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tapr.org/pipermail/aprssig/attachments/20120415/2ea5e979/attachment.htm>
- Previous message: [aprssig] N666BK-1 no legal call what so ever...
- Next message: [aprssig] N666BK-1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
