Skip to main content
HonestMOS
●InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.→
←Back to AT Aviation Electronics Technician — overview, pay, training, civilian translation, reviews
ATE1-E3

Aviation Electronics Technician

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

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

You graduated NATTC Pensacola as an Apprentice AT. The fleet squadron is not a continuation of A-school — it is the first real job. Your name is on every piece of paper you touch, and the QA inspector reads every piece of paper you touch. Get the PQS signed, learn ESD discipline before it costs you an LRU, and start reading your NWAE bibliography before the AT3 window creeps up.

The Honest MOS Read
You checked aboard a fleet aviation squadron — a VFA with F/A-18E/F Super Hornets, a VAQ with EA-18G Growlers, a VAW with E-2D Hawkeyes, a VP with P-8A Poseidons, or an HSM or HSC helicopter squadron with MH-60R/S Seahawks — and the LPO handed you a PQS binder, a grounding strap, and the least glamorous job in the avionics bay. You are an Apprentice AT in everything but title: your rate card says AT but the work center sees an ATSN who has not yet earned a place on the fault-isolation bench. The first months are not glamorous and that is correct. You are cleaning test benches, logging discrepancy write-ups in the maintenance information system, verifying documentation on jobs the AT2s and AT3s completed, hauling line-replaceable units (LRUs) from the calibrated cage to the bench and back, and watching the senior techs run built-in test equipment (BITE) fault isolation on avionics boxes. That observation time is not wasted time — the ATSN who pays attention during those first 90 days can describe what an APG-79 radar fault isolation looks like before he has ever touched the procedure himself. The ATSN who zones out becomes the AT3 who still needs hand-holding on the bench. ESD (electrostatic discharge) discipline is the first real test of your professionalism. LRUs on an aviation avionics bench are sensitive to static discharge in ways a junior tech underestimates — a latent ESD event damages the circuitry without any immediate visible indication. The LRU passes BIT checkout, goes back on the jet, and degrades in flight three sorties later. The maintenance documentation traces back through the cage log to the last technician who handled it without proper grounding. That technician's name is on the safety investigation. Treat every LRU as ESD-sensitive regardless of whether anyone is watching, because the cage log is always watching. Tool control is the other discipline that separates the sailor who belongs in an aviation maintenance shop from the one who does not. Aviation FOD (foreign object debris) is a class A mishap waiting to happen. One tool left in a cockpit or avionics bay, ingested by an engine or lodged in a control surface, is the kind of event that ends careers and kills aviators. Sign the tool out when you pull it from the box; account for it before you close any access panel or exit any cockpit; sign it back in before you leave the shop. There are no exceptions and no "I thought the other AT3 had it" excuses that survive a FOD investigation. NATTC Pensacola taught you the fundamentals — basic electronics theory, avionics systems overview, wiring diagram interpretation, test equipment operation — but the fleet aircraft are not NATTC benches. The MIM (Maintenance Instruction Manual) for your platform is the technical authority, and the procedure the AT2 is running is pulled from that MIM, not from memory. Your first productive habit is learning to read MIM fault isolation procedures rather than watching someone else interpret them. Pull the relevant section, follow the tech. When the AT2 runs a BIT, you track the step on the page. When he writes up the corrective action, you read the language and understand why that WUC (Work Unit Code) and corrective action were chosen. The career conversation about NEC pipelines — platform-specific avionics, electronic warfare, radar, sensor systems — feels abstract at ATSN but it is not. Navy COOL funds the FAA A&P, the FCC General Radiotelephone Operator License (GROL), and the NCATT AET (Aircraft Electronics Technician) credential. Those credentials are yours if you pursue them. The AT2 who mentions the NEC pipeline to you in your first 90-day counseling is doing you a favor — pull the current NEC source-rating NAVADMIN and start the conversation before the AT3 board cycle. The sailor who arrives at the AT3 slate without a NEC direction is the sailor the LPO has to counsel reactively instead of proactively.
Career Arc
  • 01Check aboard fleet squadron post-NATTC Pensacola. LPO assigns PQS binder, work center berth, watch bill slot.
  • 02First 90 days: bench support role — ESD handling, LRU cage accountability, maintenance log documentation, observing AT3/AT2 fault isolation.
  • 03PQS line items building — platform-specific avionics qual, tool control qual, safety-of-flight documentation qual.
  • 04AT3 eligibility window opens (TIS/TIG per NAVADMIN): NWAE study log under LPO's eye; pull current BIB from MyNavyHR/NETC.
  • 05NEC direction conversation with LPO and career counselor — platform-specific NEC pipeline, EW NEC, radar NEC, or IMA depot track.
  • 06Navy COOL window opens: FCC GROL study, NCATT AET registration, FAA A&P path noted.
  • 07PRT/BCA cycle maintained; 301-series watch quals complete; first eEVAL drops with LPO input.
