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 5939 Aviation Communication Systems Technician — overview, pay, training, civilian translation, reviews
5939E1-E3

Aviation Communication Systems Technician

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

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

The COMSEC procedures feel like bureaucracy until the day you are standing in front of the Communications Security Officer explaining why you touched the crypto fill device without a witness. That day ends careers. The TPI log is not paperwork — it is the only thing between you and a UCMJ action that has nothing to do with your technical competence.

The Honest MOS Read
You are a junior 5939 bench tech in a Marine Aviation Logistics Squadron avionics shop or a squadron communications/avionics division. The mission brief will tell you this is an aviation communications job. The hangar will tell you this is an LRU-swapping, BIT-running, logbook-annotating job at the bottom of a supervision chain that trusts nothing until you prove it deserves to be trusted. Your first months are Remove-Replace-BIT. You pull a UHF/VHF radio set — AN/ARC-210 or a platform-specific variant — from an F/A-18 or an MV-22 or a CH-53, you place connector caps on every open RF connector before the box leaves your hand, you annotate a red-X discrepancy in GCSS-MC that accurately describes what you found and what you did, and you call for the CDI. The CDI is not there to praise your work. The CDI is there to catch the thing you missed. Until the CDI does not find anything worth correcting, you are on probation. Every junior tech is on probation. The MALS does not have a ceremonial version of this job. The IFF transponder — AN/APX-111 or AN/APX-119 depending on the platform — is the system that gets people killed when it is wrong. An IFF fault that reaches the cockpit because someone skipped a connector inspection, installed the wrong variant, or signed off a BIT that cleared a known intermittent fault is an aircraft that flies into a contested airspace looking like a threat to every other friendly platform in the sector. The quality assurance chief will explain this to you once, briefly, and without emotion. After that she expects you to carry it. COMSEC is the other load-bearing wall. The crypto fill devices — KY-series equipment, HAVEQUICK fill loaders, platform-specific variants — live in a safe, require a Two-Person Integrity procedure to touch, and generate an audit trail that the Communications Security Officer samples at will. You do not open the crypto safe alone. You do not key-load a radio alone. You do not sign the TPI log without a witness present and you do not let a witness sign a TPI log entry for a procedure they did not witness. COMSEC violations go up the chain on the same day they occur or they are discovered in an audit, and discovered-in-audit is worse in every way that matters. The 5939 tech who treats COMSEC procedures as bureaucracy is the 5939 tech who ends up explaining themselves to a JAG officer. The avionics shop schedule runs on the flight schedule. When the first launch is at 0700, your preflight-maintenance window is before 0700, and the pilot is not interested in why the IFF is still on the bench. You will work nights, you will work weekends, and you will work the day before a holiday when the operational cycle requires it. That is not a surprise — it is the job description. The upside is that by the end of your first deployment, you will have touched more avionics systems in more configurations than any civilian tech of equivalent age, and the fault you close on a Tuesday morning that three senior techs called intermittent is the fault that earns you the CDI conversation.
Career Arc
  • 01NATTC Pensacola graduation — the 5939 pipeline; you do not touch production aircraft without it. Your MALS billet assignment follows from here.
  • 02First months in the MALS or squadron shop: supervised bench work, LRU R&R under CDI co-sign, BIT sequences, GCSS-MC annotation discipline built from scratch.
  • 03First independent fault isolation — a wiring-level diagnosis you close without coaching, documented in GCSS-MC well enough that the CDI signs it on first look. This is the internal milestone the shop chief is watching for.
  • 04Gray Belt MCMAP before LCpl promotion — MCMAP under MCO 1500.54; the avionics shop is still a Marine Corps unit regardless of how much the flight schedule dominates the week.
  • 05First deployment rotation — MEU or UDP to 1st/3rd MAW area; the pace of the flight schedule during a surge is different from home station, and the tech who handles it is visible.
  • 06LCpl to Cpl promotion window — composite score build, Corporals Course packet assembly, CDI qualification pipeline entry; the shop chief is deciding whether to start the CDI recommendation conversation.
