U.S. Navy SWO AQDs Explained: The Codes You Need To Know

Most SWOs first notice AQDs when a slating call gets serious, a board is coming up, or a billet description suddenly says one is required. The codes look small. Their effect is not.

An AQD is one of the fastest ways the Navy can understand what you have actually done, what you are qualified to do, and where you fit next. A detailer can read a cluster of AQDs in seconds and form a view of your platform depth, your warfighting focus, and your career timing. That is why clean AQD data can help a record feel coherent, while missing codes can make a strong record look thinner than it is.

The PERS-41 frames them the same way board members do. They are quick identifiers for the qualifications that shape your record, and they show up where people actually look.

For Surface Warfare officers, the codes that matter most sit in two families. The L series tends to capture warfare identity, shipboard qualification, command progression, and navigation or tactical watchstanding. The K series tends to capture mission specialization, especially in AEGIS, WTI, and advanced ASW. Once you know how to read those families, the AQD system stops looking like random admin and starts looking like a career map.

AQDs are the Navy’s shorthand for capability

Inside the Navy Officer Occupational Classification System, AQDs exist to record qualifications and skills that your designator, grade, NOBC, or subspecialty do not fully capture. That matters because a 1110 tells the Navy you are a SWO. It does not tell the Navy whether you are an AEGIS tactician, an engineering expert, a WTI, a command-qualified officer, or a navigator with deep bridge credibility.

Each AQD has three characters. The first character marks a broad occupational area. The second narrows the field. The third defines the specific qualification. For SWOs, that structure becomes useful very quickly. LA9 is not just another code. It is the Navy’s compact way of saying, “This officer is formally qualified as a Surface Warfare Officer.” KA6 tells a completely different story. It points to AEGIS depth. KW2 points to IAMD WTI training. LG1 points to navigation expertise, not just basic watchstanding.

The system also works in two directions. An officer AQD means you have earned the qualification. A billet AQD means the job requires it. That second piece is what makes AQDs practical, not decorative. Many entries in the code tables state that an officer must already hold the code before reporting to the billet. In plain English, the code can be a gate, not a souvenir.

The structure is also less tidy than it looks in the AQD manual. Part D is being revised, and the Navy warns that some entries still sit out of logical alphanumeric order. That matters because a casual skim can miss relevant codes. The safe method is to search by code family and read the whole local section, especially in the K and L ranges.

Once you understand that AQDs are a manpower tool first and a record tool second, the system makes much more sense. The Navy is trying to match real capability to real jobs. Your task is to make sure your record tells the truth clearly.

Where AQDs live in your record, and why missing ones hurt

AQDs matter because they sit where boards and detailers can actually see them. They are not buried trivia.

On the PSR, they appear at the bottom of the cover page. That location matters because the cover page is often the first thing anyone sees when they review a record. On the Officer Data Card, AQDs live in Item 72, listed as additional and special qualifications. The ODC instructions explain that this block identifies AQDs certified by competent authority, shows the year earned, and uses an asterisk to mark the officer’s primary AQD or warfare specialty.

That sounds administrative. In practice, it is a compressed career summary.

A board member reading your FITREPs still wants to know what the Navy has formally recognized. A detailer looking at you for a coded billet wants a faster answer. AQDs solve that problem. They show whether your shipboard qualifications were captured, whether your milestone status is current, and whether your specialization lines up with the billet you want next.

This is why missing AQDs can create real friction. If you qualified as TAO, finished a BMD course, completed a WTI production tour, or screened for a milestone and the code never posted, the board does not get full credit to you at first glance. A human can still infer parts of the story from FITREPs, but you have made your record harder to read. That is almost never a winning strategy.

There is another reason to care. Some billets are coded to require the AQD before you report. In that setting, the issue is not just recognition. It is eligibility. A qualification letter in your inbox is useful. The correct AQD on your record is what makes the manpower system recognize it.

That is why the smartest officers treat AQDs like readiness items. They are not something to check once every few years. They belong in the same routine as FITREP review, awards verification, and photo updates. If your record is going to tell your story in a board room, it needs to tell it cleanly and early.

