Posted on Oct 19, 2017
If you are in a Language Dependent MOS (35N) but not slotted or in a language billet, can you still receive FLPB?
4.11K
2
1
0
0
0
AR 11-6, Chapter 6, e (2)
"(1) The Defense Language Office will determine which languages on the strategic language list are dominant in the force. When a language is also identified by the Army as dominant in the force, the Army will only pay FLPB to Soldiers in a language dependent MOS/specialty or language-coded billet. For example, Spanish has been identified as a dominant language. Only those Soldiers who are in a language dependent MOS/specialty or language-coded billet for Spanish will be paid FLPB for Spanish."
"(1) The Defense Language Office will determine which languages on the strategic language list are dominant in the force. When a language is also identified by the Army as dominant in the force, the Army will only pay FLPB to Soldiers in a language dependent MOS/specialty or language-coded billet. For example, Spanish has been identified as a dominant language. Only those Soldiers who are in a language dependent MOS/specialty or language-coded billet for Spanish will be paid FLPB for Spanish."
Edited 7 y ago
Posted 7 y ago
Responses: 1
35N is a Language Capable MOS, not a Language Dependent MOS. This means that successfully completing a language program at DLIFLC is not required for you to be awarded your MOS, and there is not requirement for you to retake the DLPT (and pass) on an annual basis.
Therefore, you would need to be placed into an analyst billet that specifically requires you to utilize spanish in order to be eligible for FLPB. These positions are normally coded as language billets in eMilpo. Speak with your S-1 to see if you are in a billet that requires spanish.
Therefore, you would need to be placed into an analyst billet that specifically requires you to utilize spanish in order to be eligible for FLPB. These positions are normally coded as language billets in eMilpo. Speak with your S-1 to see if you are in a billet that requires spanish.
(0)
(0)
Read This Next