Common Screwups
  • ×COMSEC TPI violation — touching a crypto fill device without a witness, failing to document the TPI log completely, or allowing a witness to sign for a procedure they did not observe. This is a UCMJ matter, not a counseling event. The Communications Security Officer is required to report it up the chain on the day of discovery.
  • ×Fraudulent logbook entry — signing a GCSS-MC corrective action for work you observed rather than work you performed, or annotating a step as complete before completing it. The QA division audits maintenance records; one fraudulent entry is an Article 92 or Article 107 offense and voids the maintenance record for the entire work order.
  • ×DUI or NJP during the barracks phase. The MALS has a zero-tolerance posture for first-term DUI — administrative separation proceedings begin immediately. The tech who earns an NJP before CDI qualification has made the CDI conversation significantly harder.
  • ×Posting imagery of aircraft systems, COMSEC equipment, hangar layouts, or maintenance documentation to personal social media. The OPSEC violation attaches to your name in the unit's security incident log, and aviation OPSEC breaches can draw a formal investigation.
  • ×Fitness failure — dropping below 1st-Class PFT/CFT under MCO 6100.13. Aviation maintenance Marines work in confined spaces, climb ladders with toolboxes, and conduct field operations. A 3rd-Class score earns a remedial fitness program and a FitRep notation that follows you to the next shop.

A Day in the Life

  • 0500Wake. Check the section group chat — any overnight maintenance holds or aircraft status changes that affect the morning launch window. PT uniform, head to the MALS or squadron.
  • 0530PT formation. Accountability to the section leader. Junior techs report to the senior tech or section chief. Being the last person into formation is noticed; being the first one dismissed for a late arrival is also noticed.
  • 0545-0700Unit PT — runs, functional fitness, or the squadron-specific PT plan for the day. Aviation maintenance Marines carry equipment up boarding ladders and into confined maintenance spaces; fitness is a functional requirement, not a box-check.
  • 0700-0830Hygiene, chow, utilities. Pre-walk the aircraft work center if a scheduled maintenance event is on today's flight schedule. Any GCSS-MC discrepancies opened overnight need to be reviewed before the morning production meeting.
  • 0830Morning production meeting. The production controller and the Maintenance Officer give the day's flight schedule and maintenance priorities. Your CDI briefs the section's task assignments. You receive your work order for the day.
  • 0900-1130Primary maintenance event — LRU R&R, BIT sequence, fault isolation, corrosion inspection, or a crypto fill evolution under CDI supervision. Document each step in GCSS-MC as you complete it. Call for CDI check when the MIM procedure calls for it — not at the end of the work order.
  • 1130-1300Chow. The junior techs eat with the section. The CDI and the shop chief eat at the adjacent table. The conversations at lunch are not idle — the CDI is noting who is asking good questions about the morning's fault isolation and who is on their phone.
  • 1300-1500Afternoon maintenance — continuation of the morning event, or a new work order if the morning event closed. MIM study during any dead time — know the fault-isolation tree for your assigned systems well enough to walk it without the manual open.
  • 1500-1630Final production meeting. Work order status updates, next-day maintenance schedule, sensitive items accountability (crypto fill devices logged and secured before end of day). Section chief reviews your GCSS-MC entries before dismissal.
  • 1630Liberty call on a normal schedule. The section leader gives the same brief at the end of every work week — liberty standards, DUI consequences, who to call first.
  • 1700-2000Personal time — MCMAP training, MIM self-study, PFT/CFT prep at the gym, or college coursework through Tuition Assistance. The Cpl who hits the composite score gate faster than expected is the one who closed these hours.
  • NIGHT LAUNCH or SURGE periodsClock breaks entirely. The flight schedule sets the maintenance window, and a night launch means a late-maintenance start. You are in the shop when the aircraft is. You document, you clean up your work center, and you secure all tools and crypto fill devices before you leave regardless of how late it is. Missing a tool on tool accountability is a Class-A maintenance discrepancy and grounded aircraft until resolved.