Common Screwups
  • ×ESD incident from skipping the grounding strap 'just once.' The cage log records the handler; the maintenance investigation follows the log. A latent-damaged LRU that degrades on the flight line names you at the safety review.
  • ×Tool accountability failure — leaving a tool in a cockpit or avionics bay. One FOD event at the wrong moment is a Class A mishap. Your name is the last one on the checkout log. Aviation maintenance does not give second chances on tool accountability.
  • ×Letting PQS stall because the shop is busy. The LPO notes the stalled PQS binder at the quarterly review. The ATSN who finishes PQS last in the work center cohort starts the AT3 advance cycle behind the peer group.
  • ×NJP or DUI — separation processing, clearance review, advancement flags, and the entire NEC pipeline closed before it opened.
  • ×Posting photos from the avionics bay — cockpit displays, pod configurations, tail numbers, squadron patches, hangar deck content. Squadron S2 and PAO run sweeps; adversary collection follows Navy aviation social accounts.

A Day in the Life

  • 0500-0600Wake up. If on the flight line duty section, phone check for overnight discrepancies or watchbill changes. PT gear on — squadron morning PT or personal PT before report.
  • 0600-0700Command PT or shop PT. Aviation squadrons vary — some run unit PT on the flight line apron, some release to the gym. The ATSN who falls out of the run gets noticed. Build a baseline from week one.
  • 0700-0800Hygiene, chow, into utilities. Pre-quarters check: review the day's work center plan from the LPO's board, check PQS binder for any line items that can be signed today, confirm any bench assignments from the day prior.
  • 0800-0830Quarters. LCPO or LPO puts out plan-of-the-day; work center assignments distributed. The ATSN stays quiet, listens, and writes down the day's tasking. You do not have the floor at quarters until the LPO hands it to you.
  • 0830-1130Work center time. Bench support role: LRU cage pulls and returns for AT3/AT2 fault isolations, maintenance log entries under supervision, bench cleaning and calibration equipment check-in, MIM reading on the bench system you are learning. Watch the AT2 run the fault isolation procedure; follow it on the page.
  • 1130-1230Chow. You eat with the other ATSNs and junior AT3s. Quick check of the tool log before stepping away from the bench — every tool signed in before the bench is left unattended.
  • 1230-1500Afternoon bench block. If the AT3 has PQS line items to sign, this is the window to ask. LRU documentation work, any assigned watch qualification study, maintenance log review with the AT2. If a jet write-up came in before noon, the shop may be on the flight line with the AT2 and you are the pack mule and the documentation writer.
  • 1500-1600NWAE study block. The ATSN who builds 30 minutes a day into the bench routine before the AT3 eligibility window opens is the ATSN who does not miss the first slate. Pull the current BIB from MyNavyHR/NETC and start from page one.
  • 1600-1630End-of-day tool accountability. Every tool on your work center assignment signed in. Calibrated test equipment powered down correctly and documented. Bench clean, anti-static surfaces grounded and covered. LCPO walks the deck before release.
  • 1630-1800Released most garrison days. Detachment surges, flight schedule crunches, deployment cycles, and duty sections change this window. If on duty section: stand assigned watch, run LRU cage night accountability, support any after-hours flight schedule write-ups.
  • 1800-2100Personal time. Barracks or off-base. ATSN in the first enlistment: gym, study (FCC GROL prep if started, NWAE BIB, NAVEDTRA rate manual), Navy COOL exploration, personal admin.
  • 2100-2200PQS review — identify the next three unsigned line items, prep any questions for the AT3 or AT2 tomorrow morning. The ATSN who arrives at morning quarters knowing exactly which PQS line items need witnesses is the ATSN who finishes PQS first.
  • 2200Lights out. Tomorrow at 0500.
  • Deployment / detachment tempoThe squadron is embarked or on a shore det. Bench hours extend to 12-14 hours during surge ops; the ATSN is support for the AT3/AT2 team running extended fault isolation on ready-deck write-ups. Documentation pace doubles; ESD and tool control discipline matter more, not less, under time pressure.
  • Duty section (assigned rotation)24-hour section duty as the junior member. LRU cage accountability overnight, maintenance log entry support, work center security watch as directed. The ATSN on duty does not sleep through a flight schedule emergency; the work center phone rings before 0400 sometimes.

