Posted on Jun 20, 2016
I am Army and may soon be attached to a Joint Forces HQ. How should I address Air Force NCOs?
17.6K
130
57
18
18
0
So I might soon be working at the Colorado National Guard Joint Foces HQ with the protection force. I have never really been around Air Force and I was curious how I should address Air Force NCOs, by their exact rank? Or how we do in the Army where E-5 through E-7/8 is Sergeant? Help please.
Customs and Courtesies
NCOs
Posted >1 y ago
Responses: 28
7
7
0
SPC (Join to see) You show your professionalism by asking the question. Nice work. Capt Prickett has it right.
(7)
(0)
SPC (Join to see)
Thank you sir, I thought I'd seek guidance instead of blindly teaching and learning myself, considering how man higher ups will be at that site.
(1)
(0)
5
5
0
By their rank usually works for me. However it is the Air Force so it may be as simple as using their first name.
(5)
(0)
Lt Col John (Jack) Christensen
Come on Charles, we may be new and the youngest service but we have military traditions and use rank when addressing people.
(1)
(0)
SSG (Join to see)
I know sir, couldn't resist getting a quick jab in. My sister and my daughter were AF, and my son-in-law is AF.
(0)
(0)
4
4
0
SPC (Join to see)
I worked for an Air National Guard Unit (contractor) at my last job.
While I obviously called everyone by first name, the Airmen did go by shortened rank:
E1-E4 - Airman
E5-E7 - Sergeant
E8 - Senior (if you know the person) or Senior Master Sergeant (I never heard an Air Force E8 get called just Sergeant)
E9 - Chief (short for Chief Master Sergeant)
Officers will be easy, just call them Sir/Ma'am, LOL...
I worked for an Air National Guard Unit (contractor) at my last job.
While I obviously called everyone by first name, the Airmen did go by shortened rank:
E1-E4 - Airman
E5-E7 - Sergeant
E8 - Senior (if you know the person) or Senior Master Sergeant (I never heard an Air Force E8 get called just Sergeant)
E9 - Chief (short for Chief Master Sergeant)
Officers will be easy, just call them Sir/Ma'am, LOL...
(4)
(0)
Read This Next
Continue with Facebook 
Continue with Google