Weekly Cadence

Monday is when the week's flight schedule and maintenance priorities come into focus. The production controller has the week's sortie requirements from the operations officer; the Maintenance Officer has translated those into maintenance events by aircraft. Your CDI gives you the section's task list for the week — which systems need scheduled maintenance, which aircraft have open discrepancies, whether there are any crypto fill events on the schedule. A junior tech who knows the week's task list by Monday morning is a junior tech who is not scrambling Thursday afternoon. Tuesday through Thursday is the production rhythm. R&R events on scheduled maintenance aircraft, fault isolation on discrepancy aircraft, BIT sequences, logbook maintenance, GCSS-MC entries. The pace follows the flight schedule — a heavy launch day means early starts and long afternoons; a light maintenance day may include MIM study time or T&R training events. The CDI is present on the shop floor for primary maintenance events and available for documentation review throughout the day. Junior techs who ask the CDI about fault logic rather than waiting for the CDI to check their work are the techs who close the CDI qualification gap fastest. Friday brings sensitive-items accountability for the week — crypto fill devices inventoried and signed back into the COMSEC safe, tool accountability clean, all open GCSS-MC work orders in the correct status. The section chief reviews the week's T&R event completion against the NAVMC 3500.14 schedule. Any missed T&R events need a makeup plan before the next cycle date. The week's end is also when the junior tech reviews the personal composite score against the cutting score — where is the gap, what is the highest-leverage variable to move before the next Cpl board.

