You're Not Flying the Jet Anymore
In military aviation, the pilot flies the aircraft. Even in aircraft with advanced autopilot systems, the culture values stick-and-rudder skills. You hand-fly departures. You hand-fly approaches. You click off the autopilot and fly the pattern. Stick time is currency, and the best pilots pride themselves on their ability to hand-fly precisely.
At the airline, that mental model inverts.
Manage, don't fly
the foundational philosophy of airline automation — you supervise the systems that fly the aircraft
FAA Advisory Circular 120-71B, Standard Operating Procedures and Pilot Monitoring
The airline wants you managing the automation, not flying the aircraft. Autopilot on at 400 feet after takeoff. Autothrust engaged from takeoff to landing. Flight Management System (FMS) managing the lateral path, the vertical path, the speed targets, and the performance calculations. Your job is to tell the automation what to do, monitor that it's doing it, and intervene when it doesn't.
This is not because airlines think you can't fly. It's because decades of accident data have shown that automation management produces more consistent, more precise, and safer outcomes than hand-flying — especially in complex operational environments with traffic, weather, and fatigue.
The FMS: Your New Mission Computer
The Flight Management System is the brain of airline automation. You program it on the ground with your route, performance data, and approach. In flight, it manages your lateral navigation (LNAV), vertical navigation (VNAV), and speed targets. It calculates top-of-descent points, fuel predictions, arrival times, and approach speeds.
If you flew military aircraft with mission computers, you have a conceptual framework for the FMS. But airline FMS systems are significantly more complex than most military equivalents, and the way you interact with them is fundamentally different.
Programming scope
Mission computer or nav system programmed with waypoints, targets, and weapons data. Often pre-loaded or simple.
FMS programmed with full route (SID, enroute, STAR, approach), performance data (weights, wind, temperature), and cost index. Reprogramming in flight is routine.
In-flight changes
Route changes are mission-driven. Often manual navigation when tactical situation demands.
Route changes from ATC are constant. Vectors, direct-to, amended clearances, runway changes. You reprogram the FMS while managing the current flight path.
What it controls
Navigation display and weapons targeting. Rarely controls the flight path directly.
Controls lateral path, vertical path, speed, thrust, and descent profile. The FMS IS the flight path in managed mode.
Level of trust
Trust your instruments and your hands. The pilot is the final common pathway.
Trust the automation unless you have reason not to. Monitor, verify, intervene only when needed.
Heads Up
The FMS is the number one study priority after memory items and flows. If you can't program a route change, insert a hold, or modify an approach in the FMS, you will fall behind in the simulator immediately. Your sim partner will be reprogramming the box while you're still looking for the right page.
Managed vs. Selected Modes
This concept has no direct military equivalent, and it's the one that takes the longest to internalize.
In managed mode, the automation follows the FMS flight plan. Lateral path, vertical path, speed — all computed by the FMS, all executed by the autopilot and autothrust. You told the FMS what to do during programming. Now it's doing it. Your job is to monitor.
In selected mode, you override the FMS and manually set a target. You dial in a heading, an altitude, a speed. The autopilot flies to your manually selected target instead of the FMS-computed one. You're still not hand-flying — the autopilot is engaged — but you're directing it manually rather than letting the FMS direct it.
Managed mode
No direct equivalent. Closest would be a coupled approach where the nav system flies the approach.
FMS-computed targets. Autopilot follows the programmed route, altitude constraints, and speed schedule. Pilots monitor.
Selected mode
Closer to what you're used to — setting a heading, altitude, or speed manually on the autopilot panel.
Pilot-selected targets on the flight control unit (FCU/MCP). Overrides FMS guidance. Used for ATC vectors, non-standard situations.
When to use which
You fly how the situation demands. Flexibility is valued.
Managed mode is the default. Selected mode is for ATC vectors, deviations, or when the FMS can't handle the situation. Returning to managed mode as soon as practical is the expectation.
The key insight: managed mode is the default, not selected mode. At the airline, you should be in managed mode whenever possible. Going to selected mode is fine — ATC will vector you regularly — but you should always have a plan to get back to managed. The FMS knows the route, the constraints, the speeds. Let it do its job.
The mode awareness trap
The most dangerous moment in airline flying is when you think the automation is doing one thing and it's doing another. This is called a mode error, and it has contributed to fatal accidents. Every time you change a mode — managed to selected, or vice versa — verify what the automation is actually doing. Read the flight mode annunciator (FMA) on the primary flight display. Say it out loud. Make sure your partner confirms it.
The Autothrust Habit
Most military aircraft don't have autothrust. You manage the throttles manually — power on, power off, adjustments by feel and by gauge. You develop a throttle hand that knows where to set the power for a given flight condition.
At the airline, autothrust manages the throttle levers for you. It adjusts thrust to maintain the target speed — whether that target comes from the FMS (managed speed) or from your manual selection (selected speed). The throttle levers move on their own. Your hand is not on them during most of the flight.
This feels deeply wrong at first. Every instinct you've built over thousands of hours says your hand should be on the throttles. Trusting a computer to manage your thrust — especially during approach and landing — requires a conscious override of your training.
Insight
Here's the reframe: autothrust is not removing your control. It's adding a layer of precision. Autothrust maintains speed more accurately than any human pilot can, especially during approach in gusty conditions. Your job is to monitor that it's commanding the right speed and intervene if it isn't — not to do its job for it.
Hand-Flying: When You Do Get to Fly
Airlines are not anti-hand-flying. Most airlines actually encourage hand-flying during certain phases — low-altitude, visual conditions, calm weather. It maintains proficiency and satisfies the FAA's requirement that pilots demonstrate manual flying skills.
But the window for hand-flying is narrow compared to the military. You might hand-fly from the runway to 1,000 feet on departure, or from 1,000 feet to the runway on approach. That's it. The rest of the flight — potentially 4+ hours — is autopilot.
Hand-fly expectations
Valued. Many pilots hand-fly whenever conditions permit. Stick time is important for proficiency and pride.
Acceptable within SOP limits. Most airlines allow hand-flying below 10,000 feet in VMC. Above that, autopilot is the expectation.
During training
You demonstrate proficiency by hand-flying to standards.
You demonstrate proficiency by managing automation AND hand-flying to standards. Both are graded. Automation management is often the bigger discriminator.
When things go wrong
Disconnect everything and fly the jet. 'Aviate, navigate, communicate' means you fly first.
Assess whether the automation can still help. Sometimes the right answer is to leave the autopilot on while you troubleshoot. Sometimes it's to click it off. The decision depends on the failure.
Heads Up
Don't interpret the automation philosophy as "never hand-fly." That's not what the airline is saying. They're saying: use the right tool for the situation, and most of the time, the right tool is the automation. But when you do hand-fly, you need to be sharp. Practice hand-flying to airline standards — centerline, glideslope, speed — because when you do get the chance, the standards are exacting.
VNAV: The Vertical Dimension
If there's one automation concept that causes more confusion than any other, it's VNAV — Vertical Navigation.
VNAV is the FMS managing your vertical path: climbs, descents, level-offs, altitude constraints at waypoints. In managed vertical mode, the FMS commands pitch and thrust to follow a computed vertical profile — climbing at the optimal speed, beginning descent at the computed top-of-descent point, meeting altitude constraints at each waypoint.
The complexity comes from the modes within VNAV:
- VNAV SPD — the FMS is targeting a specific speed, letting altitude vary
- VNAV PTH — the FMS is following a computed path, adjusting speed to stay on it
- VNAV ALT — the FMS has captured a target altitude and is leveling off
Each mode behaves differently. Each handles thrust differently. And the transitions between modes happen automatically, often without the pilot commanding them. Understanding which VNAV mode you're in — and which one you're about to transition to — is essential.
Tip
VNAV is where mode awareness matters most. The Flight Mode Annunciator (FMA) at the top of your Primary Flight Display (PFD) tells you exactly what mode the automation is in. Get in the habit of reading the FMA every time something changes — altitude, speed, or configuration. When the FMA changes, announce it out loud. Your PM should do the same.
Why Military Pilots Struggle With Automation
1. The instinct to hand-fly. When things get busy or uncertain, your trained response is to take the controls. At the airline, the trained response is often to leave the automation on and manage the situation from a higher level. Fighting this instinct takes conscious effort.
2. The "false familiarity" trap. If you flew glass cockpits (F-35, F/A-18E/F, C-17, MV-22), you'll assume your automation experience carries over. It doesn't — the logic, modes, and philosophy are different enough to breed overconfidence. If you hand-flew everything (older fighters, helos), you're starting from zero on automation trust. Different starting points, different pitfalls — neither one is automatically better.
3. Programming under pressure. The FMS must be reprogrammed in real time when ATC changes your route, your runway, or your approach. This requires fine motor skill (typing on a small keyboard), system knowledge (which page, which function), and timing (doing it while the aircraft is moving). The military rarely required this level of real-time reprogramming.
4. Energy management shift. You're used to managing energy directly — throttle, configuration, speed brakes, power by feel. At the airline, autothrust and VNAV handle that. Your job goes from doing the energy management to watching the automation do it. Completely different mental model. The instinct to grab the throttles when the speed looks wrong takes months to override.
5. Trust. You need to trust the automation to fly the aircraft while you manage the big picture. Military pilots are trained to trust themselves. Transferring that trust to a computer feels like abdicating responsibility — but it's not. You're still responsible. You're just delegating the execution while retaining the oversight.
6. Mode awareness. With multiple automation modes, transitions between modes, and different behaviors in each mode, keeping track of what the automation is doing requires constant attention. The FMA is your primary tool. If you can't read the FMA instantly and understand what the aircraft is about to do, you're behind the automation.
Getting Ahead
-
Study the FMS. Whatever aircraft you're training on, the FMS is your priority after memory items, flows, and callouts. Learn the page structure, the most common operations (route entry, direct-to, approach selection, hold programming), and the button layout.
-
Learn the automation modes. Managed vs. selected. LNAV/VNAV/speed modes. What each mode does, what triggers transitions between modes, and what the FMA annunciations look like.
-
Practice mode callouts. Every time the FMA changes, the PM should call it. Practice saying mode changes out loud during chair flying: "VNAV PTH, FMS SPD." This builds the habit.
-
Recalibrate your instincts. When your gut says "disconnect and fly," pause. Ask: is the automation helping or hurting right now? If it's helping, leave it on. If it's not, take over. But make the decision consciously, not reactively.
-
Accept the philosophy. You're not a worse pilot because you use automation. You're a more effective operator. The airline is paying you for judgment, decision-making, and systems management — not for your ability to hold a heading within a degree by hand.