NCATT AET common mistakes
NCATT AET · Understand the traps and how to avoid them.
When reducing a series-parallel network, the candidate collapses resistors across parallel branches as if they were in series (or adds branch currents as if they were voltages), then carries the wrong value forward through the rest of the problem and reports a final answer that is internally inconsistent.
Candidates memorize 'add resistors in series' and 'add reciprocals in parallel' as isolated rules but never redraw the circuit to mark nodes and identify which elements actually share the same current path versus the same voltage. Under exam time pressure they pattern-match on how the schematic looks rather than on node connectivity.
What to do instead
Before any arithmetic, redraw the circuit twice: once marking series elements (same current, no junction between them) and once marking parallel elements (same two nodes). Write the reduction step by step with units attached, then sanity-check the result: total resistance of a network must be greater than the largest series element and less than the smallest parallel branch.
The candidate mixes current directions and sign conventions mid-problem, assigns voltage drops with polarities that contradict the assumed current arrow, and then treats the resulting negative number as a calculation error rather than as a physically meaningful result.
Training material sometimes uses electron flow and sometimes conventional current without stating which, so candidates flip conventions halfway through a Kirchhoff loop or a diode/transistor problem. A negative result then triggers guessing and rework instead of interpretation.
What to do instead
Declare the convention at the top of the work: conventional current, positive terminal to negative through the load, current entering a resistor at the positive end. Keep one direction arrow per loop and never flip it mid-solve. Treat a negative answer as evidence that the actual direction opposes the assumed arrow, and state that explicitly in the answer.
The candidate selects a wire or terminal using only the conductor gauge and ignores derating factors, insulation temperature rating, bundle size, altitude/high-altitude current derating, or the fact that a higher AWG number means a smaller conductor.
Gauge tables are memorized as a single 'ampacity' number, so the candidate treats the wire-selection problem as a lookup rather than as a multi-variable decision. The inverse AWG numbering also causes silent reversal errors in a hurry.
What to do instead
Work the selection as an ordered checklist every time: current required, ambient and bundle derating, altitude correction, insulation temperature rating, voltage drop over the run length, then gauge. Confirm the direction of AWG (larger number = smaller cross-section) with a circular-mil value before committing. Terminal selection follows: wire gauge, stud size, insulation style, and the correct crimp die for that terminal family.
The candidate terminates a shielded cable by grounding the shield at both ends, or leaves a shield floating, or dresses a coax or signal bundle running parallel and tightly bundled with a high-current power feeder.
Shields and separation are taught as 'good practice' rather than as a specific electrical function, so candidates cannot predict the consequence (ground loops carrying circulating current, or inductive coupling of noise into a low-level signal) and therefore cannot choose correctly when the question describes a scenario rather than a rule.
What to do instead
Learn the function behind each rule: the shield is grounded at one point to intercept interference without creating a return path for circulating current; separation and crossing at right angles minimize inductive coupling. When a question describes a symptom (noise on a low-level signal, intermittent audio), trace it back to the physical routing and termination decision that caused it.
The candidate measures resistance or continuity with the circuit energized, or with the component still connected in a network where parallel paths shunt the meter, and then declares the component 'good' or 'shorted' based on the displayed value.
Continuity checks feel binary and safe, so candidates skip the isolation step. Parallel return paths through airframe structure and ground straps are invisible on the schematic the candidate is holding, and a powered circuit can also damage the meter or produce a plausible but meaningless reading.
What to do instead
State and follow the isolation rule on every resistance test: power removed, component disconnected at least one end, meter zeroed or leads compensated. For airframe bonding and return-path checks, identify all parallel paths before interpreting the reading, and compare against the specified resistance limit rather than an eyeballed 'beep'.
The candidate troubleshoots by swapping suspected components one at a time, or trusts a meter reading without regard to the instrument's limitations (burden voltage, crest factor, true-RMS versus averaging, autorange settling, or an AC range used on a DC signal).
Component swapping feels productive and mirrors hangar habits, while meter specifications are treated as fine print. The candidate also assumes any meter reading is the circuit's actual value, so an averaging meter on a distorted waveform or a low-impedance range loading a high-impedance node produces a confident wrong diagnosis.
What to do instead
Use a divide-and-conquer approach: verify power and ground at the load first, then split the circuit at its midpoint and test which half holds the fault, halving the search area each step. Before trusting a number, state what the meter is actually measuring and whether its accuracy and input impedance suit that node; use a true-RMS meter for non-sinusoidal or switching signals.
The candidate describes a digital databus with the wrong physical or logical characteristics, for example treating a one-way, single-transmitter bus as bidirectional, confusing a bus controller/remote terminal architecture with a peer-to-peer one, or mixing bit and byte counts when computing message length or data rate.
Bus specifications are absorbed as a list of names and numbers with no mental model of the wire, the direction of data flow, or the addressing scheme, so closely related buses blur together during recall. Unit confusion compounds the error when calculating throughput.
What to do instead
Build a one-page comparison table per bus covering: number of wires, direction of data flow, how many transmitters can share the bus, word/label structure, data rate, and error detection. Anchor bit-versus-byte by always converting to bits before computing rate (bits per second = words per second x bits per word).
The candidate converts between binary, decimal, and hexadecimal by dropping or misplacing the least significant bits, or misreads a two's-complement negative value as a large positive number, and then answers the follow-on question with that value.
Conversion is done mentally without place-value columns, and the candidate has no habit of validating the result; two's-complement notation in particular looks like an ordinary magnitude value if the sign bit is not deliberately considered.
What to do instead
Write the place-value columns (128, 64, 32, 16, 8, 4, 2, 1, or powers of 16) for every conversion, group binary into nibbles from the right when converting to hex, and state the word width explicitly before applying two's complement. Verify by converting back to the original base.
The candidate explains a stall as a function of airspeed alone (a fixed 'stall speed'), or conflates angle of attack with pitch attitude, and does not account for load factor, weight, or configuration when judging performance and structural limits.
Everyday flying language ties stall to speed, so the underlying aerodynamic cause (exceeding the critical angle of attack) gets replaced by a memorized number. Pitch attitude and angle of attack look similar from the cockpit, and load-factor effects are abstract until worked numerically.
What to do instead
Re-anchor on the cause: a stall occurs when the wing exceeds its critical angle of attack, at any airspeed, attitude, weight, or bank angle. Work load-factor problems as ratios (load factor equals lift divided by weight) and note that stall speed rises with the square root of load factor, so a level 60-degree bank raises stall speed by roughly 40 percent.
When installing avionics line-replaceable units, the candidate routes or secures hardware from habit, bending a coax beyond its minimum radius, using unapproved fasteners or non-factory connector pins, torquing to 'feel', and working without citing the approved maintenance or installation data in the answer.
Installation questions are treated as general workmanship rather than as questions about compliance with specific published limits. The candidate has hands-on habits from the hangar but has not internalized that bend radius, fastener part number, pin part number, torque value, and separation are all specified numbers traceable to approved data.
What to do instead
For any installation item, answer from the controlling document: identify the approved data source first, then state the specific limit (bend radius, torque, separation distance, fastener and contact part numbers). Treat 'snug by feel' and unspecified hardware as automatically wrong, and remember that a substituted connector contact or fastener is an airworthiness issue, not a convenience.