13.4 Flight Management Systems (FMS), Autoflight & Avionics

13.4 Flight Management Systems (FMS), Autoflight & Avionics

Modern commercial transport operations depend upon a tightly integrated suite of advanced flight management, autoflight, and terrain/traffic surveillance avionics. For the 14 CFR Part 121 aircraft dispatcher, flight planning and operational control are inseparable from these digital systems. Dispatchers input route strings, speed schedules, step climbs, and Cost Index (CI) figures directly into computerized flight plans (CFP) that synchronize with aircraft Flight Management Computers (FMC). Furthermore, understanding autoland redundancy classification (fail-passive vs. fail-operational), Class A Terrain Awareness and Warning Systems (TAWS), and Traffic Alert and Collision Avoidance System (TCAS II version 7.1) protocols is essential when planning low-visibility approach alternates and analyzing in-flight emergency deviations.

---

Flight Management System (FMS / FMC) Architecture

The Flight Management System (FMS) is the central automated navigation and performance brain of modern jet transports. The flight deck interface consists of the Control Display Unit (CDU) or Multifunction Display (MFD) keyboard, which communicates with redundant Flight Management Computers (typically FMC Left and FMC Right operating in dual synchronized mode).

Dual Database Architecture

The FMS relies on two distinct internal software databases to compute 4-dimensional lateral and vertical trajectories:

1. The Navigation Database (NDB):
   • Contains worldwide aeronautical navigation data: VOR, DME, NDB, and TACAN ground stations, RNAV waypoints, oceanic entry/exit fixes, airways, Standard Terminal Arrivals (STARs), Standard Instrument Departures (SIDs), instrument approach procedures (IAP), and runway geographic thresholds.
   • The 28-Day AIRAC Cycle: Under International Civil Aviation Organization (ICAO) Annex 15 and FAA standards, the Navigation Database is updated on a mandatory 28-day Aeronautical Information Regulation and Control (AIRAC) cycle (e.g., 2601, 2602, 2603).
   • Dispatch Operational Rule: Dispatch releases cannot be issued for RNAV or RNP routes if the onboard navigation database has expired, unless the operator's approved operations specifications (OpSpecs) and MEL authorize dispatch under strict verification procedures (e.g., cross-checking every waypoint latitude/longitude against current paper or electronic flight bag charts, with prohibited use of revised navigation procedures).
2. The Performance Database (PDB):
   • Permanently stored by the airframe manufacturer (Boeing, Airbus) and engine vendor (GE, CFM, Rolls-Royce, P&W).
   • Contains the certified aerodynamic drag polar of the airframe, engine thrust ratings (Takeoff, Maximum Continuous MCT, Maximum Climb MCL, Maximum Cruise CRZ), single-engine drift-down profiles, and fuel consumption tables across the full gross weight, Mach, and altitude envelope.

Lateral Navigation (LNAV) vs. Vertical Navigation (VNAV)

• Lateral Navigation (LNAV): Directs the autopilot/flight director roll channel to track programmed flight plan legs, including Great Circle routes, airway intersections, fly-by waypoints (smooth anticipatory turn transitions), and fly-over waypoints (mandated turn initiation directly over the fix).
• Vertical Navigation (VNAV): Directs the autopilot pitch channel and autothrottle system to manage vertical climb, cruise, and descent flight profiles:
  • VNAV SPD (Speed Mode): The autothrottle holds a commanded thrust limit (e.g., Maximum Climb Thrust during climb, or Flight Idle during descent), while the autopilot pitch channel modulates aircraft pitch attitude to maintain a constant target airspeed or Mach number.
  • VNAV PATH (Geometric Path Mode): The FMC calculates an idle-thrust geometric vertical descent path starting backward from the runway threshold or final altitude/speed constraint waypoint up to the Top of Descent (T/D). The autopilot pitches to track this rigid vertical profile. If headwinds are lighter than forecast, the aircraft will accelerate down the path, and the FMC will display "DRAG REQUIRED" on the CDU, alerting the crew to deploy flight spoilers.

Cost Index (CI) Thermodynamics & Flight Scheduling

The Cost Index (CI) is a numerical parameter entered into the FMS initialization page that mathematically balances the cost of flight time against the cost of Jet-A fuel:

$\text{Cost Index (CI)} = \frac{\text{Direct Time-Related Operating Cost (dollars/hr)}}{\text{Direct Jet-A Fuel Cost (cents/lb or dollars/100 lb)}}$

---

Autoflight & Category II/III Autoland Architecture

Commercial jet transports incorporate dual- or triple-channel autopilot and flight director systems coupled to Full Flight Regime Autothrottles.

Autothrottle Operating Modes

• N1 / EPR: Autothrottle commands and locks the thrust levers to rated takeoff, climb, or go-around thrust limits.
• SPEED / MCP SPD: Autothrottle continuously modulates thrust levers forward and aft to maintain the target airspeed set on the Mode Control Panel (MCP) or commanded by VNAV.
• ARM: Autothrottle servo clutches are energized, but the throttles are not actively driving; the crew can manually position throttles, and the autothrottle will automatically engage to provide minimum speed stall protection (Alpha-Floor or Underspeed Protection).
• RETARD: Throttles automatically retard to flight idle during the flare maneuver (at 27 to 30 feet radio altitude) during an automated approach.