Weekly Cadence

The Mon-Fri rhythm for an ATSN in a fleet aviation squadron is structured around the flight schedule and the maintenance production cycle. Monday is the heaviest planning day for the work center — the maintenance plan for the week is published after weekend stand-down, and the LPO assigns bench slots and flight line support tasking at morning quarters. As an ATSN your Monday job is to understand your week's assignment, confirm your PQS line items for the week, and check that the tool sub-account is clean coming off the weekend. Tuesday and Wednesday are the core production days for most squadrons. Flight operations run, write-ups come off the deck, and the avionics shop is working at whatever tempo the flight schedule demands. As an ATSN you are at the AT3's and AT2's side on bench work and flight line support — documentation, LRU handling, test equipment setup. The quality of your work center contribution in these two days is what the AT2 mentions when the LPO asks how the junior bench sailors are doing. Thursday typically carries maintenance officer sync or department-level readiness review — the ATSN is not in those meetings but the work center's documentation quality is reflected in the numbers the AT1 or AT2 briefs. Friday is plan-of-the-week-out and any readiness checks the LPO runs before liberty. The flight schedule collapses this rhythm during high-ops-tempo periods — carrier air wing workup, pre-deployment training cycles, sustained surge operations on deployment — and expands it during stand-down and post-deployment maintenance periods. During stand-down the ATSN's best window for PQS progress and NWAE study opens: longer bench hours without flight-schedule urgency means the AT2 has time to sign PQS line items and the ATSN has time to read. Use it. The ATSN who coasts during stand-down and cramsheets during the workup shows up with half a PQS binder and no NWAE study log when the AT3 window opens.

Key Skills — How to Drill Each

  1. 01
    Log a maintenance action in the applicable maintenance information system — correct WUC, system code, corrective action text — clean enough that QA does not send it back.
    The WUC is not a guess — it comes from the MIM or the maintenance information system's lookup, not from asking what the AT3 used last time. The corrective action describes what was done: replaced, repaired, inspected, cleaned, adjusted, with the technical reference and the part number or serial number where required. Pull the previous job card on the same system for format reference, then verify against the MIM. QA return-for-rework on your documentation is a pattern that follows you to the eEVAL; zero returns is the floor.
  2. 02
    Handle an LRU from cage to bench to return without causing ESD damage — proper bagging, grounding strap, documentation, packing chain intact.
    Before you touch the LRU: grounding strap on your wrist, strap grounded to an ESD-safe surface, anti-static bag staged. During transit: LRU in the bag, bag sealed, no contact between the LRU pins and any ungrounded surface. At the bench: ESD mat grounded, every technician who touches the LRU grounded. On return: original anti-static packaging or equivalent. The one time you shortcut this chain is the one time the cage log traces back to your name on a latent-damage finding. Drill the habit until it is reflexive.
  3. 03
    Read a wiring diagram from the MIM and trace a circuit from connector pin to LRU — not guessing, reading.
    NATTC taught you diagram symbology. Fleet MIMs are more complex, but the skill transfers. Pick one system in your work center — radar altimeter, communications set, navigation system — pull the applicable MIM wiring diagram section, and trace the power circuit and the signal circuit end-to-end without asking anyone. Then verify with the AT2 that you traced it correctly. One diagram per week builds the skill that makes you a productive AT3 at the bench within 12 months.
  4. 04
    Complete AT rate PQS and platform-specific 301-series watch qualifications on the LCPO's timeline — every line item witnessed, not assumed.
    The PQS is a training contract between you and the shop. Every line item requires a witness signature from a qualified technician — it does not auto-complete because you observed the evolution. At the start of each week, identify the next three line items, ask the AT3 or AT2 who is qualified to sign them to show you the evolution and sign the line. The LCPO who checks your PQS at week 12 and finds it two-thirds complete has a decision to make about your eEVAL — make that decision easy.
  5. 05
    Follow tool control to the letter: signed out, signed in, FOD check before and after, nothing left in a cockpit or avionics bay.
    The tool control habit is built in the first 30 days or it is never fully built. Every time you pull a tool from the controlled toolbox: sign it out on the log, account for it during the work, sign it back in when you return it — even if you only had it for 10 minutes. Before closing any panel: count the tools on your person, count them against the sign-out log, confirm the space is clean. Do this every time without exception, and the habit becomes automatic. The AT who asks you to 'just be quick about it' is the AT whose FOD event you do not want to share.

