Air Force Specialty Code
FUF
The Air Force Specialty Code (AFSC) is an alphanumeric code used by the United States Air Force to identify a specific job. Officer AFSCs consist of four characters and enlisted AFSCs consist of five characters. A letter prefix or suffix may be used with an AFSC when more specific identification of position requirements and individual qualifications is necessary. The AFSC is similar to the military occupational specialty codes (MOS Codes) used by the United States Army and the United States Marine Corps or enlisted ratings and USN officer designators and Naval officer billet classifications (NOBCs) used by the United States Navy and enlisted ratings and USCG officer specialties used by the United States Coast Guard. The United States Space Force equivalent is known as the Space Force Specialty Code (SFSC).
History
After the Air Force separated from the Army in 1947, it retained the Army's system of MOS occupation codes, modifying them in 1950. These were 5-digit codes; for example a maintenance data systems specialist was 39150 and a weather technician was 25170. In October 1993, the Air Force implemented a new system of AFSCs, aligning occupations with the force wide restructuring that was implemented under Merrill McPeak. These reduced officer AFSCs from 216 to 123 and enlisted AFSCs from 203 to 176.
Enlisted AFSCs
The enlisted AFSC consists of five alphanumeric characters:
Career group (numerical)
Operations
Logistics & maintenance
Support
Medical
Professional
Acquisition
Special investigations
Special duty identifiers, typically used for Airmen chosen for specialized jobs
Reporting identifiers, typically used for Airmen in transitive status: trainees, awaiting retraining, prisoner, etc.
Begin with the source’s own compact description: “Air Force Specialty Code” is fUF. The dossier treats that line as a proposition to test through Force, Specialty and Code, not as a finished interpretation.
Why this record matters
The phrase “fUF” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 3, 2026. The linked authority identifier is Q4697964. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1947, 1950 and 1993.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Air Force Specialty Code”, its source revision and the description used here.
- Expand the search: follow Air Force Specialty Code primary sources, Air Force Specialty Code archive and Force research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Air Force Specialty Code”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Air Force Specialty Code” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.