Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to RW Robotics Warfare Specialist — overview, pay, training, civilian translation, reviews
RWE1-E3

Robotics Warfare Specialist

E-1 to E-3 (Junior Enlisted) · Navy

E1–E3E-4E-5E-6E-7E8–E9
HEADS UP

You are entering a rating with less than two years of institutional history. The pipeline is real, the mission is real, and the safety requirements are absolute — but the NEC catalog, the advancement bibliography, and the chief's mess tradition for RW are all being written while you wear the uniform. That is not a warning to avoid this rate; it is a heads-up that you cannot borrow the playbook from a senior who has twenty years of RW experience, because that person does not exist yet.

The Honest MOS Read
Robotics Warfare Specialist (RW, SR through RWSN) is the Navy's newest enlisted rating, established February 2024 under NAVADMIN 036/24. You are not the first class to come out of any long-established A-school; you are the first generation of Sailors to wear this designator in the fleet. The pipeline has been stood up — a course of instruction built around unmanned systems operation, autonomous vehicle fundamentals, robotic systems maintenance, sensor employment, and the human-operator control framework that DoD Directive 3000.09 requires — but the curriculum is newer than the uniform you arrived in, and the schoolhouse instructors are the first people certified to teach it. When you check aboard your first command, you may be one of a handful of designated RWs in the division, or possibly the first one who has come directly from the formal pipeline. The commands that are integrating this rating — surface combatants with unmanned surface vehicle (USV) or unmanned underwater vehicle (UUV) programs, mine countermeasures (MCM) commands using autonomous clearance systems, Naval Special Warfare support elements using unmanned maritime platforms, and expeditionary commands building robotic warfare capability — are themselves figuring out how to integrate what you know into the way they operate. What that means practically: you are going to spend your first year doing the junior-enlisted work every rating does — pre-mission checks, post-recovery maintenance, log entries, PQS line items, working parties, watch-standing — but you will also be in rooms where more senior sailors who have not been through your schoolhouse are asking you to explain what the systems can and cannot do. That is an unusual position for an RWSN or RW3. Carry it carefully: defer to operational experience on mission employment, but do not underplay the technical depth the schoolhouse gave you. The safety-of-use framework is not optional. DoD Directive 3000.09 governs human-operator control requirements for autonomous weapons systems — what autonomy levels are authorized, who must be in the loop at each phase, and what conditions require an abort. You learned this in the schoolhouse and your senior operators know it. The Sailor who treats these protocols as bureaucratic overhead will find himself named in a safety investigation when something goes wrong, because these systems operate in complex environments and do not have the same forgiveness margin as a rifle that misfires. The daily work as a junior RW is more physical and more varied than the 'robotics' label might suggest. Unmanned system launch-and-recovery operations on a moving ship deck in sea state 3 is a hands-and-feet job. UUV maintenance involves confined spaces, heavy handling gear, and battery systems that carry real hazards. UAV operations in an expeditionary environment involve hauling ground control station equipment, setting up antennas, and operating on terrain that does not care what your job title is. Know the platform, know the manual, and stay current on the safety procedures — because the platform your section operates in 2027 may be a generation newer than what you trained on. The career calculus at this stage is simple: show up ahead of the maintainer who was there before you. Keep your log clean. Ask the questions during the AAR. Knock out PQS before the LCPO has to ask twice. The rate does not yet have the thirty-year record of advancement data that lets you benchmark yourself against the E-5 slate history — which means your individual performance is more visible, not less.
Career Arc
  • 01Complete A-school (verify current course length and location — the pipeline was still being formally established as of early 2025) and receive an RW designator and initial platform assignment.
  • 02Check aboard first command; achieve initial operator qualification on the command's primary unmanned system within the LCPO's published timeline.
  • 03Complete all RWSN PQS line items and earn the seaman designator; begin RW3 NWAE study cycle.
  • 04Earn baseline DoD 8140 cybersecurity certification if the billet requires it — Navy COOL funds the voucher; use it.
  • 05First re-enlistment / obligated-service decision: weigh the NEC pipeline options (advanced operator, maintenance technician, NSW support) that are available for the RW rating in the current cycle.
  • 06Advance to RW3 via NWAE; begin the operator-qualification track for the next platform capability level.
  • 07Identify a warfare device path (SW, EXW, FMF, or other) based on assignment and begin the qualification PQS.
