Avionics, Navigation & Air Data Systems
The electronic nervous system of an aircraft. Learn the flight instruments and air data (pitot-static, AoA vanes, ADIRU), inertial navigation (IMU, gyros, accelerometers, drift), GNSS and augmentation (SBAS, RAIM), radio navigation (VOR, DME, ILS), sensor fusion, communication and surveillance (VHF, SATCOM, transponders, ADS-B, TCAS), glass cockpits and flight management systems, avionics data buses (ARINC 429, AFDX, MIL-STD-1553) and integrated modular avionics — with Python converting pitot pressure to airspeed.
Avionics ('aviation electronics') tell the crew and the automation where the aircraft is, how fast it's going, what attitude it's in, and what is around it — and carry the commands that fly it. A modern airliner has hundreds of avionics functions and millions of lines of certified software.
Navigation has evolved from compasses and radio beacons to inertial systems blended with satellite navigation, enabling precision approaches and performance-based navigation (RNP) worldwide.
An analogy
Avionics are the aircraft's senses and brain: pitot tubes are its ears feeling the wind, gyros its inner ear sensing rotation, GNSS its map-reading, radar its eyes, and the flight management system its planner.
The basic six and the glass cockpit
Traditional instruments: airspeed indicator, attitude indicator, altimeter, turn coordinator, heading indicator, vertical speed indicator. Modern glass cockpits combine them on a primary flight display (PFD) and navigation display (ND), with engine/system displays (EICAS/ECAM) and head-up displays.
Navigation sensors
Complementary sources:
- Inertial (IRS/INS) — ring-laser or fibre-optic gyros + accelerometers; self-contained, smooth, but drifts (~1 nm/h)
- GNSS (GPS, Galileo, GLONASS, BeiDou) — accurate, global; vulnerable to jamming/spoofing; augmented by SBAS (WAAS, EGNOS, GAGAN) and checked by RAIM
- Radio aids — VOR (bearing), DME (distance), NDB, ILS (localiser + glideslope for precision approaches)
- Radar altimeter — height above terrain for landing and autoland
- Hybrid INS/GNSS fusion with Kalman filters combines strengths
Communication and surveillance
VHF voice and CPDLC datalink, HF and SATCOM over oceans; transponders (Mode S) answer ground radar; ADS-B broadcasts GNSS position every second; TCAS uses transponder replies to compute collision risk and issues resolution advisories; weather radar and EGPWS/TAWS terrain warnings protect against the environment.
Architecture, buses and certification
Federated avionics (one box per function) gave way to Integrated Modular Avionics (IMA): shared computing cabinets running partitioned applications (ARINC 653). Data flows on ARINC 429 (point-to-point, 100 kbit/s), MIL-STD-1553 (military, command/response) and AFDX/ARINC 664 (switched deterministic Ethernet). Software is certified to DO-178C (DAL A–E), hardware to DO-254, environment to DO-160. The flight management system (FMS) holds the navigation database, computes the route, performance and VNAV profile, and drives the autopilot.
Formulas
- Equivalent airspeed (incompressible):
EAS = √(2q_c/ρ₀) - True airspeed:
TAS = EAS/√σ - Pressure altitude (troposphere):
h = (T₀/L)·[1 − (p_s/p₀)^(RL/g₀)] - INS position error (gyro drift):
grows roughly with time (Schuler 84-min oscillation + drift) - GNSS range:
ρ = c·(t_rx − t_tx) = |r_sat − r_user| + c·δt - Wind triangle:
GS⃗ = TAS⃗ + wind⃗
Worked example: Altitude from static pressure
Given: p_s = 70.1 kPa
Find: Pressure altitude.
- h = 44 331 × [1 − (70.1/101.325)^0.1903]
Answer: ≈ 3000 m (FL100)
Worked example: Wind correction
Given: TAS 120 m/s heading north, wind 20 m/s from the west
Find: Ground speed and drift.
- GS = √(120² + 20²)
- drift = atan(20/120)
Answer: 121.7 m/s, 9.5° right drift
Worked example: INS drift
Given: 1 nm/h, 10 h oceanic crossing without updates
Find: Error.
- ≈ 1 × 10
Answer: ~10 nm — why GNSS/radio updates are used
From pitot pressure to true airspeed and ground speed
import math
# Pitot-static: indicated -> true airspeed (incompressible approximation)
rho0 = 1.225
def isa_rho(h):
T = 288.15 - 0.0065 * h
return 1.225 * (T / 288.15) ** 4.256
q = 3000.0 # measured dynamic pressure, Pa
EAS = math.sqrt(2 * q / rho0)
for h in (0, 3000, 10000):
TAS = EAS * math.sqrt(rho0 / isa_rho(h))
print(f"h={h:5d} m: EAS {EAS:.1f} m/s, TAS {TAS:.1f} m/s")
# Ground speed with 20 m/s headwind
print(f"ground speed at 10 km with 20 m/s headwind: {EAS*math.sqrt(rho0/isa_rho(10000))-20:.1f} m/s")
# h= 0 m: EAS 70.0 m/s, TAS 70.0 m/s
# h= 3000 m: EAS 70.0 m/s, TAS 81.2 m/s
# h=10000 m: EAS 70.0 m/s, TAS 120.6 m/s
# ground speed at 10 km with 20 m/s headwind: 100.6 m/sThis is what an air data computer does (with full compressible equations and calibrations). Blocked pitot tubes (icing, insects) corrupt airspeed — a factor in accidents such as AF447 — which is why aircraft carry three independent air data systems and synthetic airspeed monitoring.
Common mistakes
- Wrong: Trusting a single airspeed source. — Right: Cross-check three ADIRUs; follow unreliable-airspeed procedures.
- Wrong: Assuming GNSS is always available. — Right: Plan for jamming/spoofing with INS and radio aids.
- Wrong: Wrong altimeter setting. — Right: Set QNH below transition altitude, 1013.25 hPa above.
Applications
- RNP approaches: Curved GNSS approaches into terrain-constrained airports.
- Autoland: CAT III ILS landings in fog.
- Drones: MEMS IMU + GNSS autopilots.
- Military: Jam-resistant INS/GNSS, terrain-referenced navigation.
Key takeaways
- Air data: pitot + static → airspeed, altitude, Mach.
- INS drifts; GNSS bounds it; fuse with Kalman filters.
- Surveillance: transponder, ADS-B, TCAS.
- IMA, AFDX and DO-178C underpin modern avionics.
Going further
- Synthetic vision: Terrain databases rendered on the PFD.
- GNSS spoofing detection: Multi-constellation, antenna arrays, INS consistency checks.
- Optical/vision navigation: Camera-based navigation for drones and landers.