The milestone AQDs that mark your career stage

Not every AQD carries the same weight. Some codes describe a shipboard skill. Others define where you are in the SWO career ladder. Those milestone AQDs matter most because they answer the question every board asks first: What stage officer is this, and is the record moving on time?

The anchor code is LA9, the formal AQD for a qualified Surface Warfare Officer. It is the baseline identity marker for the community. The current rule set is tight. The code is tied to formal SWO qualification standards, and the manual notes that only 111X is eligible to receive it going forward, while officers who held it before the 2018 rule change may retain it. If LA9 is missing from a true SWO record, everything else downstream starts to look unstable.

From there, the next major gate is LA5, which means Department Head Afloat. This code matters because it is not a casual reflection of having served in a hard job. It requires LA9, selection by the Surface Department Head Selection Board, and a contract that carries service through two DH tours or one longer DH tour. That makes LA5 a commitment marker as much as a qualification marker.

Next comes LK8, the key XO screening code. It records that the officer has been surface screened for XO afloat style assignments. This is one of the clearest signs that the record has moved from solid post-DH performance into true milestone territory.

Then comes LN7, which records qualified surface command. This is the code that tells the system you have completed the formal requirements for command. After that, the LN1 through LN4 series records actual command experience by rank tier, while LN8 records eligibility for sequential major command.

A clean way to read the core milestone stack is this:

These codes work because they compress timing. A strong milestone record looks ordered. LA9 appears first. LA5 appears when the officer commits to the DH path. LK8 and LN7 appear when the record has matured enough to support command timing. If those codes show up late, or not at all, a board starts asking whether the record is truly on glidepath.

The milestone section is also where the current Surface Warfare Officer manual matters in the background. LA9, later command qualification, and the bridge between operational performance and formal recognition still sit inside fleet qualification guidance, not informal community lore. AQDs simply give the Navy a way to record that progress in a form the manpower system can use.

The shiphandling, engineering, and watchstanding AQDs that build early credibility

If milestone AQDs tell the Navy where you are in your career, watchstanding AQDs tell the Navy what you can be trusted to do on a ship. For junior officers and early post-DIVO SWOs, this part of the record often carries the most immediate weight.

Start with the LB series. LB2 records OOD qualification for fleet maneuvers and task group or force operations. That is more than simple bridge standing. It signals qualification in a more demanding operational setting. LB3 records Command Duty Officer Underway, which tells a detailer or board that the officer has moved beyond routine watchstanding into a broader command-responsibility context.

Then come the LC codes, which capture engineering watchstanding. LC1, LC2, and LC3 cover EOOW qualification in steam, diesel, and gas turbine plants. Those are classic signals of technical competence because they tell the record you did not just work around the plant. You qualified to manage it. The later LC variants sharpen the picture by platform. LC5 is EOOW on a CVN. LC6 and LC9 distinguish the two LCS variants. LC7 captures LHD and LHA gas turbine electric plants. LC8 captures DDG 1000.

That platform specificity matters. A generic statement that you are “engineering strong” is vague. An LC code shows what kind of plant you mastered.

The LF codes do the same thing for tactical watchstanding. LF6 records TAO in a non-NTDS unit. LF7 records TAO in an NTDS equipped unit. For many SWOs, especially on combatants, LF7 becomes one of the most meaningful watchstanding signals on the record because it shows you can manage the fight, not just the watchbill. LF9 is different. It records at least ninety days on a tour involving employment of ship offensive or defensive weapons systems against a hostile threat. That code carries real operational weight because it points to combat systems employment under hostile conditions.

Finally, LG1 marks Navigation Expert, Surface Ship. This code is more selective than many officers assume. It requires completion of navigator qualification requirements, a minimum of twelve months in billet as Navigator, and commanding officer recommendation. That makes LG1 a strong differentiator for officers whose records lean toward shiphandling, seamanship, and command-at-sea credibility.

