Unmanned Aircraft System (UAS) Officer

You are a brand-new UAS officer learning to fly a box that looks like a science-fair project and kills real targets. The Marine Corps is transitioning this community to MQ-9A Reaper, so your training pipeline may shift under your feet.

You spend your first tour at a VMU squadron getting qualified on the RQ-21A Blackjack or, increasingly, the MQ-9A Reaper. Duty means long GCS shifts — 8 to 12 hours staring at sensor feeds, managing datalinks, deconflicting with manned aircraft, and writing post-mission intelligence products. You are the junior set of eyes on a sensor that commanders trust for targeting decisions, so the learning curve is steep and the consequence of sloppy scan technique is real. Expect substantial time in Link-16 and ROVER coordination, learning to talk to ground FACs, and doing BDA write-ups after every kinetic event.

• 01GCS operation — RQ-21A or MQ-9A systems, payload management.
• 02Link-16 and ROVER datalink coordination with supported units.
• 03ISR mission planning — collection management, sensor tasking.
• 04Air traffic deconfliction in congested airspace.
• 05Intelligence product writing — BDA, mission reports, FMV exploitation.

• —MCWP 3-20.8 — Unmanned Aircraft Systems Operations.
• —NAVMC 3500.107 — UAS Officer T&R Manual.
• —FAA COA procedures for UAS operations in NAS.

• —GCS qualification complete within 12 months of joining VMU — squadron readiness gate.
• —Maintain instrument currency and all T&R events per NAVMC 3500.107 quarterly review.
• —Post-mission intelligence products submitted within 2 hours of landing per squadron SOP.

• —Treating the GCS like a video game — complacency on sensor management leads to missed TTPs and degraded products for the JTAC.
• —Poor datalink hygiene — letting Link-16 track management slide means commanders lose SA on your bird's position.
• —Writing BDA products without consulting imagery analysts — solo assessments get called out in higher-echelon review.

An O2 who arrives at VMU-1 and grinds through RQ-21A qualification while simultaneously getting ahead on MQ-9A transition material — before the squadron is officially re-equipped — so that when the Reaper arrives she is the first qualified crew member and her CO trusts her with the first operational mission. That's the play.

You are a proven UAS aircraft commander and the squadron's go-to for hard missions — deliberate targeting, SIGINT support, and MEF-level ISR tasking. This is also the tier where you decide whether UAS is a career or a waypoint.

As a captain you are an aircraft commander who owns the pre-mission planning cycle, leads two-ship sensor coverage packages, and interfaces directly with ANGLICO, MAGTF intelligence, and MEF ISR cells on collection requirements. MQ-9A transition means you may be both the last qualified Blackjack AC and the first Reaper-qualified crew in your squadron — document everything. You also run the flight schedule, mentor your junior officers, and begin writing the T&R events that will define how the next generation of VMU pilots gets trained. Deployment rotations to CENTCOM or PACOM put you in real collection environments where the products you write feed EXORD-level targeting packages.

• 01Aircraft commander authority — crew coordination, GCS crew standards enforcement.
• 02Deliberate targeting cycle — D3A, JPME targeting principles applied to UAS.
• 03Collection management coordination with MEF G-2 and theater ISR cells.
• 04SIGINT mission support — coordination with NSA/USMC SIGINT billets.
• 05Mentorship and T&R event instruction for O1-O2 peers.

• —JP 3-60 — Joint Targeting, Chapter 3 (Decide phase for UAS employment).
• —MCTP 3-20B — Aviation Ground Support.
• —NAVMC 3500.107 — UAS Officer T&R Manual, AC-level events.

• —Aircraft commander designation board completed; recommendation endorsed by CO.
• —Minimum 300 mishap-free flight hours per COMNAVAIRFORINST 3710 requirements at AC upgrade.
• —Deployment readiness — all T&R events green 60 days prior to scheduled deployment.

• —Failing to document transition lessons learned during RQ-21A-to-MQ-9A crossover — institutional knowledge evaporates and the next crew starts from zero.
• —Letting collection managers task the sensor without pushback — if the requirement doesn't support the ground commander's PIR, say so before launch, not after.
• —Skipping pre-brief coordination with supported JTAC — surprises during a CAS stack are how friendly fires happen.

A captain who deploys to CENTCOM with VMU-3, earns his SIGINT mission qualification in-theater, and comes home with a white paper on MQ-9A collection manager integration that the MAGTF ISR cell actually uses to revise its TASKORD template. His CO submits it to MAWTS-1 for inclusion in the next UAS officer course curriculum.

You are a major who either runs the operations or intel side of a VMU squadron or gets pulled into a MAG/MAW staff billet that shapes how the entire wing employs unmanned systems. The community is small and everyone knows everyone.