Key Skills — How to Drill Each

  1. 01
    Remove, replace, and BIT-verify a UHF/VHF radio LRU or AN/APX IFF transponder per the applicable MIM — clean connector inspection, torque values, and BIT pass documented in GCSS-MC before calling for CDI check.
    Open the MIM to the removal and replacement procedure before you touch anything. The procedure has connector inspection steps built in — cap counts, pin inspection requirements, torque values for the mounting hardware — and the CDI is going to check whether you followed them in sequence. On IFF transponders specifically, verify the NSN on the replacement box against the part number in the MIM and the work order before you install it. A wrong AN/APX variant may BIT-pass on the bench and fail at operating altitude in ways neither you nor the CDI will catch until the pilot is airborne. Run the BIT sequence from the MIM, not from memory, and document each step result as you go — 'BIT pass, code XX' is a complete entry; 'BIT checked OK' is a rewrite.
  2. 02
    Perform a Two-Person Integrity crypto fill and key-load procedure on a KY-series or HAVEQUICK-compatible device — never touch fill equipment alone, never sign the log without a witness present.
    TPI is a two-step process with two signatures: the individual performing the key-load and the individual witnessing it. Both people must be physically present for the entire procedure — not 'I watched from across the room' present, but standing at the safe, eyes on the fill device, for every step. Before the safe opens, both individuals verify their identities in the log entry. After the procedure, both sign the log with the time, the fill device serial number or keyed system, and the key period loaded. If anything interrupts the procedure — a phone call, someone entering the space, a system error — stop, annotate the interruption, start from step one. The COMSEC account holder checks these logs. One incomplete TPI entry, even one that looks like a clerical error, triggers a COMSEC incident report.
  3. 03
    Read and apply a wiring diagram and connector pin-out from the applicable MIM or IPB — identify the circuit under test before probing a live connector.
    The MIM wiring diagrams use standard aviation wiring notation — wire numbers, circuit breaker designators, connector designators (J1, P1, J2, P2), and pin designators. Before you put a meter probe on anything, trace the circuit on paper: what wire number carries the signal you are testing, which connector pin it terminates at, and what the MIM says the expected value is. The tech who probes a live aircraft connector without knowing what signal is on that pin is the tech who shorts a 28V DC bus to a chassis ground, pops a circuit breaker the production controller cannot explain, and causes a GCSS-MC discrepancy unrelated to the original fault. Trace first, probe second, document what you found.
  4. 04
    Annotate a GCSS-MC discrepancy and corrective-action record accurately and completely — 'performed maintenance' is not a corrective action.
    A complete GCSS-MC corrective action entry describes: what system discrepancy was found (symptoms, fault code if applicable), what diagnostic steps were performed in sequence, what was found at each step, what was replaced or adjusted, and what the post-maintenance verification result was. 'R2 radio set, BIT pass' is closer than 'performed maintenance' but still incomplete. 'Removed AN/ARC-210, inspected RF connectors (no damage found), installed serviceable unit NSN [number], torqued per MIM para X.X, BIT pass code XX — aircraft cleared' is the entry the CDI signs on first look. The shop chief uses good entries as examples. The QA division uses bad entries as training scenarios.
  5. 05
    Conduct corrosion inspection and treatment on antenna mounts, RF connectors, and coaxial cable runs per the applicable MIM.
    Corrosion on an RF connector is an electrical fault in progress. A corroded SMA or TNC connector that reads 50 ohms impedance on the bench may read 55-60 ohms in-flight after thermal cycling, which degrades the IFF output power and the HAVEQUICK frequency-hop sync below the operational threshold. The MIM corrosion inspection section specifies the tool (usually a dental pick and a magnifying glass), the treatment compound (usually a contact enhancer or corrosion inhibitor — verify the specific product the MIM authorizes for your platform), and the inspection intervals. Perform this task at the MIM-specified interval regardless of whether the system is showing a fault. The tech who finds and documents corrosion before it causes a discrepancy is the tech whose preventive maintenance record the CDI mentions favorably.
  6. 06
    Maintain personal ESD discipline — wrist strap, ESD mat, handling procedures — consistently, because a $40,000 avionics card killed by static is a Class-B mishap with your name on the work order.
    ESD discipline is not conditional on whether you feel static when you walk across the hangar floor. Low-humidity climates, synthetic uniform materials, and the rubber soles of safety shoes can build enough charge to damage CMOS circuits without any perceptible discharge. Before touching any avionics card or circuit module, test your wrist strap against the ESD station tester — not just plug it in, but verify the continuity reading is within the MIM-specified range. If the tester shows an open circuit, the wrist strap is non-functional and you report it to the tool room before proceeding. ESD mat condition is the shop chief's responsibility, but the individual tech is responsible for using a verified mat. One avionics card damaged by ESD generates a replacement action that removes the aircraft from the schedule for as long as the part lead time is — and your name is on the work order.

Manuals & References — What Chapters Matter

  • NAVMC 3500.14 — Marine Aviation T&R Manual (Aviation Electronics series)
    This is the source document for every individual and collective task you are evaluated against in the 5939 pipeline. Print the individual-task list for your assigned rank tier and walk it with the CDI during your first 30 days. Each task has performance steps, conditions, and a go/no-go standard — these are exactly the steps the CDI and the QA representative use when they evaluate your work. The tech who knows the T&R task standards cold is the tech who does not need coaching during an evaluation.
  • MCO P4790.2C — Aviation Maintenance Management Program
    The governance document for every maintenance action in a MALS or squadron avionics shop. The chapters governing CDI authority, discrepancy documentation, work-order lifecycle, and the relationship between the QA division and the production techs are the ones you live by. When the CDI challenges your logbook entry or the production controller asks why a work order is in a specific status in GCSS-MC, the answer is in this manual. Own the documentation requirements chapter before you annotate your first work order.
  • Applicable MIM series for assigned platforms (AN/ARC-210, AN/APX-111/119, and platform-specific variants)
    The MIM is the step-by-step procedure document for every maintenance action on your assigned systems. Every removal, every installation, every BIT sequence, every fault-isolation tree is in the MIM. The CDI checks whether you followed the procedure in sequence — not whether you got the right answer by a different route. Ask the shop chief which volumes apply to your assigned aircraft platform on your first day, and verify the edition of each volume against the MALS technical library.
  • GCSS-MC — Global Combat Support System, Marine Corps (Aviation module)
    GCSS-MC is where every maintenance action is tracked — discrepancies, parts requests, corrective actions, work-order status, T&R event completion. A maintenance action that is not in GCSS-MC did not happen as far as the Maintenance Officer and the production controller are concerned. Learn the discrepancy workflow — create, document, route, close — before your first solo work order, and verify your entries are complete and accurate before calling for CDI check.
  • MCO 5530.14 — COMSEC Physical Security Program
    The COMSEC procedures chapter covers TPI requirements, safe handling and storage, key-load documentation, and incident reporting timelines. The junior tech's direct obligations are in the TPI section — who constitutes a qualified second person, what steps require two-person observation, and what documentation format the TPI log requires. Read this chapter before your first crypto fill evolution, and review it again after. The COMSEC account holder will test you.

