Build B2 knowledge as signal chains: for each avionic system, trace the physical quantity from sensor or antenna through processing to display, attach the relevant electrical law or electronic device to each block, and practise locating faults at the boundaries between blocks rather than at the component level alone.
Aircraft DC circuits: why wiring resistance changes your Ohm's law answer
B2 electrical content expects Ohm's and Kirchhoff's laws applied to real distribution systems, where wiring and connection resistance sit in series with loads and parallel consumers share one supply.
Work the arithmetic first. A 28 V bus feeds two 13 ohm lamps in parallel through wiring totalling 1 ohm. The parallel pair is 6.5 ohms, so total resistance is 7.5 ohms, current is about 3.7 A, and the lamps see roughly 24 V, not 28 V. Kirchhoff's laws justify each step: one supply current splits between branches, and voltage drops sum around the loop.
Now compare that with the plausible mistake. Faced with a 'dim lights' report, a candidate computes per-lamp current as 28 divided by 13, calls the circuit healthy, and replaces the lamps. The better decision is to calculate the expected terminal voltage, measure it, and treat a large gap as connection resistance. That matters because crimp degradation, not the lamp, is the fault the calculation reveals.
AC fundamentals: impedance, phase, and why 38 ohms is the wrong total
The AC portion requires combining resistance with frequency-dependent inductive and capacitive reactance vectorially, because current and voltage can be out of phase and opposition to current is impedance, not resistance.
Inductive reactance rises with frequency while capacitive reactance falls, so a series circuit's impedance depends on the driving frequency. Take 10 ohms of resistance with 20 ohms inductive and 8 ohms capacitive reactance: net reactance is 12 ohms, so impedance is the square root of 100 plus 144, about 15.6 ohms, with a phase angle of roughly 50 degrees. Resonance, where the two reactances cancel, explains why tuned circuits select one frequency.
The typical error is adding all three quantities arithmetically to get 38 ohms, a method that works only for DC. The better habit is sketching the impedance triangle before any arithmetic and stating the phase relationship explicitly. This matters because filters, tuning stages, and transformer behaviour throughout the avionics syllabus rest on phase and reactance, and a wrong impedance model makes every downstream conclusion unreliable.
Electronic fundamentals: deriving device behaviour instead of memorising formulas
Analogue electronics — diodes, transistors, amplifiers, operational amplifiers — forms the bridge between circuit theory and digital systems, and each device is best learned as a transfer behaviour with defined operating regions.
Characterise each device by what it does to a signal: a diode conducts in one direction above a forward threshold; a transistor operates in cutoff, active, or saturation depending on its drive; an operational amplifier responds to the difference between its inputs, with feedback setting the overall gain. For a basic inverting amplifier, the closed-loop gain follows from the resistor ratio, and negative feedback trades raw gain for stability and bandwidth.
The mistake to avoid is treating op-amp and amplifier formulas as unrelated facts to recall under pressure. The better approach is deriving them from two assumptions — near-infinite input impedance and the output moving to null the input difference — so unfamiliar circuit arrangements become solvable on sight. That matters because the exam and real avionics both present configurations you have not seen before, and derivation transfers where memorisation does not.
Digital techniques: reading words on a bus, not voltages on a wire
Digital content covers number systems, logic gates and families, and aircraft data transmission, where information exists as encoded words and fault behaviour differs fundamentally from analogue circuits.
Practise converting fluently among binary, octal, hexadecimal, and binary-coded decimal, and reduce any gate network with truth tables rather than intuition. Then connect this to the aircraft layer: serial data buses carry structured words between units, so a healthy bus can look electrically busy while carrying corrupted data, and a physically intact wire can still deliver an unusable signal. The medium and the message are separate concerns.
That distinction suggests the layer decision in the table below. The mistake is probing a data line with a multimeter and reasoning as if it were an analogue circuit; the better decision is to use built-in test facilities and word-level interpretation where the content is digital. This matters because analoguing across layers produces confident but meaningless measurements.
| Layer | What is carried | Key concepts | Sensible analysis approach |
|---|---|---|---|
| Electrical | Current and voltage in circuits | Ohm's and Kirchhoff's laws, impedance, phase | Reduction, calculation, measurement of voltages |
| Analogue electronic | Continuously varying signals | Diodes, transistors, amplifiers, feedback | Transfer behaviour, bias and operating regions |
| Digital system | Encoded words between units | Number systems, logic, serial data buses | Truth tables, word interpretation, built-in test |
Airframe, aerodynamics, and propulsion as sensor inputs, not B1 territory
B2 candidates study structures, aerodynamics, and propulsion to understand what the avionics sense and drive — air data, angle of attack, engine parameters — rather than to certify mechanical work.
Anchor this topic to your systems. Pitot and static sources feed airspeed and altitude; temperature and angle-of-attack sensors refine air data; engine speed, temperature, and pressure sensors feed indication and control. Flight control positioning and autopilot servo interaction belong here too, because an autopilot's commands become airframe movement through actuators whose behaviour the electronics must monitor.
The mistake is skimming these subjects as someone else's syllabus and losing the physical meaning of every parameter your displays show. The better decision is to write, for each sensor, what physical quantity it converts and what physics determines that quantity. This matters because fault-isolation questions place symptoms exactly at the boundary between physics and electronics, and a candidate who cannot describe the physical side cannot judge whether an indication is plausible.
Communication, navigation, instruments, and autoflight as one method, not four subjects
Each system is a chain from antenna or sensor through processing to display or servo, and the disciplined method is to identify what physically crosses each block boundary before attempting fault isolation.
Take a navigation receiver as the model: an antenna captures a radio signal, the receiver filters and demodulates it, processing extracts the guidance information, and an indicator presents it. Instruments split along the same seams — gyroscopic sources versus pitot-static sources — and autoflight adds mode logic and servo outputs to chains you already understand. Build one such chain per system and annotate what form the signal takes at every arrow.
Worked scenario: a pilot reports the heading display disagreeing with the magnetic compass. The plausible mistake is swapping the display unit first, an unverified part change that may not touch the fault. The better decision is to check the sensor's excitation and output at the coupling point, compare against a known-good reference, and only then isolate the display. It matters because undisciplined swapping wastes serviceable units and mirrors exactly the human-factor traps the syllabus describes.
Practical exercise with expected observations: draw the full chain for one navigation and one instrument system, then for each block write the input form, the output form, and the law or device that governs the block. Self-check rubric — score one point each: (1) every block has a named input and output; (2) you can state one governing principle per block; (3) you can name two test points where you would distinguish a sensor fault from a display fault; (4) you can predict what the display shows if one chosen block fails. Four of four suggests the chain is genuinely connected; revisit any block that only earns a label.
Legislation, human factors, and a preparation sequence that ties the layers together
This area covers how maintenance is organised and certified under UK regulatory oversight, and how human capabilities, limitations, and error chains shape maintenance outcomes, so study it as working practice rather than trivia.
Treat human factors content as a set of named concepts to apply: error models, situational awareness, communication and workload pressures, and how small lapses combine into incidents. Practise by taking your heading-indicator scenario and labelling which human-factor pressures would push a technician toward the unverified part swap. Legislation content is best learned as roles and responsibilities — regulator, approved organisations, certifying staff — rather than as isolated clauses.
The mistake is leaving this area to the final week as memory work. The better decision is interleaving it with technical scenarios from the start, since every fault-isolation decision doubles as a human-factors case. For administrative specifics such as application requirements, consult the UK Civil Aviation Authority directly; this guide addresses study content only. Note also that this overview does not restate current official document versions — verify anything regulation-dependent against the issuer.
Adaptable preparation sequence: Phase 1 — rebuild DC and AC fundamentals with the reduction and impedance-triangle habits until calculations feel routine. Phase 2 — cover analogue and digital electronics, deriving device behaviour and practising number systems and truth tables. Phase 3 — build one signal chain per avionic system and attach airframe, aerodynamic, and propulsion knowledge to the sensor blocks. Phase 4 — consolidate with legislation and human factors interleaved into scenario work. Stretch or compress phases by your own diagnostic results, not by a fixed calendar; a candidate strong in electronics may spend most time in Phases 1 and 3.
- Readiness check 1: you can solve the parallel-load and impedance examples in the earlier sections without notes and explain each step as a named law.
- Readiness check 2: for any system you name, you can draw its signal chain within a few minutes and mark where sensor faults, processing faults, and display faults separate.
- Readiness check 3: given a symptom, you can state which layer — electrical, analogue, or digital — the first diagnostic step belongs to, with a reason.
- Readiness check 4: you can apply a human-factors concept to a technical scenario and describe how it changes the decision, not just recite the definition.
- These checks are learning milestones for your own tracking; they indicate study progress, not a prediction of any exam outcome.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.