At O4 you are the squadron S-3 (operations officer) or XO, responsible for the flight schedule, readiness reporting, and the daily production of every ISR mission the squadron flies. You own the relationship with the wing's ISR coordination cell and the MEF G-2, and you personally brief the CO on collection posture and platform availability. You're also heavily involved in MQ-9A FMC transition planning — coordinating with NAVAIR, writing CONOPS, and liaising with the Air Force's MQ-9 schoolhouse at Holloman. If you drew a MAG staff billet instead, you're writing the ISR annex to the MAGTF order and educating ground commanders on what UAS can and cannot do.

• 01Squadron operations management — flight scheduling, readiness reporting, T&R oversight.
• 02ISR coordination with MEF and theater joint ISR cells.
• 03MQ-9A transition planning — NAVAIR interface, CONOPS development.
• 04Staff officer skills — ISR annex writing, MAGTF order integration.
• 05Budget and resource management for aviation unit operations.

• —MCWP 3-20.8 — Unmanned Aircraft Systems Operations, Chapter 4 (MAGTF UAS).
• —OPNAVINST 3710.7 — Naval Aviation Safety Program (mishap reporting chain).
• —DoD UAS Roadmap — programmatic context for MQ-9A fleet transition.

• —Squadron ISR mission capable rate reported monthly to MAG — O4 ops officer owns this number.
• —NAVAIR transition milestone compliance — MQ-9A IOC/FOC dates driven by readiness data you provide.
• —Zero preventable Class A mishaps — the major owns the safety program in the CO's absence.

• —Over-promising ISR coverage to the MEF without accounting for maintenance cycles — unrealistic collection commitments erode commander trust faster than canceled missions.
• —Delegating MQ-9A transition documentation to a contractor without officer oversight — the Air Force schoolhouse will send you home if your crew standards packet is wrong.
• —Losing currency personally while running the desk — a major who can't fly is a major who can't lead.

A major who serves as VMU-2's S-3 during the first MQ-9A deployment, keeps the squadron at 85% FMC despite a new platform, writes a lessons-learned report that HQMC Aviation uses to revise the transition timeline for VMU-1, and gets screened for XO on the strength of that document alone.

You command a VMU squadron or hold a senior ISR billet at MAW or HQMC. The community is so small that a successful O5 tour here is genuinely visible to the Commandant's staff. The pressure is real.

As a lieutenant colonel you are commanding VMU-1, VMU-2, or VMU-3 — or you're the senior UAS officer at a MAW or at HQMC Aviation. Command means you own the people, the planes, the readiness, and the safety record. You personally engage with theater combatant commanders on ISR requirements when your squadron deploys. You're also managing the community's future: writing PPBEs, arguing for MQ-9A procurement slots, and managing the career development of every junior officer in the pipeline. At HQMC your job is to translate what the operating forces need into acquisition language that NAVAIR and the Hill can fund.

• 01Unit command — personnel accountability, UCMJ authority, safety program ownership.
• 02Theater ISR advocacy — direct engagement with CCMD J2/J3 on collection requirements.
• 03Acquisition interface — NAVAIR program office coordination, JCIDS documentation.
• 04Community career management — mentorship pipeline, O3-O4 screening input.
• 05Congressional budget justification — PPBE cycle participation for UAS procurement.