The smartest way to think about these codes is not as a checklist to collect. It is to ask which ones best prove you can operate your platform at a high level. For a DIVO, that usually means bridge and engineering depth first. For a DDG or cruiser officer, TAO becomes more central. For someone building a navigation-heavy profile, LG1 stands out. A record with the right LB, LC, LF, and LG combination reads like a shipboard résumé in compressed form.

The warfare specialization AQDs that separate one SWO from another

Once the basics are in place, AQDs start doing a different job. They stop proving that you can qualify, and start showing how you specialize. This is where two officers with the same designator and similar FITREP language can begin to look very different on paper.

The classic example is KA6, the AEGIS Officer AQD. This is one of the strongest specialization signals in the SWO community because it tells the Navy that your combat systems experience is not casual. The code can be earned through completion of the AEGIS CSO or PCO/PXO course combined with qualifying service in key roles on a CG-47 or DDG-51, or by qualifying as TAO on those classes. In practical terms, KA6 tells the system you have real credibility inside the Navy’s core air and missile defense combatant force.

The BM series does something similar for ballistic missile defense. BM1 is the foundational code. It can come from a qualifying tour on an AEGIS BMD ship in key billets, from qualification as TAO, AAWC, or CSC in that environment, or from a BMD related staff assignment that supports planning or execution. BM2 is the senior progression code. BM3 records completion of the Maritime Integrated Air and Missile Defense Planning System operator course. BM4 captures junior technical engineer and supervisor experience in Missile Defense Agency aligned work.

Read together, those four codes tell a more nuanced story than “BMD experience.” They distinguish operator, planner, senior practitioner, and technical engineer paths.

Then there is KX1, the advanced ASW code. This one is especially useful because it combines training and practice. The officer must complete the Surface Anti-Submarine Warfare Evaluator course, complete the Advanced ASW Officer course, and spend six months in a qualifying billet. That last part matters. KX1 is not just classroom exposure. The record is saying the officer learned the trade and then worked it.

This is where platform logic should drive your priorities. A DDG officer often benefits most from KA6, one or more BM codes, and eventually a KW2 if the WTI path opens. A ship that lives closer to the ASW problem set makes KX1 more valuable. An amphibious record may lean less on AEGIS depth and more on command, navigation, or warfare development paths.

A practical table makes the point clearer:

The point is not to chase every code. It is to build a specialization pattern that matches the billets you want and the jobs the Navy will trust you with next.

The elite differentiators, WTI and AEI

Some AQDs do more than reflect experience. They mark entry into recognized high-value talent tracks. In the surface community, two of the most important are WTI and AEI.

The WTI family starts before graduation. KWS records that an officer has been administratively screened for Warfare Tactics Instructor. That matters because it shows selection into the pipeline, not just interest. The tactical credentials then split by mission area. KW1 is ASW and SUW. KW2 is Integrated Air and Missile Defense. KW3 is Amphibious Warfare. KW4 is Mine Warfare. After that, KWC records completion of a WTI production tour.

That last code is important because it distinguishes classroom excellence from fleet contribution. A WTI without the production tour is a graduate. A WTI with KWC has already taken the knowledge back into force generation, training, or tactical development work. Boards understand that difference.

WTI codes carry unusual signal value because they combine competitive selection, formal instruction, and fleet impact. They also suggest that the officer may be valuable in billets well beyond a single ship. That can be an advantage, but it also means timing matters. A WTI path should fit your milestone flow, not fight it.

The same is increasingly true for the Advanced Engineering Instructor program. The current community brief treats AEI as a named talent track, not a niche side job. It lays out a production model of 45 AEIs per year with a force goal of one AEI per ship by 2033, which tells you how seriously the community now treats engineering expertise and maintenance performance.

The AEI AQDs make the track easy to read. LAS records selection into the AEI program. The course graduates then receive a propulsion-specific code. LAB is steam. LAD is diesel. LAG is gas turbine. LAH is hybrid. These are not generic engineering decorations. They tell the Navy exactly what kind of maintenance and propulsion depth you bring.

For a SWO deciding between tactical specialization and engineering specialization, the trade is not prestige versus irrelevance. It is two different kinds of value. The WTI route often signals warfighting development and tactical excellence. The AEI route signals material readiness, technical authority, and fleet maintenance impact. Both can be powerful. The right choice depends on what sort of officer you want your record to describe.