Manuals & References — What Chapters Matter

  • NAVAIR 01-1A-505-1 through -4 — Organizational and Intermediate Maintenance of Avionics Equipment
    The technical manual series that governs how your bench work is documented and executed. At ATSN level you will not use all four volumes immediately, but start with the organizational-level volume that covers your work center's systems. The AT2 running a fault isolation procedure is using this reference — follow him to the section and read it while he works.
  • OPNAVINST 4790 series — Naval Aviation Maintenance Program (NAMP)
    The umbrella program instruction that every maintenance action you will ever log operates inside. At ATSN you do not need to read it cover to cover — but you do need to understand why maintenance documentation standards exist and what happens when they are violated. The QA provisions chapter is where your shop's documentation standard comes from.
  • Platform-specific MIM / NATOPS / Maintenance Requirement Cards (MRCs) for your aircraft
    The MIM is the law of the bench in your work center. Your LPO will identify which TM series and which work-unit sections apply to your berth. Own those sections — not the whole publication, the sections your shop uses. The AT3 who can navigate the MIM for his work center's systems without asking for help is the AT3 the LPO sends to the jet alone.
  • NAVPERS 18068 Vol II — Manual of Navy Enlisted Manpower and Personnel Classifications (NEC catalog)
    The AT-series NEC entries describe the pipelines available to you: platform-specific avionics, electronic warfare, radar, sensor systems. Read the entries before your first career-counseling session so the NEC conversation is grounded in the source document and not in what a buddy told you. The current source-rating NAVADMIN supplements this catalog with active quotas — pull both.
  • NWAE Bibliography for Advancement (BIB) for AT3 cycle — current, from MyNavyHR / NETC
    The BIB is the test and the test is the BIB. Pull it the day you are eligible to check whether you are close to the TIS/TIG window for AT3 — do not wait for the LPO to hand it to you. Build a 30-minute daily study habit before the cycle opens; the ATSNs who hit the NWAE cold are the ones who miss the first slate and spend another cycle watching peers advance.

Standards — How to Hit Each

  • AT PQS complete on the LCPO's timeline — every line item signed by a qualified witness.
    At the start of each week pull the PQS binder and identify the next three unsigned line items. Ask the AT3 or AT2 who is qualified on those items to walk you through the evolution and sign. Do not wait for the LCPO to chase you. The sailor who finishes PQS ahead of the cohort is the sailor the LCPO mentions by name when a C-school pipeline slot comes open.
  • Tool control compliance: zero unresolved tool discrepancies on your name for the assignment.
    Tool control is binary — the tool is signed out and accounted for, or it is not. Build the sign-out/sign-in habit within your first week on the job. Before closing any cockpit or avionics bay access: physically verify every tool you brought into the space is back in your hands and signed in. The calibrated test equipment assigned to your bench section has calibration due dates — put them in a phone reminder 90 days out and alert the AT2 before the drift happens.
  • Zero ESD incidents on your name throughout the ATSN tenure.
    ESD discipline is not a training-exercise courtesy — it is a documented standard in the NAVAIR maintenance environment. Set the grounding strap before you touch the LRU, every time, regardless of whether the AT2 is watching. The latent ESD damage that appears three sorties later is traced through the cage log to the last ungrounded handler. That is how a habit becomes a career record.
  • PRT Good Low or higher; BCA in standard from the first cycle.
    Aviation squadrons have physical readiness standards that exist alongside the avionics technical standards — the two are not separate. The ATSN who falls out during squadron PT on the flight line apron is noticed. Build a baseline PT routine: run 3 days a week, lift 2 days a week, make the Navy's minimum PRT Good Low your floor from day one. It is much easier to maintain a baseline than to rebuild fitness after a failure.

