[MilCom] Discussion Points -- Logging Codes, Summary Logs Versus Real Time, Multiple List Postings Uniqueness?

[Joe Cobb]

That would be Ok but for a lot of people i don't think
they can handle the "codes" or shorthand form. And my
point starts with the city (ICAO) codes.  Some folks
were identifying origins and destinations with the
ICAO code ie. KBNA (Nashville, Tn) and there were some
on here who kept crying to have the city spelled out
(in maybe addition to the code), even with the most
known airports.  Thats why on my posts i try to log
the most elementary way so people can understand it. 
Thats why everything is spelled out as it happens
(kind of like a summary of what went on at the time)
and the freqs are listed in the order they were heard
followed by a > to tell in which direction the
sequence was.  

I also figure you would have to put a little legend at
the bottom or top cause different folks hear different
things.  And that to me would take more time.  I work
from 1400 to 2200 (CST) and when i get home i type in
my logs as quickly as possible so i can get to other
things before bed so i choose to do a summary of what
i heard at once.  It's not feasible to post every
single time i hear an event.  I don't have that kind
of time.  I will maybe post something as it happens if
it's something out of the ordinary (B-2A's passing
over or aircraft actually working Campbell's ranges,
which hardly ever happens) for this area.  I need most
of my time to concentrate on whats happening on the
scanner rather than trying to rush and post something
in "real time".  I might miss something or screw up
what was said all together.  Well, thats my two cents
worth.

Joe
Nashville, Tn.

--- Ken <rfinder1 at verizon.net> wrote:

> Perhaps this a bit controversially but this message
> covers the following 
> potential discussion points
> 1.  Introduction of a Logging Coding Scheme:
> 2.  Recommend information in Loggings.
> 3.  Summary Posting daily versus many messages
> 4.  "Uniqueness of Lists" versus multiple postings
> 
> 1.  Maybe it's time to consider introduce a log
> coding scheme.
> An example (not all inclusive of codes):
> 
> AR = Aerial Refueling
> BL = Block Assignment
> CD = Clearance Delivery
> CO = Climb out
> DE = Descending
> ER = Engine Run (on the ground)
> FL = Flight Level
> GE = Ground Emergency
> IFR = Instrument Flight Rules
> IFE = Inflight Emergency
> LA = Land
> LPW = Local Pattern Work
> PRD = Parachute Drops  Add B for bundles/cargo, P
> for personnel
> R# = Runway number
> RC= Radio Check
> TA = Taxi
> TG = Touch/goes
> TO = Take Off
> UNK = Unknown
> (others could be added, suggestions?).
> 
> 2.  Frequencies could be in order of use followed by
> "/" between each
> What also would be great if ever once and awhile &
> legend would be published 
> to show the frequency & it's specific user in
> numeric order at the bottom of 
> the logs.   Furthermore when an aircraft callsign is
> used in parenthesis 
> indicate the type of aircraft.  Additionally if the
> unit is know that could 
> be added.  I think that Sandy's logs (from Colorado)
> are a very good example 
> of concise summary of daily loggings.
> 
> 3 & 4.  Don't want to scare away any logging posters
> BUT I guess the other 
> question/discussion point for this group is should
> the nitty gritty of 
> TYPICAL LOCAL ACTIVITY be reported in individual
> messages as in occurs 
> throughout the day to the list OR should a summary
> at the end of the day be 
> best?   Personally, I would think that the various
> regional lists would be 
> more applicable to getting individual messages as it
> happens than the milcom 
> nationwide list since the hobbyists in that region
> have a DIRECT interest in 
> what is happening & may be able to monitor the
> action.  When MILCOM was 
> formed many years ago at Grove Enterprises the other
> nationwide free mail 
> list servers weren't really in existence BUT TIMES
> HAVE CHANGED!!!!  The 
> multiple postings of loggings to multiple groups (of
> which many if not most 
> of us are members) just results in spending time
> analyzing the posts & than 
> throwing away one of the post.  Shouldn't each list
> have some "uniqueness" 
> to it?    That's why I've decided awhile back to
> just post a monthly logging 
> summary to milcom & post the details of daily
> activity to the northeast 
> regional list.
> 
> I am not trying to dictate how this list should
> operate BUT IMHO (as a 
> member since the founding of this list) it's worth
> discussing in a hopefully 
> civilized manner.
> 
> Comments, public or private as you prefer!
> 
> Ken
> 
> 
> ----- Original Message ----- 
> From: "Greg Brazil" <baycomm at earthlink.net>
> To: "jay dehm" <dehmmy.qth at gmail.com>; "mil"
> <milcom at mailman.qth.net>
> Sent: Friday, October 27, 2006 11:40 PM
> Subject: Re: [MilCom] Logs continued
> 
> 
> > Ya think you could post this in English, please?
> > Greg (SF Bay Area)
> > jay dehm wrote:
> >
> >> 1349z/ JOSA 829
> >> .. 120.65 < 133.275 < 118.025
> 
> 
>
______________________________________________________________
> MilCom mailing list
> Home: http://mailman.qth.net/mailman/listinfo/milcom
> Help: http://mailman.qth.net/faq.htm
> Post: mailto:MilCom at mailman.qth.net
> 



 
____________________________________________________________________________________
Low, Low, Low Rates! Check out Yahoo! Messenger's cheap PC-to-Phone call rates 
(http://voice.yahoo.com)