Welcome, Guest. Please login or register.
Did you miss your activation email?
December 14, 2018, 05:40:24 AM
Home Help Login Register
News:

CAP Talk  |  General Discussion  |  Uniforms & Awards  |  Topic: Specialty badges question
0 Members and 1 Guest are viewing this topic.
Pages: [1] Print
Author Topic: Specialty badges question  (Read 636 times)
WillTheCommsGuy
Recruit

Posts: 6
Unit: MER-SC-099

« on: October 04, 2018, 03:39:39 PM »

Hello everyone,
I have a question about the specialty track badges (ES, Comm, etc). Hypothetically, if a member had both the ES badge and the Comm badge, which one would he/she wear on their blues shirt? I know they go on the right pocket, but does one take precedence over the other?


Sent from my iPhone using Tapatalk
Logged
Dwight Dutton
Forum Regular

Posts: 155

« Reply #1 on: October 04, 2018, 04:04:00 PM »

You can wear both, one goes on each pocket.  I don't think it makes a difference which one has the higher level to it.
Logged
WillTheCommsGuy
Recruit

Posts: 6
Unit: MER-SC-099

« Reply #2 on: October 04, 2018, 06:33:54 PM »

You can wear both, one goes on each pocket.  I don't think it makes a difference which one has the higher level to it.

Thank you. I have the communications badge, and I am going to take my ES specialty track soon.


Sent from my iPhone using Tapatalk
Logged
Dwight Dutton
Forum Regular

Posts: 155

« Reply #3 on: October 04, 2018, 07:35:27 PM »

You can wear both, one goes on each pocket.  I don't think it makes a difference which one has the higher level to it.
Thank you. I have the communications badge, and I am going to take my ES specialty track soon.

Used to be that was only true about the AF blue shirt, but as of the last revision you can wear a specialty track badge on both pockets on the white shirt as well.
Logged
Pages: [1] Print 
CAP Talk  |  General Discussion  |  Uniforms & Awards  |  Topic: Specialty badges question
 


Powered by MySQL Powered by PHP SMF 2.0.14 | SMF © 2017, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.051 seconds with 25 queries.