Technical Mistakes — Concrete Consequences

  • Logging a maintenance action from memory instead of from the book — incorrect WUC, missing corrective-action reference, vague description of what was done.
    QA return-for-rework on your documentation creates a paper trail that compounds into the eEVAL narrative. One return-for-rework is a lesson; two within a deployment cycle is a pattern the LCPO notes. A maintenance record that cannot be verified against the MIM technical reference is also a safety risk — the follow-on technician who reads your entry and acts on it is working from your interpretation, not from verified doctrine.
  • Skipping the FOD check before closing an access panel or exiting a cockpit.
    The last person to have the access open is named first on the safety investigation when the FOD event happens. Aviation maintenance FOD events — tools or hardware ingested by an engine, lodged in a flight control, or left in a fuel system — are Class A mishaps. They kill aviators and they end the careers of the technicians whose names are on the job documentation. No deadline, no scheduling pressure, no supervisor impatience justifies skipping the FOD check.
  • Treating ESD grounding as optional when the LPO is not present or when time pressure is high.
    Latent ESD damage does not announce itself at the bench — the LRU passes BIT, returns to service, and fails in flight. The cage log and the maintenance documentation trace the handling chain; the ungrounded handler's name is recoverable. The cost is not just a written record — it is an in-flight avionics degradation event that grounds the aircraft, triggers a safety review, and identifies the technician who shortcut the standard.
  • Going around the AT2 or AT1 on a technical call without authorization.
    The maintenance authorization chain exists for a reason — the action you take on a fleet aircraft must be authorized at the correct level, documented with the correct technical reference, and reviewed by QA. An ATSN who makes a technical judgment call and acts on it without authorization is producing an undocumented maintenance action on a flight-critical system. The mishap board will ask who authorized the work, and 'I was confident in my diagnosis' is not an authorization.
  • Letting PQS stall because the work center is busy and the AT2 seems too occupied to sign line items.
    The PQS is your responsibility, not the AT2's. A stalled PQS at the quarterly review signals to the LCPO that the ATSN cannot manage competing priorities — a signal that follows into the first eEVAL narrative. The AT3 advancement cycle is tied to TIS/TIG, and the ATSN who enters the cycle with incomplete qual progression is starting behind. Ask the AT2 for the line-item witness when the work center is slower; do not wait for the LCPO to ask.

Career Decisions at This Rank

  • Which NEC pipeline to pursue — platform-specific avionics, electronic warfare, radar/fire control, or IMA depot track
    The NEC decision at ATSN is the earliest career fork in the AT rate. Platform-specific NEC pipelines (tied to a particular aircraft type — F/A-18 series, E-2D, P-8A, MH-60R/S) keep you operationally embedded with the aircrew and the flight schedule. EW-focused NECs (tied to VAQ squadrons and EA-18G systems) carry the electronic warfare specialization that has strong defense-industry translation. Radar/fire control NECs build the technical depth that transitions to the FAA regulatory or avionics test environment. IMA depot-track NECs build intermediate-maintenance depth that leads to depot contracts and the DoD civilian workforce pipeline. Pull the current NEC source-rating NAVADMIN, talk to AT2s and AT1s in each pipeline, and make the call before the LPO has to make it for you.
  • FCC General Radiotelephone Operator License and NCATT AET — start early or wait
    Navy COOL funds both credentials and both are employer-visible in the commercial aviation market. The FCC GROL exam covers communications system theory that overlaps with the NWAE bibliography — studying for one advances both. The NCATT AET is the industry-standard aircraft electronics technician credential that civilian MRO (maintenance, repair, and overhaul) employers recognize alongside the FAA A&P. Starting GROL prep as an ATSN is not premature; it is the kind of initiative the LPO notes on the eEVAL and the kind of credential that stays on your resume for 20 years. Talk to your LPO about the COOL process before the next advancement worksheet cycle.
  • Re-enlistment versus ETS at the end of first contract
    The first-term decision arrives faster than it feels in the barracks. Most enlisted sailors have a four-year first contract with a 12-month re-enlistment window that opens before the 36-month mark. The AT rate's NEC pipeline depth, the Navy COOL credentialing stack, and the defense-industry and commercial-aviation post-service market are genuinely strong arguments for staying through at least an AT3 or AT2 pin — the sailor who leaves at ATSN with no NEC and no COOL credential is leaving the technical investment half-made. The sailor who stays through AT2 with an NEC, an FCC GROL, and NCATT AET walks out into a commercial aviation MRO market that will compete for him. Run the math with the career counselor before the window closes.

