Skip to main content
HonestMOS
InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.
Back to 7315 Unmanned Aircraft System (UAS) Officer — overview, pay, training, civilian translation, reviews
7315O1-O2

Unmanned Aircraft System (UAS) Officer

O-1 to O-2 (Junior Officer) · Marines

HEADS UP

You are a UAS Officer in a Marine Corps that is actively figuring out what a UAS Officer is. The RQ-21A Blackjack has replaced legacy systems, the MQ-9A Reaper is now a Marine platform, and the doctrine for how to employ all of it is still being written by people senior to you who are also learning. This is a good time to be a 7315 because the community is shaping itself, and a bad time because nobody has a clean answer for what your career looks like in ten years.

The Honest MOS Read
The 7315 MOS is the Marine Corps' answer to a joint force that increasingly fights with, through, and dependent on unmanned aircraft systems. As a second or first lieutenant, you are either a platoon commander or a detachment OIC for a UAS element attached to a supported ground unit, which means you are responsible for the GCS operators, the mission planners, the link and communications architecture, and the integration of UAS ISR and targeting products into the supported unit's intelligence picture. You are not flying. You are leading the team that runs the systems, and the supported commander's first question will always be 'what can your aircraft see right now?' and the second will be 'how fast can you get me a grid?' The Ground Control Station is your primary work environment. The GCS integrates the control link, the payload feed (EO/IR and SAR depending on the platform), and the datalink architecture that distributes products to intelligence consumers. Understanding the GCS at the technical level — not as a black box but as a system with modes, failure points, and operating parameters — is a baseline requirement for a 7315 officer who wants to be credible to his NCOs and pilots. The lieutenants who try to manage UAS operations from a distance and let the operators handle the technical details are creating a capability gap that will surface during an operation. Mission planning is the other half of the job. UAS missions require route planning that accounts for airspace restrictions, line-of-sight requirements for the control link, weather effects on EO/IR and SAR payload performance, and coordination with the supported unit's scheme of maneuver and collection priorities. A poorly planned UAS mission puts the aircraft somewhere that cannot see what the supported commander needs to see, and the intelligence consumer will blame the aircraft when the problem was the planning. Link-16 and datalink coordination is where the junior 7315 officer earns or loses credibility in the joint environment. Distributing UAS-derived products — real-time video, FMV downlink, SIGINT tips, BDA imagery — to ground consumers, fires cells, and higher headquarters requires understanding which data links are available, which consumers have the receive capability, and how to manage the information flow so that the right picture gets to the right people without saturating the net. The lieutenant who treats datalink as 'someone else's problem' will find himself in an exercise where the ISR product cannot reach the fires cell because nobody built the architecture. Your immediate relationship with enlisted GCS operators is the most important leadership dynamic of the junior 7315 career. The experienced Staff Sergeant GCS operator knows more about the system than you do when you arrive. Acknowledge that reality, learn aggressively from them, and build a professional relationship where your tactical judgment and their technical expertise produce missions that work. The lieutenant who pretends to know more than his operators is the one whose operators route around him.
Career Arc
Months 0-6: UAS officer training pipeline — RQ-21A or MQ-9A GCS qualification, mission planning certification, link and datalink procedures. Months 6-18: Platoon or detachment OIC; first deployment with supported ground unit; ISR and targeting mission execution. Months 18-30: Senior platoon OIC or squadron assistant S-3; mission planning cell lead; detachment OIC for MEU or expeditionary deployment. Year 3: O-3 consideration; UAS-specific school completion; MAGTF integration qualification.
Common Screwups
Approving a mission route that takes the aircraft through restricted airspace because the mission planner didn't check the current airspace order — the UAS OIC who authorizes a mission without personally validating the airspace deconfliction has created a fratricide risk and an airspace violation that will be visible to everyone on the Link-16 picture. Allowing sensor operators to drive their own collection priorities instead of executing against the supported commander's requirements — the UAS that is looking at what the operators find interesting and not what the S-2 requested is burning flight hours without producing intelligence value. Ignoring GCS technical failures until they cascade — an intermittent control link issue that gets managed around rather than reported and repaired will become a lost aircraft during an operation.

A Day in the Life

0530: Pre-mission brief — target package review, airspace order check, weather assessment for payload performance, link architecture verification. 0630: Mission launch — GCS activation, launch authority brief, operator coordination. 0700-1200: Active mission execution — ISR collection against priority requirements, real-time coordination with S-2 and fires cell, sensor management, datalink product distribution. 1200: Mission handoff to relief crew or recovery sequence. 1300: Post-mission debrief — imagery exploitation review, fires cell coordination on targeting products, collection results against requirements. 1400: Next mission planning — route development, airspace deconfliction, consumer coordination. 1600: GCS maintenance coordination, equipment status review. 1700: Administrative close-out, operator log review.

Weekly Cadence

The UAS detachment runs on a mission-first schedule — the supported commander's ISR requirements drive the flight schedule and the flight schedule drives everything else. When operational, the week is a rotating mission cycle with pre-mission planning, execution, and post-mission exploitation stacked continuously. In garrison, the week balances mission-system currency (GCS qualification maintenance, mission planning exercises, link architecture training) with unit administration and individual professional development.

Key Skills — How to Drill Each

