People who work around aircraft hear the word “alternate” so often that it becomes background noise. Yet the idea behind it applies to far more than a landing airport. A small flight school, a maintenance shop or a flying club can all decide ahead of time what happens when the first option fails. What follows are frequently asked questions from pilots, students and ground crew, each given a direct reply. Keep in mind that this is general guidance on planning habits; operating rules, manuals and your own organisation’s procedures always come first.
What exactly is an aviation plan B?
It is a second course of action chosen in advance, together with the sign that tells you to use it. The sign matters as much as the course. “Use the other runway if the wind is too strong” is a plan B only when someone has said how strong is too strong and who decides. Without that, you have a wish.
Is a plan B the same as an alternate airport?
An alternate airport is one famous example, but the habit stretches beyond it. In day-to-day flying operations, fallbacks show up in many forms: a second briefing time when the first is missed, a different aircraft when one is held for maintenance, a paper copy of a checklist when a tablet fails, or a different lesson plan when the weather turns. Each one answers the same question: what do we do if this particular thing does not work?
Where should a small organisation start?
Start with the points where a single item decides whether the day runs. List them on one page: the aircraft, the instructor, the briefing room, the fuel supply, the weather window, the key person who signs things off. Then mark the ones that have no second option. Those are your priorities. Do not try to cover everything; two or three well-chosen fallbacks outperform a dozen vague ones.
How do we choose the trigger?
Pick something observable and time-bound. A reading on an instrument, a message from a particular person, or a clock time all work. Avoid triggers based on mood or hunches, because they invite argument at the worst moment. A good test: could two people look at the same situation and agree on whether the trigger has fired? If yes, it is a good trigger.
Who should decide when the switch happens?
One named role, with a named stand-in. That does not mean everyone else stays silent; observations from the line crew, the instructors and the students all feed in. But a single decider prevents a committee debate while time runs out. Write the role into the plan and tell everybody who holds it that day.
Do fallbacks need to be as good as the main plan?
No, and expecting that makes people give up. A fallback has to meet the purpose of the activity, not the full comfort of the original. If the purpose of a training flight is to practise circuits, a simulator session may serve a limited purpose on a bad-weather day. If the purpose is to complete a ground subject, a classroom hour will do. Decide the purpose first, then ask what the least costly acceptable substitute is.
How often should the list be reviewed?
A quick monthly look is enough for most small teams, and a deeper review after any disruption. Fallbacks go stale: a contact leaves, a field closes, a spare part supplier changes. An out-of-date fallback can be harmful, since it lets people feel covered when they are not. When you use a fallback in real life, spend ten minutes afterwards noting what worked, and update the page.
What about people outside the organisation?
Include them. Students, visiting pilots, suppliers and families all have their own dependencies. A short message in advance, such as “if the morning briefing is cancelled, expect a text by this hour and the lesson moves to the afternoon”, spares everyone a round of anxious calls. People tend to stay calm when they know the plan and the rule for changing it.
Can technology be a fallback, or is it the thing that fails?
Both. Digital tools are excellent at tracking schedules and alerting people, and they also fail through flat batteries, missing signal and software updates at the wrong moment. The rule of thumb is that every critical digital tool should have a low-tech partner: a printed copy, a phone number written in a notebook, a whiteboard in the hangar. Test the partner occasionally so that you know it still works.
What if the fallback fails too?
It can happen. For the most important parts of an operation, think about a third layer, or at least a clear rule for stopping. In aviation, “do not go” is a legitimate final fallback. Deciding in advance that you will stop an activity if both the main and second options are unavailable removes pressure to continue in poor conditions. Not every item needs three layers; reserve them for the places where a failure would be costly.
Does this apply to activities off the airfield?
Absolutely. Transport to the airfield, accommodation for visiting students, childcare during a long flying day: all of these can disrupt training and all of them respond to the same approach. Many teams find that life logistics fail more often than aircraft, so they deserve the same attention. A free afternoon created by a cancelled session also gives people something to do; some pick a talk or a local gathering, you might scroll through MyEventNow, a website that sorts upcoming events and venues into categories, alongside its own blog and forum, for ideas. Always confirm particulars with the organisers yourself.
How do we introduce the habit without overwhelming people?
Begin with one briefing. Pick a regular meeting and add a single question: “what is our fallback for today’s biggest dependency, and what is the trigger?” Ask it for a few weeks until it feels natural. Then add a second question about who decides. Over time, the answers become part of normal conversation, and the written list grows by itself. Resist the temptation to launch a big programme; small repeated habits last longer than large announcements.
What does a good written fallback look like?
Short. Aim for four lines: what the main plan depends on, what replaces it, what tells you to switch and who calls it. A card pinned in the briefing room works better than a binder on a shelf. If you can read it aloud in about fifteen seconds, people will use it. If it takes a page, they will skip it on the busy mornings when it matters most.
Can one fallback cover several risks?
Sometimes. A general-purpose option, such as a prepared ground session, can stand in for a cancelled flight whatever the cause: weather, an aircraft defect or an unavailable instructor. That makes it efficient to maintain. Just be sure the trigger for each cause is still written down, because the reason for switching shapes how you tell people about it.
Should students be involved in the planning?
Yes, to a sensible degree. Students who understand why a lesson might be swapped for a ground session are less frustrated when it happens, and they pick up the habit for their own flying later. Show them the weather limit that triggers the change, explain the second option and invite questions. It is a gentle way of teaching decision-making before the stakes are high.
How do we handle the disappointment when a plan B kicks in?
Name it, then move on. A cancelled flight is disappointing, and pretending otherwise rarely helps. What does help is having the replacement activity ready so that the disappointment is short. A well-run ground session, a useful simulator hour or a hands-on workshop can make the day feel productive. People remember how a change was handled more than the change itself.
Which single idea is worth carrying away?
A fallback is only real if it has three parts: a second option, a clear trigger and a named decider. Check those three and you will have covered most of what matters. Everything else is detail that can be added as experience grows, and each time a plan B is used successfully, the whole team learns that a surprise does not have to become a scramble.