Standards — How to Hit Each

  • NATTC Pensacola graduation in the 5939 pipeline — you do not touch a production aircraft without it.
    Your pipeline performance at NATTC follows you to the MALS. The shop chief will pull your training record. A tech who graduated at the top of the pipeline has a head start on CDI qualification; a tech who squeaked through with passing scores has a longer supervised period before the CDI recommendation conversation begins. If you are still in the pipeline, take every practice fault-isolation exercise seriously — the diagnostic logic you learn at school is the same logic the MIM uses in the shop.
  • 1st-Class PFT and CFT under MCO 6100.13 — a 2nd-Class score earns a conversation with the quality assurance chief.
    Build a personal fitness program around the PFT and CFT events specifically. The CFT ammunition-can lift and the maneuver-under-fire lane replicate the physical demands of moving avionics equipment in a confined aircraft maintenance space more directly than running alone does. 1st-Class is the floor; the section leader notices who is pulling the platoon run average down. If your PFT/CFT score drops below 1st-Class, a remedial program is mandatory and the notation lands in your FitRep narrative.
  • Zero GCSS-MC discrepancy entries returned for rewrite by your CDI — the logbook is a legal document.
    Track every entry the CDI corrects and understand why the correction was made. After the first month, you should know your own annotation weaknesses — whether you underspecify the diagnostic steps, leave out the BIT result code, or use shorthand that does not pass QA review. Ask the CDI to show you a clean example entry for each work order type you handle. By month three you should be at zero rewrites; by month six the CDI should be co-signing rather than correcting.
  • Annual rifle qualification at Expert level — you are a Marine first, an avionics tech second.
    The avionics shop does not issue rifle-qual waivers. Schedule your range block early enough in the qualification cycle that you have a make-up opportunity if the weather or the flight schedule pushes your primary range day. Dry-fire practice in the barracks is free. The tech who shows up at the qualification range having dry-fired 200 times in the previous month qualifies Expert reliably; the tech who shows up cold and misses Expert is spending a qualification cycle in remediation while the shop chief is deciding who gets the next school slot.
  • Tan Belt MCMAP out of MCRD; Gray Belt before LCpl under MCO 1500.54.
    MCMAP belt progression requires documented sustainment training hours and a technique demonstration before each belt test. Track your hours from the first week in the unit — the MCMAP instructor keeps records but so should you. Gray Belt before LCpl is achievable in the first year if you are training consistently. The tech who walks into the LCpl promotion period without Gray Belt has a composite score gap that takes time to close.