How the Seat Varies by Unit Type

  • F/A-18E/F VFA squadron (avionics shop, high-ops-tempo)
    The Super Hornet's avionics suite — AN/APG-79 AESA radar, navigation/targeting pod integration, digital flight controls, communications and IFF systems — is dense and deployment-driven. An ATSN at a VFA squadron works inside the carrier air wing deployment cycle: workup, deployment (7-9 months), post-deployment maintenance period, back to workup. The pace during carrier workup and deployment is the most demanding in the AT rate. The bench work is meaningful — a radar write-up on the flight deck 90 minutes before a scheduled launch is the real version of the job. Tool control and ESD discipline at carrier tempo are not optional.
  • EA-18G Growler VAQ squadron (ALQ-218 EW systems)
    The VAQ is the electronic warfare community inside naval aviation. The EA-18G's electronic attack and jamming mission means the avionics systems — AN/ALQ-218 Tactical Jamming System, AN/ALQ-99 pods, and the aircraft's own emitter systems — are sensitive, complex, and operationally significant in ways that require additional security awareness. An ATSN at a VAQ works near EW-specific systems that have classification implications for documentation, photo policy, and external communications. The technical depth in the VAQ community is genuinely distinctive and the NEC pipelines tied to EW systems have strong post-service defense-industry translation.
  • E-2D Hawkeye VAW squadron (radar-heavy, long-range electronics)
    The E-2D Hawkeye's AN/APY-9 radar and the mission systems that support long-range airborne early warning and battle management are the defining technical environment in a VAW avionics shop. The radar system is physically large (rotodome-mounted), the mission systems integration is complex, and the technical documentation load per aircraft is heavier than in a point-defense fighter squadron. An ATSN at a VAW gets deep exposure to large-aperture radar system maintenance — a NEC pipeline that transitions well to the ground-based radar and air traffic control electronics market.
  • P-8A Poseidon VP squadron (land-based, ASW electronics)
    VP squadrons are shore-based and the deployment pattern is different from carrier air wing squadrons — P-8A crews and maintenance detachments deploy to forward operating locations for 6-12 month cycles rather than carrier deck deployments. An ATSN at a VP squadron experiences the land-based maintenance environment: the avionics bay and bench work are similar in technical content but the operational tempo and the crew-and-aircraft integration are different from a carrier-embarked context. The P-8A's acoustic sensor, radar, and communications suites have strong crossover to the commercial Boeing 737-derivative airframe avionics market.
  • MH-60R/S helicopter HSM/HSC squadron
    Helicopter squadrons run a different maintenance tempo from fixed-wing — more frequent inspection intervals, different avionics architecture (rotary-wing systems, dunking sonar integration on the MH-60R, hoist and cargo systems on the MH-60S), and a detachment-heavy deployment pattern (small shipboard detachments versus full squadron carrier deployments). An ATSN at an HSM or HSC works in a smaller avionics shop where junior sailors get broader exposure to more systems earlier, because the shop cannot afford narrow specialization at low manning. The flip side is less depth on any single NEC pipeline — the cross-training is broad but the formal NEC progression takes longer.

What Good Looks Like at This Rank

The good ATSN is the apprentice the LPO sends to bench-prep an LRU when the AT2 is already running a fault isolation on the jet — because the ATSN's documentation will come back clean and the QA inspector will not flag it. The LPO knows this because the ATSN asked the right questions during the first month: how does the cage log entry work, why does the WUC matter, what does this MIM section say about the interconnect for the radar altimeter. He did not wait for information to be handed to him; he pulled it. His PQS binder is ahead of the cohort by month six. Not because he asked the AT2 to rubber-stamp line items, but because he identified the evolutions he needed signed, asked the AT3 or AT2 with time to witness them, and kept the binder updated. The LCPO who flips through it at the quarterly review can trace every signature to a real evolution. His tool control log is clean — no unresolved discrepancies, calibration due dates tracked in his phone, FOD check completed every time whether or not anyone is watching. By month nine the NEC conversation has happened. The good ATSN pulled the current NEC source-rating NAVADMIN before the counseling session and showed up with a question about the platform-specific NEC track for his squadron type. The LPO mentioning his name for a C-school pipeline slot is not a surprise — it is the result of 12 months of documented professionalism that the LPO can defend with paper.

