If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Transmissions
November 12345, a Cessna 172, 20 miles northeast of Sugarloaf Mountain, level
VFR seven thousand five hundred, en route to Winston-Salem, North Carolina." For those who like to write lists, it would look like this: 1) FULL callsign; 2) Type aircraft; 3) Current location; 4) Current altitude and altitude to which you are climbing/descending; and, 5) Destination. There is a method behind my madness. Most Center controllers will find this format comfortable and oddly familiar. That's because it's the format that the flight plan is written on a flight progress strip. Guess I will not listen to hangar talk and continue giving the whole spiel, until advised different. Hank |
#2
|
|||
|
|||
"Hankal" wrote in message ... November 12345, a Cessna 172, 20 miles northeast of Sugarloaf Mountain, level VFR seven thousand five hundred, en route to Winston-Salem, North Carolina." For those who like to write lists, it would look like this: 1) FULL callsign; 2) Type aircraft; I would combine the two, "Skyhawk 12345". Please, do not combine them as "Cessna 172 12345" |
#3
|
|||
|
|||
"Hankal" wrote in message
Guess I will not listen to hangar talk and continue giving the whole spiel, until advised different. The part you quoted isn't quite in context without the preceding section: quote ....I've been told by some approach controllers that they want all the flight information on the initial check in. I can't imagine why, but I won't argue about it. I prefer this method straight out of the AIM. "Atlanta Center, Cessna 12345 requesting VFR advisories." That serves to get my attention. It's short and lessens the chance that you'll transmit at the same time someone else is transmitting. It's just a good idea, period. Once I'm off the landline, I'll say, "Calling Atlanta Center, say again." You, realizing that Center controllers are slow, will say, "Atlanta Center, Cessna 12345 requesting VFR advisories." I'll hit the CODE key on my keyboard, type in N12345 and press ENTER. Seeing as it's me doing the typing, I'll go back and make sure I really hit the CODE key this time, type in N12345 and press ENTER. (I always said I could be a great controller if I could just learn to type.) The computer will spit out a beacon code and I'll say, "Cessna 12345 squawk 3231 and go ahead." /quote The quote above is from a Center controller whose job is a bit different from a TRACON controller. If providing all information on the initial call-up works for you in your area, by all means continue doing so. However, if you're not already in the system (e.g., known to the controller), the controller may spend a few seconds scanning his scope for your tail number when you call him up the first time. That may cause a complete re-transmission of your request which ties up the airwaves even longer. To minimize this possibility, be sure to use "VFR" right after your tail number on initial call-up. Another source of information is AIM §4-2-3.a.1: quote 1. The terms initial contact or initial callup means the first radio call you make to a given facility or the first call to a different controller or FSS specialist within a facility. Use the following format: (a) Name of the facility being called; (b) Your full aircraft identification as filed in the flight plan or as discussed in paragraph 4-2-4, Aircraft Call Signs; (c) When operating on an airport surface, state your position. (d) The type of message to follow or your request if it is short; and (e) The word "Over" if required. EXAMPLE- 1. "New York Radio, Mooney Three One One Echo." 2. "Columbia Ground, Cessna Three One Six Zero Foxtrot, south ramp, I-F-R Memphis." 3. "Miami Center, Baron Five Six Three Hotel, request V-F-R traffic advisories." /quote -- John T http://tknowlogy.com/TknoFlyer http://www.pocketgear.com/products_s...veloperid=4415 ____________________ |
#4
|
|||
|
|||
In a previous article, "John T" said:
EXAMPLE- 1. "New York Radio, Mooney Three One One Echo." 2. "Columbia Ground, Cessna Three One Six Zero Foxtrot, south ramp, I-F-R Memphis." 3. "Miami Center, Baron Five Six Three Hotel, request V-F-R traffic advisories." /quote It's a good thing they put dashes between the letters there to indicate you spell those things out. I've been saying "viffer" and "eye-fer" all this time. :-) -- Paul Tomblin http://xcski.com/blogs/pt/ "Tech Services - We Aim To Please, We Shoot To Kill" -- H. Wade Minter, ASR |
#5
|
|||
|
|||
I would combine the two, "Skyhawk 12345". Please, do not combine them as
"Cessna 172 12345" I never use Cessna 172. Always use Skyhawk. Of course some controllers come back "say aircraft" |
#6
|
|||
|
|||
You might know what your aircraft is, but don't expect everyone else to do
so. You are in a 172 offficially, so why not announce yourself as so? I fly from a major international airport, they aren't interested that I fly a brand new Archer, they tell all the 737's and Airbus's to "look out for the Cherokee on base" It's a PA28 to them. John "Hankal" wrote in message ... I would combine the two, "Skyhawk 12345". Please, do not combine them as "Cessna 172 12345" I never use Cessna 172. Always use Skyhawk. Of course some controllers come back "say aircraft" |
#7
|
|||
|
|||
Here in the UK, the controllers like your first call to be just the approach
name and your callsign. Around London, they are usually very busy and often will reply with a message to standby. When they come back to you, then you give full details and intentions. There is no point transmitting everything first call if he's not ready to talk to you John "John T" wrote in message ws.com... "Hankal" wrote in message Guess I will not listen to hangar talk and continue giving the whole spiel, until advised different. The part you quoted isn't quite in context without the preceding section: quote ...I've been told by some approach controllers that they want all the flight information on the initial check in. I can't imagine why, but I won't argue about it. I prefer this method straight out of the AIM. "Atlanta Center, Cessna 12345 requesting VFR advisories." That serves to get my attention. It's short and lessens the chance that you'll transmit at the same time someone else is transmitting. It's just a good idea, period. Once I'm off the landline, I'll say, "Calling Atlanta Center, say again." You, realizing that Center controllers are slow, will say, "Atlanta Center, Cessna 12345 requesting VFR advisories." I'll hit the CODE key on my keyboard, type in N12345 and press ENTER. Seeing as it's me doing the typing, I'll go back and make sure I really hit the CODE key this time, type in N12345 and press ENTER. (I always said I could be a great controller if I could just learn to type.) The computer will spit out a beacon code and I'll say, "Cessna 12345 squawk 3231 and go ahead." /quote The quote above is from a Center controller whose job is a bit different from a TRACON controller. If providing all information on the initial call-up works for you in your area, by all means continue doing so. However, if you're not already in the system (e.g., known to the controller), the controller may spend a few seconds scanning his scope for your tail number when you call him up the first time. That may cause a complete re-transmission of your request which ties up the airwaves even longer. To minimize this possibility, be sure to use "VFR" right after your tail number on initial call-up. Another source of information is AIM §4-2-3.a.1: quote 1. The terms initial contact or initial callup means the first radio call you make to a given facility or the first call to a different controller or FSS specialist within a facility. Use the following format: (a) Name of the facility being called; (b) Your full aircraft identification as filed in the flight plan or as discussed in paragraph 4-2-4, Aircraft Call Signs; (c) When operating on an airport surface, state your position. (d) The type of message to follow or your request if it is short; and (e) The word "Over" if required. EXAMPLE- 1. "New York Radio, Mooney Three One One Echo." 2. "Columbia Ground, Cessna Three One Six Zero Foxtrot, south ramp, I-F-R Memphis." 3. "Miami Center, Baron Five Six Three Hotel, request V-F-R traffic advisories." /quote -- John T http://tknowlogy.com/TknoFlyer http://www.pocketgear.com/products_s...veloperid=4415 ____________________ |
#8
|
|||
|
|||
"John Bishop" wrote in message ... You might know what your aircraft is, but don't expect everyone else to do so. You are in a 172 offficially, so why not announce yourself as so? What makes "172" any more "official" than "Skyhawk"? |
#9
|
|||
|
|||
In article ,
Hankal wrote: I never use Cessna 172. Always use Skyhawk. Of course some controllers come back "say aircraft" I've had controllers come back and say "say type aircraft" in response to a spiel including "cessna 1 7 2 slant golf". -- Ben Jackson http://www.ben.com/ |
#10
|
|||
|
|||
"Steven P. McNicoll" wrote...
November 12345, a Cessna 172, 20 miles northeast of Sugarloaf I would combine the two, "Skyhawk 12345". That will work, now that the A-4 has been retired from the Navy... ;-) For those who don't have the list in front of them, a couple old rule of thumbs: Initial contact: Callsign Altitude "XYZ Center, Skyhawk 12345, 7,500'." Then, after the controller responds, Who you are Where you are What you want "XYZ Center, Skyhawk 12345, 20 miles NE of Sugarloaf, 7,500', enroute Winston-Salem, request VFR flight following." |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Transmissions? | Hankal | Instrument Flight Rules | 7 | April 3rd 04 04:05 PM |