Autoland Certification Standards: Fail-Passive vs. Fail-Operational

Under FAA Advisory Circular AC 120-28D and 14 CFR Part 121 OpSpecs (C059/C060), Category II and Category III precision approach autoland capabilities are strictly categorized by their system failure modes below the Alert Height (AH):

---

Terrain Awareness and Warning Systems (TAWS / EGPWS)

Controlled Flight Into Terrain (CFIT) historically represented the leading fatal accident category in commercial aviation. In response, the FAA promulgated 14 CFR § 121.354, which legally mandates that all turbine-powered airplanes operated under Part 121 must be equipped with an approved Class A Terrain Awareness and Warning System (TAWS).

Class A TAWS vs. First-Generation GPWS

First-generation Ground Proximity Warning Systems (GPWS) relied solely on downward-looking radio altimeters and barometric descent rates. They suffered from a fatal aerodynamic limitation: they could not "look ahead." An aircraft flying in level flight into a vertical mountain face received zero warning until the radar altimeter sensed the steep slope milliseconds before impact.

Class A TAWS (Enhanced GPWS / EGPWS) solves this through advanced digital integration:

1. Internal Worldwide Terrain & Obstacle Database: Digital elevation models (DEM) storing worldwide terrain topography, man-made obstacle heights (antennas, wind turbines), and airport runway layout coordinates.
2. Geometric Altitude & GPS/FMS Position: Synthesizes GPS position, inertial reference data, and geometric altitude to map aircraft position continuously against the terrain grid.
3. Forward-Looking Terrain Avoidance (FLTA): Projects dynamic "terrain caution" (20-30 seconds ahead) and "terrain warning" (15-20 seconds ahead) ribbons along the projected 3D flight path, triggering audio alerts like "TERRAIN AHEAD, PULL UP!"
4. Terrain Clearance Floor (TCF): Creates an imaginary safety envelope around every airport runway. As the aircraft approaches to land, the allowable terrain clearance floor decreases smoothly toward the runway threshold, preventing short landings or landing on incorrect terrain without flaps/gear deployed.

Classic TAWS / GPWS Warning Modes 1 Through 7

---

Traffic Alert and Collision Avoidance System (TCAS II Version 7.1)

TCAS II is an autonomous, airborne surveillance system operating completely independent of ground air traffic control radar systems, mandated under 14 CFR § 121.356 for all large commercial transports.

Air-to-Air Transponder Interrogation & Surveillance

TCAS II uses directional antennas to transmit 1,030 MHz interrogations to the Mode C and Mode S transponders of all aircraft within an approximate 40 nautical mile radius. Sensed transponders reply on 1,090 MHz. TCAS calculates range, bearing, and altitude closure rates to establish the Closest Point of Approach (CPA) and time to impact (designated by the symbol Tau / τ):

$\tau = \frac{\text{Range}}{\text{Range Rate}}$

Traffic Advisory (TA) vs. Resolution Advisory (RA)

Mode S Air-to-Air RA Coordination Link

When two aircraft equipped with TCAS II encounter a collision conflict, their Mode S transponders establish an automated, digital air-to-air datalink to coordinate complementary Resolution Advisories:

• If Aircraft A is commanded to "CLIMB, CLIMB", its transponder sends a coordination interrogation forcing Aircraft B's TCAS to command "DESCEND, DESCEND".
• This prevents catastrophic situations where both aircraft independently elect to climb or descend into each other.

Version 7.1 Upgrade: The "LEVEL OFF" Safety Command

Following mid-air collision investigations (notably the Überlingen collision), TCAS II was updated to Version 7.1:

• In earlier versions, an initial "CLIMB" or "DESCEND" RA could adjust to an "ADJUST VERTICAL SPEED, ADJUST" command, which caused dangerous pilot confusion.
• Version 7.1 replaces this with the unambiguous, clear voice command: "LEVEL OFF, LEVEL OFF", commanding the pilot to smoothly reduce vertical climb or descent speed to zero feet per minute once adequate vertical separation has been established.

Mandatory Pilot Compliance Overriding ATC Clearances

The Golden Rule of TCAS RA Operations (AIM 4-4-16 & 14 CFR Part 121): Whenever a flightcrew receives a TCAS Resolution Advisory (RA), the pilot MUST immediately comply with the TCAS RA, even if the TCAS command directly contradicts an active Air Traffic Control (ATC) heading, altitude, or clearance instruction!

Air Traffic Control radar displays do NOT show TCAS Resolution Advisories in real time. Controllers frequently issue climb or turn instructions that conflict with TCAS escape logic. Federal regulations legally indemnify pilots who deviate from an assigned ATC clearance to comply with an RA. The pilot must inform ATC as soon as possible with the standard phraseology: "[Callsign], TCAS RA." Once the traffic conflict is resolved and TCAS announces "CLEAR OF CONFLICT", the crew must promptly return to the previously assigned ATC clearance and notify ATC: "[Callsign], Clear of conflict, returning to [assigned altitude]."