Hi Chris,
Thanks for the reply. As you identified (quote)"I understand that one might want to know the squawk if listening to airband to help identify an aircraft when the squawk is transmitted to the aircraft as part of the ATC clearance or start up instructions".
This is the primary use to me in knowing the squawk. Given finite resources in channel allocations on the receiver it is helpful in determining which frequencies might be included and which might not, or which group of frequencies might yield comms from a certain flight or area.
It is probably possible, but quite impractical to program every known frequency into the receiver.
Having the squawk available in the reporter means I can also build a pattern as an aid to programming frequencies for greater likelihood of traffic rather than a hunt and peck frequency range search. And it also means I don't have to be glued to the screen to see the squawk ( I love the hobby but I'm not married to it :))
As occured this morning,
The reporter returned this result:
AE0945 S289 01-0040 B73B USA - Air Force 2011/12/21 02:23:02
Not much to go on.
As it happened, I was up and at the computer at the time and using the alert function on Squawkbox I was notified:
01-0040 3350 Swanwick mil
I had a ballpark frequency range to go looking at and there it was!
BUT... and this is what I find frustrating. I had to be there at the time. An ability to stipulate what fields are logged in the reporter would be sooo nice for reference, hence my original query.
Incidentally, thank you for alerting me to the possibility, though rare, that squawks might change enroute. I encountered exactly that, and was left rubbing my eyes (it was early am) to be sure I'd seen it happen.
A49929 CMB461 N396AX B763 Omni Air Internat... 2011/12/21 03:22:22
Showed initially on Squawkbox as N396AX 4121 Transit (ORCAM) Frankfurt, then just over the Irish Sea it changed to N396AX 4144 Transit (ORCAM) Dusseldorf. So for a brief moment I had 2 N396AX flights in Squawkbox. Interesting.
Cheers