Plan and execute an ISR mission that provides the supported ground unit with full-motion video and targeting-quality imagery on a priority target — route planning, payload management, datalink coordination, and real-time adjustments to the collection plan when the tactical picture changes. Manage the GCS during a dynamic targeting sequence — coordinating the sensor operator, the fires cell, and the supported commander while the aircraft is providing terminal guidance-quality imagery against a time-sensitive target. Brief the supported battalion commander on UAS capabilities, limitations, and collection plan for the next 24-hour operational period — translating what the aircraft can and cannot do into language that informs the ground commander's maneuver planning.

Manuals & References — What Chapters Matter

MCO 3710.series — Marine Corps aviation regulatory guidance that governs UAS operations in the MAGTF context; understand the operational and safety requirements before your first mission. JP 3-30 — Command and Control of Joint Air Operations; UAS flights operate in the same airspace as manned aviation and the 7315 officer must understand how JFACC airspace management applies to his aircraft. MCWP 3-20.5 — Marine UAS operations doctrinal guidance; the framework for how UAS capabilities are integrated into MAGTF operations. STANAG 4671 and applicable UAS airworthiness publications — the interoperability standards that govern how Marine UAS operate alongside coalition partners.

Standards — How to Hit Each

GCS qualification on the assigned platform — unqualified officers do not run missions, and the qualification timeline is enforced by the squadron. Mission planning certification — the ability to produce an executable mission plan that passes safety review is a threshold requirement before independent mission authority. Airspace coordination proficiency — demonstrated ability to deconflict UAS routes with manned aviation, apply airspace restrictions, and brief the supported unit on limitations. Physical fitness standard is standard Marine officer — UAS units deploy expeditionarily and the detachment OIC is a deployed Marine, not a GCS jockey.

Technical Mistakes — Concrete Consequences

Committing the aircraft to a specific collection point without verifying that the control link geometry supports the GCS-to-aircraft distance at that route segment — the RQ-21A and MQ-9A have line-of-sight constraints on certain datalinks, and a planned collection orbit that puts the aircraft beyond effective control link range produces a lost contact event or a degraded feed exactly when the supported commander needs the picture. Attempting to push FMV via a datalink the receiving consumer does not have a configured terminal for — verifying receive capability before the mission, not after the aircraft is on station, is the mission planner's job. Managing a GCS technical anomaly by adjusting around the problem rather than declaring it and requesting maintenance — degraded systems that continue flying degrade further.

Career Decisions at This Rank

Joint UAS qualification: the 7315 officer who pursues qualification on additional platforms — gaining familiarity with the full Group 3-5 spectrum including RQ-21 and MQ-9 — is building the breadth that makes the MAG/Wing ISR staff billet competitive. Intelligence community relationship: the 7315 officer who actively builds relationships with the supported unit's S-2 cell and SIGINT elements, understanding what they need and how UAS can deliver it, is developing the intelligence-integration expertise that distinguishes the best 7315 officers from the ones who are just running platforms.

How the Seat Varies by Unit Type

VMU squadron: the home unit for 7315 officers, full-spectrum UAS operations in support of MAGTF ground operations. MEU/ARG deployment: expeditionary UAS operations from ship, austere basing, and compressed support relationships — high operational tempo in a small team with limited maintenance and logistics support. MAGTF ISR support: integrated ISR collection management, multi-INT coordination with SIGINT and HUMINT elements, full-spectrum intelligence support to the ground element.

What Good Looks Like at This Rank

The good junior 7315 is the one the supported battalion S-2 calls directly to update the collection plan because that officer has demonstrated the ability to translate intelligence requirements into executable UAS taskings without a translation layer. She knows the GCS status, the current mission, and the fuel state of every aircraft in her detachment without being asked. Her mission plans have clean airspace deconfliction and she has verified receive capability for every datalink product before the aircraft launches. When a target of opportunity appears on the feed, she can sequence from collection to targeting support in the time it takes the fires cell to build the call-for-fire — because she has rehearsed that sequence.

Preview — The Next Rank

At O-3, the transition is from detachment OIC to squadron operations officer or intelligence integration cell lead. The Captain is expected to manage the squadron's mission tasking, coordinate UAS support across multiple supported units, and begin contributing to the joint ISR architecture at the MAG and Wing level. The lieutenant who has built the GCS technical depth, the mission planning rigor, and the intelligence-community relationship at O-1 and O-2 is the one who walks into the O-3 billet without needing a remedial orientation.
FAQ

7315 O1-O2 — Frequently Asked Questions

Q01What does a O1-O2 7315 (Unmanned Aircraft System (UAS) Officer) actually do?
The 7315 MOS is the Marine Corps' answer to a joint force that increasingly fights with, through, and dependent on unmanned aircraft systems.
Q02What's the most important thing to know as a O1-O2 7315?
You are a UAS Officer in a Marine Corps that is actively figuring out what a UAS Officer is.
Q03What mistakes get O1-O2 7315 soldiers fired or relieved?
Approving a mission route that takes the aircraft through restricted airspace because the mission planner didn't check the current airspace order — the UAS OIC who authorizes a mission without personally validating the airspace deconfliction has created a fratricide risk and an airspace violation that will be visible to everyone on the Link-16 picture.…
Q04What's next after O1-O2 for a 7315 (Unmanned Aircraft System (UAS) Officer) in the Marines?
At O-3, the transition is from detachment OIC to squadron operations officer or intelligence integration cell lead.

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