Technical Mistakes — Concrete Consequences

  • Skipping the connector inspection before seating an LRU.
    A single bent pin on an RF connector creates an intermittent IFF fault the pilot will not find until the aircraft is in a contested airspace environment. The MIM specifies the connector inspection step before installation for exactly this reason. The CDI who catches the skipped inspection during a spot-check will document it in your training jacket. The QA representative who catches it in a discrepancy audit will document it in the unit's maintenance program records. A second occurrence removes you from the CDI qualification track.
  • Signing a GCSS-MC corrective action entry for work you watched rather than work you performed.
    This is a fraudulent official record under Article 107, UCMJ — a maximum punishment of five years confinement and a dishonorable discharge. The QA division audits GCSS-MC entries against the work order timeline and the CDI co-sign pattern. One entry where your signature's timestamp is inconsistent with the work-order timeline, or where the entry describes steps a junior tech performed without your involvement, triggers an investigation. The investigation goes to the Maintenance Officer and the CO. There is no version of this outcome that does not end your 5939 career.
  • Touching a crypto fill device without a witness or without completing the TPI log.
    MCO 5530.14 requires the COMSEC account holder to report a TPI violation as a COMSEC incident on the day of discovery. The incident report goes to the Communications Security Officer, the Communications Officer, and the unit CO. At the junior-tech level, a TPI violation typically results in NJP and removal from COMSEC access. COMSEC access removal means you cannot perform key-load procedures, which limits your utility to the shop and delays CDI qualification.
  • Installing an LRU without verifying the NSN against the work order and the MIM part number.
    An incorrect IFF transponder variant — say an AN/APX-111 installed where an AN/APX-119 is specified — may produce a clean BIT signature on the bench and perform within tolerances during ground testing. In flight, the platform's avionics integration may produce mode/code errors the pilot does not catch before entering a coordination area. The production controller traces the part requisition to the tech who submitted it. The shop chief has a documented conversation with you. The aircraft may require a return-to-depot action depending on what the incorrect part did to the surrounding integration.
  • Allowing an ESD wrist strap failure to go unreported because the shop is busy.
    One undetected static discharge on an avionics card generates a replacement action that grounds the aircraft for as long as the repair part lead time is — potentially days or weeks for a line-replaceable avionics module. The mishap report identifies the last tech who handled the card and the ESD control measures in place at the time. A tech whose ESD wrist strap failed a continuity test and who did not report it before handling avionics cards is the tech named in the Class-B mishap investigation narrative.

Career Decisions at This Rank

  • CDI qualification timeline — how aggressively to pursue it as an LCpl or early Cpl
    CDI qualification in the MALS avionics shop is not an automatically awarded milestone — it is a recommendation from the shop officer based on demonstrated error rate, systems knowledge depth, and documentation discipline. The junior tech who asks the CDI to document each coaching event and who tracks the standard the shop officer uses is the tech who compresses the timeline. The tech who waits to be told they are ready is the tech who waits 18 months. CDI qualification at LCpl is unusual but possible; CDI qualification within the first year as a Cpl is achievable and is the marker that makes the Sgt composite score conversation go differently.
  • Reenlistment at end of first term — technical depth in 5939 versus lateral move or EAS
    The 5939 occfield in the Marine Corps is a relatively small technical community. First-term 5939 Marines who reenlist and pursue CDI qualification, COMSEC account experience, and a deployment rotation leave with an avionics maintenance background that the commercial aviation sector values. The Marine who EASes as an LCpl bench tech with one MALS tour and no CDI qualification leaves with NATTC training and GCSS-MC experience — useful, but not differentiated. The Marine who EASes as a CDI-qualified Cpl with one deployment and documented fault-isolation experience on F/A-18, F-35B, or MV-22 platforms is competitive for avionics technician roles at commercial MROs, with FAA A&P licensure as the complementary credential. Run the math on SRB amounts from the current MARADMIN against the civilian salary delta; the gap is real but the technical credential story is the deciding variable.
  • Corporals Course timing — early in the Cpl window versus waiting
    Corporals Course is a prerequisite for the Sgt cutting score — the composite score that determines Cpl-to-Sgt promotion is not competitive without Corporals Course completion. Schedule the Corporals Course slot through the shop chief as early as the Cpl window opens. The shop chief who sees you asking about the Corporals Course slot in the first month as a Cpl is the shop chief who makes the scheduling conversation easier; the one who hears about it from the career planner has a different read of your initiative. In-residence Corporals Course is standard — the peer network and the leadership practicum matter in ways that distance education does not replicate.

