Instrumentation
The full EASA ATPL(A) Instrumentation syllabus, taught properly: sensors and engine instruments, air data, compasses, gyros, inertial navigation, automatic flight, communications, flight management, alerting systems and electronic displays — every learning objective explained, with the instrument behind every cockpit indication.
How the aircraft measures itself: the sensor families behind every gauge (pressure capsules and bourdon tubes, temperature probes, fuel gauges and flowmeters, tachometers, thrust and torque indication) and how to read each one, including what it means when the reading is wrong.
Every number in the cockpit starts as a physical effect on a sensor: a capsule squeezed, a resistance changed, a tube uncurled. This first module walks through the measurement chains behind the basic gauges, above all the engine instruments, because reading them and mistrusting them correctly is tested throughout the subject. The air-data instruments, which turn pressure into altitude and speed, get the next module to themselves.
The instruments that turn air pressure into flight information: the pitot-static system and its errors, temperature and angle-of-attack sensing, the altimeter and its settings, the VSI, the ASI and its speed ladder, the Machmeter, and the air-data computer that digests them all.
This is the module the first lesson of the course promised: the instruments built on nothing but air pressure. A handful of holes in the aircraft's skin feed the altimeter, the vertical speed indicator, the airspeed indicator and the Machmeter, and the whole chain stands or falls with the honesty of those pressure sources. The module therefore starts at the sources themselves, the pitot-static system, before a single instrument is opened.
Where heading comes from: the Earth's magnetic field with its variation and dip, the aircraft's own magnetism and the deviation it causes, the direct-reading compass with its manoeuvre errors and timed turns, and the flux valve that senses the field electrically for the remote systems.
Every magnetic heading in the cockpit descends from one physical fact: the Earth drags a magnetic field across its surface, and a free magnet aligns with it. This module follows that fact into the instruments — first the field itself and the two angles that complicate it, then the aircraft's own magnetism spoiling the measurement, then the two sensors that read the field: the pilot's direct-reading compass and the electrical flux valve that feeds everything else.
The instruments built on a spinning wheel's stubbornness: gyro rigidity and precession, the turn indicators, the attitude indicator, the directional gyro and its drifts, the remote-reading compass that marries gyro to flux valve, and the solid-state AHRS that replaced them all in one box.
Magnetism gave the aircraft direction, and pressure gave it height and speed; what neither can give is a reference that holds still while the aircraft manoeuvres around it. That reference is the gyroscope: a wheel spun fast enough that its axis resists being moved. This module builds the principle first, then the three classic instruments that stand on it, and ends where the magnetism module pointed: the remote-reading compass that welds gyro and flux valve together, and the solid-state unit that replaced the spinning wheels entirely.
How an aircraft navigates with no outside reference at all: accelerometers and double integration, the four corrections that keep the sums honest, the platform INS and the strap-down IRS, the ring laser gyro, the alignment ritual that must finish before the wheels move, and the panels the pilot runs it with.
Module 4 ended with the AHRS: gyros and accelerometers gone solid-state, delivering attitude and heading. This module is built from the same two ingredients and a harder ambition. An attitude and heading reference system stops at attitude and heading, leaning on a magnetic sensor to hold its heading honest; an inertial navigation or reference system carries sensors good enough to be trusted with navigation itself, summing its own accelerations, hour after hour, into velocity and position with no help from outside. The first lesson builds the principle and the hardware; the second covers the alignment that makes it work and the panels the pilot works it with. This is also where module 2's promise is kept: the air-data half of the ADIRU met there finally gets its inertial half.
From the closed control loop to the machines built on it: the autopilot and its channels, the flight director that advises instead of acting, automatic landings and their fail categories, the trims and yaw damper working in the background, envelope protection, and the autothrust that flies the speed.
Every module so far built senses: pressure, temperature, direction, rotation, acceleration. This module hands those senses to machinery. An automatic flight control system takes the measured state of the aircraft, compares it with the state the crew has asked for, and moves the controls to close the gap, tirelessly and many times a second. The module starts with the one idea underneath all of it, the closed control loop, and then climbs the ladder: the autopilot that flies, the flight director that advises, the automatic landing that finishes a flight in fog, the quiet background workers (trim, yaw damper, envelope protection), and the autothrust that owns the speed.
How the aircraft talks: the three radio links and their characters, the shift from voice to data link, the ACARS network with its boxes and messages, and the future air navigation systems (FANS) framework of data-link clearances and surveillance contracts.
Every system so far has measured, computed or flown; this short module is about the aircraft speaking. Two lessons: first the links themselves, VHF, HF and satellite, and the ACARS network that turned the aircraft into a node that sends and receives text; then the future air navigation systems (FANS) framework built on top of it, where clearances arrive as messages and surveillance happens by contract. This is also where module 1's promise is kept: the ACARS that time-stamps the clock lesson's records finally gets explained.
The system the whole course has been feeding: what an FMS is and how its dual architecture survives failures, the two databases underneath it and the rules that protect them, how it fixes its own position and predicts the flight, and the CDU/MCDU through which the crew works it all.
Half the systems in this course have ended their story with the same hand-off: the inertial module supplies raw motion data to the FMS, the autopilot flies LNAV and VNAV from the FMS, ACARS carries the FMS's world to the ground. This module finally opens the box. The promise made in the inertial module is kept here, starting with the names:
the flight management system (FMS) is the whole system.
the flight management computer (FMC) is the computer inside it.
the flight management and guidance system (FMGS) is the same idea under its other common name, an FMS that also embraces the guidance function.
The first lesson covers the design and the two databases; the second, the operations, their limits, and the CDU/MCDU the pilot works it with.
The systems that speak up: the alerting hierarchy and the flight warning system behind the master lights, the stall, overspeed and configuration warnings, the radio altimeter and the ground proximity warnings built on it, and the traffic collision avoidance system that watches the sky around the aircraft.
Everything so far has measured, flown or managed; this module is about the systems whose whole job is to interrupt. Four lessons: the alerting rulebook and the flight warning system that runs the master lights; the warnings guarding speed and configuration; the radio altimeter, promised since the autoland lesson, and the ground proximity warnings that stand on it; and the collision avoidance system that watches every transponder around the aircraft and, when it must, commands the escape.
The screens of the modern flight deck: the display technologies and the mechanical integrated instruments they replaced, the electronic flight instrument system with its primary flight display and navigation display, and the system displays, electronic flight bag, head-up display and vision systems that complete the picture.
Almost every system taught so far has ended its story at a screen it never described: the engine parameters of module 1 were left on an engine page the module never drew, the alerting lesson parked its advisories on a central annunciation display, and the terrain warning lesson painted its threat picture on a navigation display taken on trust. This module closes those gaps. Three lessons: the display technologies themselves and the two mechanical integrated instruments the electronic flight deck grew from; the electronic flight instrument system, with the primary flight display and the navigation display in full; and the system displays, the electronic flight bag, the head-up display and the vision systems that finish the flight deck.
The course's closing module: the cockpit voice recorder and flight data recorder that preserve what happened, the aircraft condition monitoring system and the flight data monitoring programme that watch trends before anything happens, and the digital computer fundamentals that name what every system in this course has quietly been.
Every system so far has measured, flown, warned or displayed for the crew in the moment. This last module is about what the aircraft keeps and what the aircraft is. Two lessons: first the recorders, the cockpit voice recorder and flight data recorder built to survive an accident and tell investigators the truth, and the condition monitoring that reads the same kind of data every day for maintenance and safety trends; then the digital computer itself, the definitions and the buses, and the recognition that the air-data computers, flight management systems and warning computers of this course were examples of one machine all along.