• —MCO 3500.27 — Operational Risk Management (commander's safety accountability).
• —JCIDS Manual — capability requirements documentation for UAS systems.
• —USMC Aviation Plan — programmatic roadmap for unmanned systems investment.

• —Zero preventable Class A mishaps during command tour — the CO is the named responsible officer.
• —Deployment readiness certification submitted to MAG 90 days prior — the O5 signs it.
• —MQ-9A FOC milestone achieved on schedule — command-level accountability to CMC Aviation.

• —Treating the command tour as a check-in-the-box rather than a genuine effort to shape the community — the UAS officer community is small enough that a weak CO tour echoes for a decade.
• —Letting NAVAIR set the transition timeline without operational pushback — the program office doesn't know what your crews actually need to reach FOC.
• —Micromanaging the S-3 on the flight schedule — that's the major's job; your job is resourcing and shielding the squadron from external demands.

A lieutenant colonel who commands VMU-3, deploys the squadron to INDOPACOM in direct support of a MEF exercise, achieves the first operational MQ-9A kinetic employment in Marine Corps history, and returns with a classified after-action that shapes the next decade of USMC UAS doctrine. Screened for colonel. Gets called to testify to HASC.

You are a colonel running a MAG or serving as the senior UAS/ISR officer at an aviation wing, HQMC, or a joint command. The community that trained you is now looking to you to define what it becomes.

At O6 you command a Marine Aircraft Group or serve as the Director of ISR or UAS programs at HQMC Aviation or a numbered Marine aircraft wing. As a MAG commander you own the readiness and safety of multiple squadrons and multiple platform types. Your UAS background makes you the wing's expert on ISR integration, and combatant commanders will pull you into theater-level planning. At HQMC you write the programmatic documents that determine whether the Marine Corps buys more MQ-9As, pursues a next-generation UAS, or divests entirely. You engage the Hill, SECNAV staff, and OSD on aviation priorities.

• 01Group command — multi-squadron leadership, readiness across platform types.
• 02Theater-level ISR integration — CCMD direct engagement on collection architecture.
• 03PPBE and POM advocacy — aviation investment priorities at the O6 level.
• 04Joint and interagency coordination — NSA, DIA, USAF ISR community.
• 05Strategic communication — Congressional testimony, HASC/SASC engagement.

• —USMC Force Design 2030 — UAS role in distributed MAGTF operations.
• —Joint Publication 2-01.3 — JIPOE (ISR integration into joint intelligence).
• —DoD UAS Integration Roadmap — programmatic context for O6-level advocacy.

• —Group readiness rates reported to wing — the O6 MAG commander owns aggregate FMC across all subordinate squadrons.
• —POM submission on time with defensible requirements documentation — HQMC Aviation holds this standard.
• —Zero safety culture failures — a MAG commander whose subordinate units have a pattern of preventable mishaps will not screen for general officer.

• —Letting joint partners define what Marine UAS can do — if you don't advocate for your community's unique MAGTF integration value, the Air Force will absorb the mission and the Marine Corps will lose the platform.
• —Failing to develop the next generation of O4-O5 community leaders during your O6 tour — the UAS community is too small to have weak senior officers.
• —Treating the MAG command tour as a paper-shuffling exercise — the squadrons need a commander who understands their problems at the operator level.

A colonel who commands MAG-39, shepherds the last RQ-21A squadron through retirement while certifying the first fully-MQ-9A VMU squadron to FOC, writes the USMC's formal recommendation to OSD on next-generation UAS requirements, and screens for brigadier general on the strength of both operational and programmatic credibility.

You are a general officer whose UAS background is now one input into a much larger portfolio of aviation and MAGTF responsibilities. The community you came from is small — your presence at this level is genuinely consequential for its future.

At O7 and above you serve as an assistant wing commander, wing commander, Deputy Commandant for Aviation, or in joint billets at CENTCOM, INDOPACOM, or the Joint Staff. Your UAS/ISR background gives you uncommon credibility on the joint ISR architecture and positions you to advocate for unmanned systems in forums where most generals have a fighter or rotary wing background. You are making decisions about force structure, acquisition strategy, and doctrine that will determine what the Marine Corps's unmanned aviation looks like in 2035 and beyond. At three and four stars you are part of the Commandant's team shaping the future of the entire MAGTF.

• 01Wing and MAGTF aviation command — multi-domain force employment.
• 02Joint ISR architecture — senior engagement with CCMD and NRO/NSA on collection priorities.
• 03Force design advocacy — USMC UAS future at SecDef/CJCS level.
• 04Senior leader development — shaping the O6-O7 pipeline for aviation.
• 05Congressional and interagency relations — HASC, SASC, OSD, State Department.

• —USMC Force Design 2030 and 2045 — the strategic framework you are executing.
• —National Defense Authorization Act (annual) — statutory authority for aviation programs you champion.
• —Joint Concept for Integrated Campaigning — joint doctrine context for MAGTF ISR employment.

• —Wing FMC rates and mishap rates are the general's accountability — even at O8 these numbers follow your career.
• —POM decisions you champion must survive OSD scrutiny — requirements must be operationally credible.
• —Subordinate general officers and colonels you develop define your legacy — talent management is the O7+ job.

• —Becoming a generalist too fast and losing UAS/ISR credibility — your comparative advantage in joint forums is that you actually flew the sensor; don't let it atrophy.
• —Allowing fighter community inertia to dictate UAS resource allocation at the wing level — unmanned systems are not a consolation prize for pilots who couldn't get Hornets.
• —Failing to actively mentor the O5-O6 pipeline — a general who doesn't sponsor the next generation of community leaders leaves the UAS community without senior advocates when he retires.

A brigadier general who serves as the Assistant Wing Commander at 3rd MAW, deploys to INDOPACOM as the theater ISR coordinator during a major joint exercise, and returns to write the authoritative USMC recommendation on MQ-Next that shapes the 2031 POM — then screens for major general on the strength of both operational and acquisition credibility. The community finally has a two-star.