How the Seat Varies by Unit Type

  • MALS (Marine Aviation Logistics Squadron) avionics shop — the primary billet
    Most 5939 Marines report to a MALS at one of the Marine aircraft wing installations — 1st MAW at Iwakuni/Futenma, 2nd MAW at Cherry Point/New River/Beaufort, 3rd MAW at Miramar/Yuma/Pendleton, 4th MAW in the reserve component. The MALS maintains equipment across the wing's assigned aircraft platforms; the 5939 bench tech may work on communications systems across F/A-18s, F-35Bs, MV-22s, or CH-53s depending on the MALS tasking. The MALS pace is keyed to the wing's flight schedule and the pre-deployment maintenance surge. Evaluations are against NAVMC 3500.14 individual tasks with the QA division sampling CDI work quarterly.
  • Squadron communications/avionics division — embedded with the flight unit
    Some 5939 Marines are billetted directly in a squadron avionics division rather than the MALS. The pace is different — the squadron's own aircraft and the squadron's own flight schedule set the maintenance tempo. You are more directly visible to the squadron's aircrew and officers; when the IFF is the reason a sortie slipped, the maintenance officer and the pilots both know who was on the work order. Smaller shop, more visibility, and the CDI qualification conversation happens directly with the squadron maintenance officer rather than through the MALS maintenance chief.
  • MEU deployment — BLT or ACE billet afloat
    A junior 5939 tech who deploys on a Marine Expeditionary Unit will be attached to the Aviation Combat Element (ACE) aboard amphibious shipping (LHD or similar). The maintenance environment is compressed — smaller shop space, limited parts resupply cycle, and the flight schedule running at operational tempo rather than training pace. TPI crypto fill evolutions happen at sea, the COMSEC account management is tighter, and the tech who has never seen a night flight deck evolution will see several. The MEU deployment is the formative technical experience of the first term — the tech who comes back CDI-qualified with deployment logbook entries has a materially stronger composite and a better CDI recommendation letter than one who has not.
  • Forward deployed to 1st MAW — Iwakuni or Futenma/Okinawa
    Forward-deployed 5939 Marines in 1st MAW area (MCAS Iwakuni, MCAS Futenma/MCAS Camp Butler) work in a different operational tempo from CONUS. Maintenance windows support the Pacific operational posture, exercises with JMSDF and allied partners are frequent, and the TPI and COMSEC procedures are enforced at a higher inspection tempo because the operational stakes of a COMSEC violation in a forward-deployed environment are higher. Unaccompanied tour policy varies by installation and rank — verify current policy with the shop chief before PCS orders are cut.

What Good Looks Like at This Rank

The good junior 5939 is recognized by what she does not need to be told. The CDI does not find connector caps missing from open RF connectors. The GCSS-MC corrective action entries do not come back for rewrite. The TPI log is complete and both signatures are present and legible before the crypto safe closes. She does not ask what to do next after completing a task — she annotates the work order, stages the next LRU, and is already reading the fault tree for the next discrepancy by the time the CDI comes over. By month six, the CDI is co-signing her documentation rather than correcting it, and the quality assurance chief has pulled her IFF sign-off for audit once without finding a discrepancy. By month twelve, the shop chief has put her name on the TPI roster — not because there was no one else available, but because her crypto fill documentation has been clean every time. The Maintenance Officer knows her name because no logbook entry she has produced has come back for rewrite, and the two intermittent faults she closed that three senior techs called NMC are now in the shop's fault-isolation training file. She PT's at 1st-Class. She knows where the composite score gap is without being asked. She treats the MIM as the answer book rather than the obstacle, because she understands that the MIM is what the next tech reads to figure out what she did and why. That is the standard the shop chief is building toward, and it is visible to anyone paying attention.

