Unmanned Aerial Vehicle (UAV) Mechanic

0530 muster, accountability, mission brief. 0600 preflight with your crew — you're walking the aircraft and supervising simultaneously. 0800 launch. Post-launch, you're in the hangar on phase inspection or troubleshooting whatever came up in the preflight that was deferred. Midday you're reviewing logbook entries from your junior Marines, correcting write-up language, and making sure parts requests are in the system. Afternoon flight recovery, postflight supervision, servicing. Before end of day you're briefing the maintenance chief on your aircraft's status and any outstanding discrepancies. Det adds field hygiene, equipment security, and whatever logistics the OIC needs done.

Monday morning: maintenance plan review, assign tasks to your crew, verify tool accountability. Daily: flight support around the schedule, supervised maintenance tasks, logbook audits before close of business. Mid-week: any required CDI refresher training, safety briefs, technical directive compliance checks. Friday: equipment status reports, ground support equipment servicing, preparation for weekend skeleton crew. In surge operations, this schedule collapses into 'whatever the aircraft needs before the next launch window.' Know which days are high-density flying and prepare accordingly.

GCS troubleshooting becomes central at this tier — you need to understand the full datalink architecture, not just the operator interface. Payload systems (EO/IR) maintenance and calibration procedures matter now because you're the one training junior Marines on them. Structural inspection criteria needs to be in your head, not just on a card — you should be able to walk a junior Marine through an impact damage assessment without looking it up. Fuel system contamination investigation: knowing how to take a sample, read it correctly, and make the right call on whether to fly or drain is a critical skill that looks simple and isn't.

COMNAVAIRFORINST 4790.2 Section IV covers CDI responsibilities — read it until it's reflex, not reference. Your squadron's QA SOP has local amplifying guidance that matters in practice more than the parent instruction. Platform safety-of-flight messages (SOF/SOI) archive in your maintenance department — pull the last two years' worth and understand what has caused problems on your platform. TM -12 for operator and crew chief procedures on your aircraft. For the Blackjack specifically, the shipboard handling procedures supplement is separate from the garrison TM and contains constraints that will bite you if you don't know them.

As a CDI, your sign-off means the work is done and correct. That's not a formality — it's a legal document. The standard is: if you didn't personally verify the measurement or configuration, you don't sign it. A CDI who signs off work they didn't inspect is a failed CDI. Turnaround time standard at Cpl: you should be able to take a Shadow from postflight to preflight-ready in under 4 hours for a standard servicing and inspection. Know your squadron's aircraft availability standard and know whether your aircraft are contributing to it or dragging it down.

Incorrectly configuring GCS waypoints or nav parameters before a mission and not catching it in preflight — link loss and aircraft departure are downstream consequences. Fuel contamination misidentification: calling a water-contaminated sample clean because the color 'looked okay' without proper testing. Rotor hub assembly errors on Shadow that produce a vibration signature that doesn't trip a fault code but causes abnormal wear — only caught by a thorough postflight physical inspection. Over-torquing composite fasteners because a junior Marine was rushing and you were supervising from too far away.

The Sgt board is the next hard gate. What matters: CDI, a clear maintenance record (no NJPs or sustained quality escapes), and visible leadership on a det or MEU. If you're at a garrison-only billet and have no field time, start asking questions about upcoming det taskings. The decision between staying in aviation and cross-training is also live at this rank — if you're genuinely engaged with the technical challenge, this MOS rewards deep expertise. If you're just showing up, cross-training to a different MOS before you hit Sgt may be a better path than grinding through a promotion board with a mediocre record.

VMU-1 Cpls are likely touching Shadow and Blackjack both, with high flying day counts. VMU-2 focuses more on Blackjack shipboard integration; if you're a Cpl at VMU-2, you're more likely to spend time on an LPD or LHA doing confined-space maintenance. VMU-3 in Hawaii has INDOPACOM support requirements that mean more austere det operations with longer communications delays from home squadron. MEU det as a Cpl is the most independent you'll ever be — the OIC trusts the senior mechanic completely, and if you're that person, you're running maintenance for the entire det.

An excellent Cpl runs a maintenance crew where the junior Marines know exactly what they're supposed to do, check their own work before calling for CDI, and write logbook entries that need zero correction. When the schedule slips and everyone is rushing, the outstanding Cpl slows the team down anyway and eats the timeline rather than compromise the inspection. In a det, when the OIC asks for aircraft status, the excellent Cpl can give an accurate answer about every discrepancy, its maintenance action code, and estimated resolution — without looking at a clipboard.

Sergeant means you are a bona fide NCO, responsible not just for maintenance quality but for the discipline, development, and welfare of junior Marines. The technical foundation you built at E1-E3 and Cpl now has to support leadership that you didn't need before. You'll be running pre-deployment readiness inspections, writing evaluations, and standing duty as the senior enlisted in situations where your OIC is not present. The Marines who make the jump from good mechanic to good Sergeant are the ones who figured out at Cpl that the job is about developing people, not just fixing aircraft.