I think I've stopped shivering enough to weigh in on this. First, let me start by saying that I was a controller, and ATC instructor, Operations specialist and tower manager over a 30-year career as well as a licensed pilot and ground school instructor. Throughout that time I learned there is a vast difference between "what is done" and "what is right". With a little variance there is one "right" but sloppiness, laziness, lack of knowledge and a dislike for "being formal" make what we practice often look and sound very different.
The correct stuff is outlined (in the USA) in the Aeronautical Information Publication (AIP). Of course that's a pretty big document and who reads the manuals thoroughly anyway? We want to hit the highlights (and, unfortunately, so do instructors so they don't bore or overwhelm students) plus there's always the feeling that 'close enough is pretty good'.
BrittMac, I'll quote you but I bet the comments are pretty typical from everywhere so forgive me if it seems I'm picking on you...
This is basically what we do, at least in the BHM area. I've flown down to the coast a bit, and to the ATL area, and it's much the same.
BHM controllers want ...).
Every region may operate a little differently, as well as every controller may do his/her own thing. Generally, you will check in with like, "Cherokee N7728N, BHM approach". They don't mind dropping the initial N usually. If you read off "7728N", and they come back with "N7728N", that is a hint to use the whole thing in my area.
I looked, but I could only find one AIP. There don't seem to be regional versions.

Initially we all try to teach and learn 'by the book' but once taught (and, in this case, licensed) there's a strong desire to develop a personality. This does get passed on and what's the problem? Nothing, until some guy with a briefcase has to investigate because someone else got scared, hurt, or killed. Then we all get a reminder that there is really only one 'correct' way to do and say things.
but the main thing for me was his comment that there are no written rules regarding the call out. i wouldn't have a clue as how to look it up.lol
In response, I call "BS". The rules are described for ATC communications but the same content and format is what pilots expect to hear regardless of location. Of course, people will always search for a convenient justification...
In this case, to answer Dave's question, it is what is laid out in the AIP (GEN 3.7-6 et al) The .pdf can be found here:
https://www.faa.gov/air_traffic/publications/media/AIP.pdf (see pages 216-217 of 1682 in the .pdf)
4.4.1.1 Radio communications are a critical link in the ATC system. The link can be a strong bond between pilot and controller − or it can be broken with surprising speed and disastrous results. Discussion herein provides basic procedures for new pilots and also highlights safe operating concepts for all pilots.
4.4.3.1 Improper use of call signs can result in pilots executing a clearance intended for another aircraft. Call signs should never be abbreviated on an initial contact or at any time when other aircraft call signs have similar numbers/sounds or identical letters/numbers, (e.g., Cessna 6132F, Cessna 1622F,Baron 123F, Cherokee 7732F, etc.).
4.4.3.2 (in part says) ATC specialists may initiate abbreviated call signs of other aircraft by using the prefix and the last three digits/letters of the aircraft identification after
communications are established. The pilot may use the abbreviated call sign in subsequent contacts with the ATC specialist. When aware of similar/identical call signs, ATC specialists will take action to minimize errors by emphasizing certain numbers/letters, by repeating the entire call sign, repeating the prefix, or by asking pilots to use a different call sign temporarily.
4.4.3.3 Civil aircraft pilots should state the aircraft type, model or manufacturer’s name followed by the digits/letters of the registration number. When the aircraft manufacturer’s name or model is stated, the prefix “N” is dropped.
YMMV from area to area. Go to LiveATC and listen to some traffic. It's a great way to learn about different areas.
We all like to find info on the internet, but remember that it is often what people think they should do, or what is common practice; it may not be right, in spite of it's repeated use. Listen and learn, but vet it against the source before assuming it is right. The use of non-standard identification techniques in Dave's question may likely get a response of: "Well, that's what they do at Oshkosh!" OSH is a very different world - for 10 days. I am willing to bet that a pilot ready for takeoff wouldn't be able to tell if the speck he sees downwind (or worse, on final) is a blue-and-white Cessna or if it is the correct one of four. As a controller I might tell a pilot his traffic is blue (or red, etc.) but that would be part of a more detailed idea of position and only if it was readily identifiable by color and critical.
I'm often accused of being the grammar-police (which is why I got to edit a published novel). Here there's a difference - bad grammar is poor performance, but bad phraseology in the ATC world can actually hurt. I'd be surprised if an accident investigator would take kindly to a defense of: "That's what I learned from YouTube".
<class dismissed>