Preview — The Next Rank

Corporal in the MALS avionics shop is the CDI qualification rank. The chevron does not grant CDI authority — the shop officer's written endorsement does, and the endorsement comes when the error record and the systems knowledge justify it. The Cpl who arrives at E-4 with a clean documentation record, gray belt, and a documented fault isolation history is the Cpl who has a CDI recommendation conversation within the first six months of the Cpl window. The Cpl who arrives without those is working from behind. At Cpl the scope of responsibility expands beyond personal bench work. You are now the senior tech on a two-person evolution, the individual who ensures TPI documentation is complete before calling the account holder, and the informal mentor for the LCpls on the section. The composite score build that drives the Sgt cutting score — Corporals Course completion, MCMAP belt, rifle qual, PFT/CFT scores, education credits through Tuition Assistance — runs parallel to the CDI qualification track. The Cpl who is managing both in parallel is the Cpl who is competitive for Sgt. The one who defers the composite score work until after CDI qualification is behind.
FAQ

5939 E1-E3 — Frequently Asked Questions

Q01What does a E1-E3 5939 (Aviation Communication Systems Technician) actually do?
You graduate the Naval Air Technical Training Center (NATTC) pipeline at Pensacola and report to a Marine Aviation Logistics Squadron (MALS) or a squadron avionics/comms shop.
Q02What's the most important thing to know as a E1-E3 5939?
The COMSEC procedures feel like bureaucracy until the day you are standing in front of the Communications Security Officer explaining why you touched the crypto fill device without a witness.
Q03What does a typical day look like for a E1-E3 5939?
Time-blocked day at the E1-E3 5939 rank tier: 0500 Wake. Check the section group chat — any overnight maintenance holds or aircraft status changes that affect the morning launch window. PT uniform, head to the MALS or squadron, 0530 PT formation. Accountability to the section leader. Junior techs report to the senior tech or section chief. Being the last person into formation is noticed; being the first one dismissed for a late arrival is also noticed, 0545-0700 Unit PT — runs, functional fitness, or the squadron-specific PT plan for the day.…
Q04What mistakes get E1-E3 5939 soldiers fired or relieved?
COMSEC TPI violation — touching a crypto fill device without a witness, failing to document the TPI log completely, or allowing a witness to sign for a procedure they did not observe. This is a UCMJ matter, not a counseling event. The Communications Security Officer is required to report it up the chain on the day of discovery; Fraudulent logbook entry — signing a GCSS-MC corrective action for work you observed rather than work you performed,…
Q05What career decisions matter most at the E1-E3 5939 rank tier?
CDI qualification timeline — how aggressively to pursue it as an LCpl or early Cpl — CDI qualification in the MALS avionics shop is not an automatically awarded milestone — it is a recommendation from the shop officer based on demonstrated error rate, systems knowledge depth, and documentation discipline. The junior tech who asks the CDI to document each coaching event and who tracks the standard the shop officer uses is the tech who compresses the timeline. The tech who waits to be told they are ready is the tech who waits 18 months. CDI qualification at LCpl is unusual but possible;…
Q06What's next after E1-E3 for a 5939 (Aviation Communication Systems Technician) in the Marines?
Corporal in the MALS avionics shop is the CDI qualification rank.
Q07What manuals and regulations does a E1-E3 5939 need to know cold?
NAVMC 3500.14 — Marine Aviation T&R Manual (Aviation Electronics series; the source of every 5939 individual and collective task you are evaluated against).; MCO P4790.2C — Aviation Maintenance Management Program (the bible for how maintenance documentation, discrepancy logging, and sign-off authority works in a MALS or squadron avionics shop).; Applicable MIM (Maintenance Instruction Manual) for each radio/IFF system — AN/ARC-210 (UHF/VHF), AN/APX-111/119 (IFF),…

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