Preview — The Next Rank

AT3 (E-4) is the first petty officer rank, and the job changes materially. You are no longer an apprentice watching fault isolation — you own a section of the bench, you run BIT/BITE procedures yourself, you train the next ATSN on PQS line items with your signature as the qualified witness. The LPO assigns you a sub-account of calibrated test equipment to manage. The NEC pipeline you chose at ATSN starts to become a C-school pipeline request, and the career conversation about AT2 advancement is no longer hypothetical. The NWAE for AT2 is the gate most AT3s focus on at this rank. The Navy Enlisted Advancement System (NEAS) combines exam score, eEVALs, time-in-rate, awards, and education into a Final Multiple Score. The AT3 who arrives at the AT2 advancement cycle with a documented study log, a clean billet record, a NEC in motion, and an EP or MP eEVAL ranking is the AT3 with a real shot at the slate. The AT3 who phones the study log and counts on being liked by the LCPO is the AT3 who watches the slate from the bench. What you cannot see from ATSN is how much more responsibility the crow carries. The AT3 is the first technician whose name on the maintenance documentation carries independent weight — the QA inspector who reviews a closed discrepancy reads the AT3's signature and holds it to a standard. Build the professionalism at ATSN that makes the AT3 transition feel like a continuation of habits rather than a new assignment.
FAQ

AT E1-E3 — Frequently Asked Questions

Q01What does a E1-E3 AT (Aviation Electronics Technician) actually do?
Fresh out of "A" School at NAS Pensacola or NAS Lemoore, you check into an aviation squadron — a patrol wing P-8 det, a carrier air wing F/A-18 squadron, a helicopter maritime strike (HSM) command, or a shore-based fleet readiness center (FRC) — and you enter the naval aviation maintenance program (NAMP) at the bottom of the work center.
Q02What's the most important thing to know as a E1-E3 AT?
You graduated NATTC Pensacola as an Apprentice AT.
Q03What does a typical day look like for a E1-E3 AT?
Time-blocked day at the E1-E3 AT rank tier: 0500-0600 Wake up. If on the flight line duty section, phone check for overnight discrepancies or watchbill changes. PT gear on — squadron morning PT or personal PT before report, 0600-0700 Command PT or shop PT. Aviation squadrons vary — some run unit PT on the flight line apron, some release to the gym. The ATSN who falls out of the run gets noticed. Build a baseline from week one, 0700-0800 Hygiene, chow, into utilities. Pre-quarters check: review the day's work center plan from the LPO's board,…
Q04What mistakes get E1-E3 AT soldiers fired or relieved?
ESD incident from skipping the grounding strap 'just once.' The cage log records the handler; the maintenance investigation follows the log. A latent-damaged LRU that degrades on the flight line names you at the safety review; Tool accountability failure — leaving a tool in a cockpit or avionics bay. One FOD event at the wrong moment is a Class A mishap. Your name is the last one on the checkout log. Aviation maintenance does not give second chances on tool accountability;…
Q05What career decisions matter most at the E1-E3 AT rank tier?
Which NEC pipeline to pursue — platform-specific avionics, electronic warfare, radar/fire control, or IMA depot track — The NEC decision at ATSN is the earliest career fork in the AT rate. Platform-specific NEC pipelines (tied to a particular aircraft type — F/A-18 series, E-2D, P-8A, MH-60R/S) keep you operationally embedded with the aircrew and the flight schedule. EW-focused NECs (tied to VAQ squadrons and EA-18G systems) carry the electronic warfare specialization that has strong defense-industry translation.…
Q06What's next after E1-E3 for a AT (Aviation Electronics Technician) in the Navy?
AT3 (E-4) is the first petty officer rank, and the job changes materially.
Q07What manuals and regulations does a E1-E3 AT need to know cold?
OPNAVINST 4790.2 (current series) — Naval Aviation Maintenance Program (NAMP). The bible; every maintenance action you perform lives inside this instruction.; Applicable aircraft NAVAIR technical manual series (e.g., NAVAIR 01-F18AC-2-6 for F/A-18 avionics systems — verify the applicable TM for your airframe). Step-by-step is the rule.; NAVAIR 00-80T-96 — Aircraft Mishap and Hazard Reporting Procedures (know the mishap reporting chain before you need it).

Based on 6 tips from 0 contributors

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