How boards and detailers read an AQD stack

A single AQD can matter. A cluster matters more.

Boards and detailers rarely read one code in isolation. They read combinations. That is why the best AQD stacks feel coherent. They tell a story without forcing the reader to infer too much.

Take one officer with LA9, LB2, LB3, LC3, and LG1. Even before you read every FITREP line, the record suggests a SWO with strong bridge and shiphandling depth, command duty credibility, gas turbine plant qualification, and serious navigation time. That officer may still be tactically strong, but the AQD pattern says “ship driver and mariner” first.

Now look at an officer with LA9, LF7, KA6, BM1, and KW2. The record immediately shifts. This is a combat-systems-heavy profile with air and missile defense weight, TAO credibility, and advanced tactical training. The likely billet fit is very different.

A third officer with LA9, LA5, LK8, LN7, and one WTI or AEGIS code tells yet another story. This is a record that has crossed the basic qualification threshold, committed to DH, screened into milestone progression, and preserved enough specialization to remain distinctive.

That narrative quality is why AQD gaps matter so much. A strong FITREP can say you were a standout Operations Officer. A missing KA6 or LF7 makes that story feel less formalized. A command-qualified officer without LN7 creates unnecessary ambiguity. A navigator-heavy record without LG1 leaves value on the table.

Detailers also care about fit and timing. They need to know whether you are merely eligible for a billet, whether the billet requires a prerequisite AQD, and whether your record lines up with what comes after that tour. In other words, they do not just ask whether you are good. They ask whether your qualifications make manpower sense.

This is also where current post-DH timing matters. The recent Surface Warfare Command Leadership Assessment replaced the old Surface Command Oral Board for officers who had not already completed it, which is one more reminder that formal gates change, while AQDs remain the durable shorthand the record uses to reflect progress through those gates.

If you want your AQDs to help you, do not think of them as badges. Think of them as narrative control. The cleaner the pattern, the easier it is for the right reader to reach the right conclusion fast.

How to audit and fix your AQDs before a board or orders negotiation

The best time to fix an AQD is long before you need it. The second-best time is now.

Start with a basic audit. Pull your PSR and your ODC. On the ODC, go straight to Item 72. Then compare the recorded codes against what you have actually earned through qualification letters, course completions, board results, and documented tours. This sounds simple. It works because it forces you to match formal record entries against proof, not memory.

A useful audit checklist looks like this:

1. Confirm the anchor code. If you are a qualified SWO, LA9 should be there.
2. Confirm platform and watchstanding codes. Bridge, TAO, EOOW, navigator, and similar qualifications should match your ship and actual role.
3. Confirm specialization codes. AEGIS, BMD, WTI, advanced ASW, or AEI entries should reflect the training and billets you completed.
4. Confirm milestone codes. DH, XO screening, command qualification, and command experience codes should post when the formal gate is complete.
5. Confirm the timing. A code earned too late can still hurt if the record was reviewed before it posted.

For active duty officers, the fix usually runs through your assignment desk or detailer with supporting documentation. The ODC instructions direct AQD questions to the individual assignment desk, which is one reason officers who wait until the week before a board often create avoidable stress for themselves. The proof package is usually straightforward. Use the designation letter, course certificate, board result, FITREP support, or other official paperwork that directly ties to the awarding criteria.

For reserve officers, the process is more explicit. The MyNavyHR page for Reserve officers may request an AQD lays out the route through PERS-911D, including mail, fax, and email options, and makes clear that requests should include the supporting documentation needed to show qualified experience or education.

The officers who handle this best usually do three things well. They review quarterly. They keep their source documents. They think ahead of boards and slating windows.

AQDs do not replace performance. They do make performance legible. In a community where timing, fit, and formal qualification all matter, that is more than enough reason to keep them clean.

You may also be interested in comparing Navy SWO vs Submariner Officer career paths, exploring Navy SWO vs Supply Corps options, and reviewing What Navy Officer Jobs Are In Demand? to see where SWO fits among top communities.