Common Screwups
  • ×Unauthorized autonomy-level activation — operating an unmanned system in an autonomy mode not authorized by the chain of command. DoD Directive 3000.09 is a hard legal and policy line; a single unauthorized activation opens a command investigation regardless of outcome.
  • ×NJP, DUI, or drug pop — closes every advanced NEC pipeline, NSW support qualification, and commissioning program window in the rate.
  • ×Falsifying or retroactively altering a maintenance log or safety-of-use record. On a weapons-capable unmanned platform, this is a federal-records integrity issue, not a minor administrative matter.
  • ×OPSEC breach — posting imagery, sensor data, capability details, or operational specifics about the unmanned systems to social media. The intelligence value is real even for seemingly innocuous photos.
  • ×Fitness failure — a PRT fail on record follows the record into every NEC pipeline application and every advancement board; two failures in two years typically starts an administrative separation process under MILPERSMAN.

A Day in the Life

  • 0530–0620PT formation — unit PT schedule (varies by command; surface ships run PT on the pier or in the ship's gym; shore commands run on the track). As a junior RW you run with the section.
  • 0630–0700Rack time or personal hygiene; muster at 0700 in uniform of the day.
  • 0700–0730Division quarters — all hands formation, accountability, safety word of the day, plan of the day read. The LPO or LCPO addresses the section.
  • 0730–0800System status check: walk to the unmanned systems spaces or vehicle handling area, visual inspection of mission-ready systems, verify battery state, check weather and sea state for planned evolution, confirm next PMS card due.
  • 0800–1000Morning work period — pre-mission preparation if an evolution is planned (pre-launch checklist, briefing, configuration verification), OR maintenance period (PMS card execution, discrepancy repair, parts run to supply). The LCPO assigns the work; you execute it.
  • 1000–1100PQS study or training event (depends on day of week and training schedule). Onboard a ship during a workup, this may be a battle drill or DC training evolution instead.
  • 1100–1200Continued mission or maintenance work, OR final pre-launch checks if an afternoon evolution is planned.
  • 1200–1300Lunch — depending on assignment, the galley (shipboard) or the chow hall (shore). Work doesn't stop if there is a mission cycle underway.
  • 1300–1500Mission execution window (if evolution is scheduled) OR afternoon maintenance / administrative work: log entries, PMS scheduling, part requisitions, controlled-equipment inventory.
  • 1500–1600Post-recovery maintenance and inspection if a system was operated: rinse, dry, inspect, battery service, sensor check, discrepancy log, system stowage. Takes as long as it takes — no shortcuts.
  • 1600–1700Section sync or LPO check-in: what did you accomplish, what is pending, what does the log look like for the next shift or next day. The RWSN who shows up to this conversation with clean notes earns early liberty; the one who shows up without them does not.
  • 1700 onwardLiberty (garrison / normal ops) or continued ship's work if underway or in a workup cycle. Study for PQS or the NWAE in the evening — the BIB is not going to memorize itself.

Weekly Cadence

Monday through Wednesday in a garrison/in-port cycle tends to be the technical work window: PMS execution, corrective maintenance, mission planning for exercises or underway evolutions later in the week. Thursday and Friday often carry administrative and training weight — PQS reviews, command training events, qual boards, and the beginning-of-week preparation for whatever the next underway or field evolution brings. The rhythm changes sharply in a workup cycle or deployed configuration: the ship's schedule drives everything, morning quarters become a smaller slice of the day, and mission cycles can stack multiple days in a row. One thing unique to this rate in its early years: the training calendar for RW is less mature than for ratings with decades of fleet integration. Commands may still be building their own internal qualification standards, PMS procedures, and watchbill structures for unmanned systems employment. That means the weekly schedule may not be as predictable as it would be in HM or IT, where the LPO can brief the week Monday morning off a template refined over twenty years. As an RWSN, expect the plan to change and document what actually happened — the log is your record when the schedule shifts. Physically, unmanned systems operations vary from bench-and-keyboard maintenance to deck evolutions that involve handling hundred-pound systems in sea state conditions. A week that includes a UUV recovery in chop is a physically demanding week, regardless of what the rating title sounds like. Stay ahead of your PRT cycle.

Key Skills — How to Drill Each

  1. 01
    Conduct pre-launch and post-recovery inspections on the unmanned systems the command operates — follow the approved checklist without improvising, every time.
    Get a physical copy of the system's pre-launch checklist and read it cover to cover before you run it for the first time — not just the section your trainer walked you through. Understand what each check item is actually verifying: propulsion health, sensor status, battery state, communication link establishment, GPS fix quality, tether or umbilical integrity, payload configuration. The RWSN who knows why each box exists catches the borderline fault the one who just checks boxes misses. Time yourself. A good senior operator can complete the pre-launch inspection on the command's primary system in a predictable window; the LCPO knows how long it takes and will notice when it's done too fast.
  2. 02
    Operate the mission control station or operator console on the command's UxV under direct supervision of a senior RW or qualified watch officer.
    Use every supervised evolution to degrade your dependence on verbal guidance. Before the evolution, brief the senior operator on what you plan to do at each phase — launch, transit, mission, recovery, emergency procedures. Ask what anomalies you should be watching for. After the evolution, debrief without prompting: what happened, what did you decide, what would you do differently. The RWSN who debriefs himself without being asked is the RWSN the senior operator trusts to run the next evolution without standing over his shoulder.
  3. 03
    Document mission logs, maintenance actions, and discrepancy reports cleanly — the log is the system's history and the LPO's first stop when something breaks.
    Write every log entry as if the JAG investigator is going to read it in six months — because on a weapons-capable or safety-critical system, they might. Time, action, result, signature. No abbreviations that aren't in the command's standard abbreviation list. No erasing or overwriting — annotated corrections only. If the discrepancy is ambiguous, err toward more detail, not less. The LCPO who can read your log and reconstruct what happened without calling you at 0200 will trust you with the next shift alone.
  4. 04
    Apply DoD Directive 3000.09 safety protocols and human-in-the-loop control disciplines as taught in the schoolhouse.
    Read the actual directive — not the schoolhouse summary — before you check aboard your first command. Know the definitions: autonomous weapons system, semi-autonomous weapons system, supervised autonomy, what 'human judgment' means in each tier. When you are in a mission brief and the authorization level being discussed seems to exceed what you were trained on, ask the question — not accusatorially, but specifically: 'Is this evolution authorized under [autonomy tier]?' A junior sailor who asks the right safety question at the right time is the sailor the senior operator praises at the debrief. The one who stays quiet to avoid friction is the sailor named in the incident report.
  5. 05
    Conduct basic field maintenance at the operator level: battery changes, sensor cleaning, propulsor checks, tether inspections.
    Own a copy of the platform maintenance manual and read the operator-level maintenance section before your LPO assigns you a PMS card. Understand the sequence: the maintenance that comes first is the maintenance that uncovers the fault the following maintenance step would have missed. Treat battery handling as its own discipline — LiPo and lithium-ion packs on unmanned platforms carry real thermal-runaway risk; the charging procedures, storage temperature requirements, and inspection criteria in the operator manual are not conservative recommendations.

Manuals & References — What Chapters Matter

  • DoD Directive 3000.09 — Autonomous Weapons Systems
    The governing DoD policy on human-operator control requirements for autonomous weapons. Read the full text, not just a summary — the definitions section is where the legal and operational line between authorized and unauthorized autonomy levels lives. This is the document that determines whether a mission is conducted within policy or becomes an investigation, and at the RWSN level you need to know it well enough to recognize a boundary when you see one.
  • NTTP 3-20.8 (USV employment) and associated NTTP publications for unmanned systems
    The Navy's tactical doctrinal framework for unmanned surface vehicle employment; verify the current edition from the Navy Doctrine Library before quoting. The NTTP series for unmanned systems is the document the section officer uses to plan mission profiles, and the RWSN who knows what the NTTP says about launch-and-recovery sea state limits, communication protocol requirements, and mission abort criteria is the RWSN who can contribute something real to the pre-mission brief instead of just executing.
  • Platform-specific operators manual for the unmanned system the command fields
    This is your actual technical bible — more specific and more actionable than the NTTP for day-to-day operation and maintenance. Know which chapter governs pre-launch inspection, which governs emergency procedures, and which governs operator-level maintenance. The technical representative and the LCPO will test you from this document at qualification.
  • NAVPERS 18068 series + current NEC source-rating NAVADMIN for the RW rating
    The NEC catalog for the RW rating is still being formally developed as of early 2025 — the source-rating NAVADMIN is updated as new pipeline positions are established. Pull the current version from MyNavyHR before any career counselor conversation; the NEC your recruiter or your buddy described may already have a different designator or a different pipeline requirement.
  • SECNAVINST 5239 series — DoN Cybersecurity / IA Program
    RW platforms have embedded software, communication links, and C2 interfaces that create cyber attack surface. The SECNAVINST 5239 series is the policy umbrella governing cybersecurity requirements for those systems. At RWSN level you need to know enough to handle classified systems properly, avoid unauthorized media connections to mission systems, and pass your annual cybersecurity awareness training without looking like you did not read it.

Standards — How to Hit Each

  • All PQS line items signed off on the LCPO's timeline — the rate is new enough that the PQS package may be freshly written.
    Get the current PQS package from the LCPO on day one and build a study calendar off the completion timeline, not the deadline. Work two line items ahead of where the LCPO expects you to be. When a line item requires a signature from a subject-matter expert you haven't met yet, make the introduction and schedule the evaluation yourself — do not wait for the LPO to arrange it. The RWSN who drives his own PQS completion is the RWSN who checks out of the cherry phase first.
  • Operator qualification on the specific unmanned systems the command fields, signed by the appropriate certifying authority.
    Ask the certifying authority early what the qualification standard looks like — what they will ask, what they will watch during the practical evaluation, and what the most common failure points are. Practice the emergency procedures cold: without notes, without verbal prompting, under time pressure. The qualification board is not interested in whether you understand the procedures conceptually; they are checking whether you can execute them when the system is doing something unexpected.
  • PRT Good Low or higher; BCA in standard.
    Train specifically for the events the Navy PRT measures — 1.5-mile run (or shuttle run), curl-ups or plank, push-ups — on a quarterly basis, not as a sprint to the test window. The launch-and-recovery operations and field environments this rating works in also require general functional fitness; incorporate loaded carries and grip-strength work if the platform involves heavy unmanned system handling. Know your PRT cycle schedule at the command and put the test date in your calendar six months out.

Technical Mistakes — Concrete Consequences

  • Improvising a maintenance step or skipping a pre-launch checklist item.
    The system that bypasses a pre-launch check is the system that surfaces a fault mid-mission — and 'we were in a hurry' is not a defensible entry in the post-mission safety investigation. At RWSN level, the log under your name is the log the LCPO reads first when the mission controller asks what happened to the system during yesterday's evolution.
  • Operating an unmanned system at an autonomy level you have not been authorized for.
    DoD Directive 3000.09 is a hard policy and legal line. An unauthorized autonomy-level activation opens a command safety investigation regardless of outcome, and your name appears on the first page of the report. The investigation is not contained to your section — it goes to the TYCOM and, on a weapons-capable system, potentially to DoD-level oversight. The Sailor whose name is on the log for an unauthorized activation does not recover from that in the rate.
  • Logging a mission action incompletely or overwriting an error instead of annotating.
    On a safety-critical or weapons-capable system, the maintenance log is a federal record. An overwritten or incomplete entry is at minimum an administrative finding at the next TYCOM inspection, and at maximum a records-integrity issue under the UCMJ. The correct action when you make an error in a log is a single line through the error, a brief annotation ('entered in error'), your initials, and the correct entry — not an erasure.
  • Letting a LiPo or lithium-ion battery charge cycle run unattended past the authorized monitoring interval.
    Thermal runaway on an improperly monitored battery pack in an enclosed compartment is a shipboard fire. The RWSN whose name is on the charging log as the responsible operator is named in the damage-control investigation. The battery charging procedures in the platform's operator manual are written around real failure-mode data — they are not conservative estimates.

Career Decisions at This Rank

  • First re-enlistment: re-up for the NEC pipeline vs. ETS and use civilian robotics / autonomous systems skills in the defense industry.
    The timing of this decision in the RW rating matters more than in older rates because the NEC pipeline is still being formalized. The sailors who re-enlist and go through the early NEC pipeline training become the technical depth the rate depends on; they also carry more risk if the NEC curriculum is still being refined. Before you sign, pull the current NEC source-rating NAVADMIN, talk to an RW1 or RW2 who has been through the current pipeline, and understand what billets the NEC actually opens. On the ETS side, the defense industry demand for autonomous systems expertise is real and growing — but the junior enlisted experience with a new Navy rate is less portable at 4 years than it is at 8-10 with advanced qualifications and a Chief packet. The sailors who ETS earliest from this rating are trading depth for optionality.
  • NSW support track: pursue the Naval Special Warfare maritime unmanned systems qualification track vs. staying blue-water fleet.
    NSW-adjacent billets for RW are among the most operationally intense seats the rate will have in the near term. If the billet structure evolves as the autonomous systems program matures, the NSW-support RW is likely to see the rate's most sophisticated employment scenarios early. The selection pathway (verify with current NAVADMIN; the formal process was still developing as of early 2025) involves operator qualification, fitness and clearance standards that exceed the baseline PRT, and a command endorsement that requires you to have been a known performer. Do not pursue this track to look good on paper — pursue it if you want the hardest, most demanding seat the rate currently has.
  • Reclass vs. staying RW: if the rate's advancement profile narrows or the NEC pipeline does not materialize as expected.
    The RW rating was established in February 2024 and the first advancement data is just starting to accumulate. If by your third or fourth year the advancement picture looks unfavorable — small selection quotas, NEC pipeline slots that haven't materialized, billets that haven't been established — the reclass conversation with your career counselor is legitimate. The skills from the RW pipeline (autonomous systems operation, UxV maintenance, DoD Directive 3000.09 familiarity) are genuinely portable to IT, CWT, EOD, and other technically demanding rates. But make this decision with data from the current NAVADMIN cycle, not from what someone heard second-hand.

How the Seat Varies by Unit Type

  • Surface combatant (DDG, LCS, LPD) integrating USV / UUV capabilities
    The majority of early RW billets are on surface ships integrating unmanned vehicles into the ship's warfare mission. The RW on a DDG or LCS works within the ship's operational schedule — which means the unmanned systems mission integrates into the normal underway workload. Launch and recovery in open-ocean sea states is physically demanding and operationally constrained. The wardroom's familiarity with unmanned warfare employment varies widely; you may spend real time educating senior officers on what the systems can and cannot do.
  • Mine Countermeasures (MCM) command
    MCM RWs are among the most operationally relevant seats in the early rate because autonomous systems have been central to mine warfare for longer than the RW rating has existed. The MCM community has a body of doctrine and experience with unmanned clearance systems that is more mature than in some other mission areas. The pace is different from a surface combatant — MCM operations are methodical, mission-specific, and highly dependent on accurate sensor data interpretation. The RW2 who can read sonar and AUV sensor data fluently is a different kind of asset than the one who can launch and recover a USV on a DDG deck.
  • Naval Special Warfare maritime support element
    NSW-support RW billets are the highest-intensity seats the rate has in its early years. The operational pace, the fitness standard, the operational security requirements, and the autonomy of action expected from the operator are all higher than in a standard fleet billet. The unmanned systems employed in NSW support may be more sophisticated and more capability-sensitive than what most RW personnel will work with in the fleet. Selection is competitive; expect a more demanding physical and security-clearance baseline than the minimum PRT standard.
  • Training command / A-school support staff
    As the rate's pipeline matures, some senior RW petty officers will end up in training billets — as instructors or curriculum developers at the schoolhouse. This is a rate-shaping billet in a way that is rarely true for an established rating: the RW who writes the next generation of PQS standards or instructional materials is directly shaping what the rate looks like for the next cohort. Not for everyone, but for the senior RW who wants to shape the institution rather than just operate within it.

What Good Looks Like at This Rank

The good RWSN in 2025-2026 is not the sailor who has the most impressive social media content about autonomous warfare. That sailor is a liability. The good RWSN is the one whose log entries the LPO reads without rewriting, whose pre-launch checklists come back complete every time, and who asks the hard question during the mission brief — 'Is this autonomy level authorized under the standing orders?' — because he read the directive, not just the summary. In a rate this young, good performance is highly visible because there are fewer people to compare against. The RWSN who owns his PQS, keeps his maintenance records clean, and stays current on the platform operator's manual is not blending into a crowd — he is standing out in a small formation where the LPO knows every name. Use that visibility deliberately. Show up early to evolutions. Debrief without being asked. Ask the LCPO where the NEC pipeline is heading. The thing the schoolhouse cannot fully prepare you for is the reality of being a subject-matter expert in a command where the people senior to you by paygrade may not have been through your pipeline. That is an unusual dynamic. Handle it with humility and precision: defer on operational judgment and employment decisions to the people who have mission experience; contribute technical depth from the platform operator's manual and the safety-of-use framework when those questions come up. The RWSN who positions himself as 'smarter than the chief because I went to A-school' is gone before his first re-enlistment. The RWSN who uses what the schoolhouse taught him to make the section better is the one the chief pushes for the first advanced NEC slot.

Preview — The Next Rank

RW3 is where the cherry phase ends and the real operator identity begins. The RWSN who spent the first year asking 'what do I do?' becomes the RW3 who is asked to tell the incoming RWSN what to do — usually before feeling fully ready for it. That transition is what the RW3 tier is about. The NEC pipeline decision gets real at RW3. The advanced operator track, the maintenance technician track, the NSW support qualification, and the emerging specialized operator roles are the doors the rate has available; which one you walk through in the next 18-24 months shapes the next decade. Pull the current source-rating NAVADMIN before any of those conversations with the career counselor, because what was true last year may have changed. The NWAE for RW2 also becomes a real study load at RW3. The BIB for the rate is newer than most — verify the current cycle's bibliography from MyNavyHR and start the study log before the LCPO asks. The sailor who shows up to the NWAE cycle on six weeks of study is the sailor who watches the RW2 slate from the bench.
FAQ

RW E1-E3 — Frequently Asked Questions

Q01What does a E1-E3 RW (Robotics Warfare Specialist) actually do?
You are coming out of a pipeline that is still being refined: A-school at a Naval training command (verify the current course location and length before quoting — the curriculum and schoolhouse were still being formally established as of early 2025), covering foundational unmanned systems operation, robotics theory, autonomous vehicle maintenance, and the DoD Directive 3000.09 rules-of-engagement framework for autonomous weapons.
Q02What's the most important thing to know as a E1-E3 RW?
You are entering a rating with less than two years of institutional history.
Q03What does a typical day look like for a E1-E3 RW?
Time-blocked day at the E1-E3 RW rank tier: 0530–0620 PT formation — unit PT schedule (varies by command; surface ships run PT on the pier or in the ship's gym; shore commands run on the track). As a junior RW you run with the section, 0630–0700 Rack time or personal hygiene; muster at 0700 in uniform of the day, 0700–0730 Division quarters — all hands formation, accountability, safety word of the day, plan of the day read. The LPO or LCPO addresses the section, 0730–0800 System status check: walk to the unmanned systems spaces or vehicle handling area,…
Q04What mistakes get E1-E3 RW soldiers fired or relieved?
Unauthorized autonomy-level activation — operating an unmanned system in an autonomy mode not authorized by the chain of command. DoD Directive 3000.09 is a hard legal and policy line; a single unauthorized activation opens a command investigation regardless of outcome; NJP, DUI, or drug pop — closes every advanced NEC pipeline, NSW support qualification, and commissioning program window in the rate; Falsifying or retroactively altering a maintenance log or safety-of-use record.…
Q05What career decisions matter most at the E1-E3 RW rank tier?
First re-enlistment: re-up for the NEC pipeline vs. ETS and use civilian robotics / autonomous systems skills in the defense industry — The timing of this decision in the RW rating matters more than in older rates because the NEC pipeline is still being formalized. The sailors who re-enlist and go through the early NEC pipeline training become the technical depth the rate depends on; they also carry more risk if the NEC curriculum is still being refined. Before you sign, pull the current NEC source-rating NAVADMIN, talk to an RW1 or RW2 who has been through the current pipeline,…
Q06What's next after E1-E3 for a RW (Robotics Warfare Specialist) in the Navy?
RW3 is where the cherry phase ends and the real operator identity begins.
Q07What manuals and regulations does a E1-E3 RW need to know cold?
DoD Directive 3000.09 — Autonomous Weapons Systems (the governing DoD policy on human-operator control requirements; every RW learns this before they touch an armed UxV).; OPNAVINST 3500 series — Navy training policy and readiness standards (the umbrella the rating's PQS and watchbill qualifications inherit from; pull the current version).; NTTP 3-20.8 (or current equivalent) — Unmanned Surface Vehicles and associated NTTP publications for unmanned systems employment;…

This playbook has no tips yet. Be the first to share what you know.

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards