Illustrated cover reading "Branching Scenarios for Aviation Decision-Making" on a butter yellow background with a blob pattern

Branching Scenarios for Aviation Decision-Making: A Design Guide for Training Providers

Table of Contents

Share:
Easily share intel
Summarise this page with your favorite AI assistant

Branching scenarios are eLearning activities in which each learner choice changes what happens next. In aviation training, they let learners practice decisions such as continuing, diverting or stopping a task, and see the consequences without real risk. A module does not replace the simulator, the aircraft or the instructor.

This guide is for training providers and aviation training organizations that build eLearning for flight schools, maintenance, cabin crew and ground handling teams. We are a content authoring vendor, not an aviation authority. Nothing here says any course or tool is approved by a regulator. Your approved training program decides what a correct answer is.

The top search results for this term are generic, and none mentions aviation.

Key takeaways

  • Use branching scenarios for judgment under uncertainty. Teach fixed procedures and recall in a linear module.
  • Give each decision node one job from a model such as DECIDE or FOR-DEC, and use branch and bottleneck to keep the build small.
  • Show consequences immediately and give coaching before any retry. Name the approved procedure when the syllabus has one.
  • Store node IDs and a compact path code in SCORM, and treat the data as practice evidence, not as proof of competence.

What are branching scenarios for aviation decision-making, and when do they fit?

Branching scenarios for aviation decision-making are eLearning activities in which a learner faces an operational situation, chooses an action, sees the consequence and meets the next decision on a path that depends on that choice. They fit judgment-based skills. They do not fit memorized facts, manual skills or crew interaction.

A quiz checks recall of a rule. A scenario asks whether the learner applies it when cues are incomplete. Aviation already uses the idea: a 2015 paper by Thomas and Lee in the Journal of Aviation/Aerospace Education & Research describes decision-based scenario lessons for flight training devices at Embry-Riddle Aeronautical University, where software presents situations that require decisions and then branches to show the results.

  • Use it for: go or no-go choices, fault diagnosis, planning as information changes, and prioritizing tasks.
  • Skip it for: approved step sequences with one correct order, psychomotor skills, and real crew interaction.
  • For crew work: our CRM aviation training scenarios guide has a worked event-set storyboard, so we do not repeat one.

Which aviation decision-making models can structure your branching scenarios?

Three aviation decision models can structure branching scenarios: the FAA’s DECIDE model, FOR-DEC from Lufthansa and the German Aerospace Center, and DODAR. Each lists steps a decision node can test, so you can grade how a learner decides, not only which option they pick.

The FAA’s Pilot’s Handbook of Aeronautical Knowledge, chapter 2, lists DECIDE. SKYbrary’s FOR-DEC article describes FOR-DEC. Soll and colleagues (2016) list DODAR in their Table 2 as used by British Airways and CityJet. The mapping is our judgment.

Model Steps as published What a node can test
DECIDE Detect, Estimate, Choose, Identify, Do, Evaluate Detect: did they notice the cue? Estimate: did they judge severity? Evaluate: did they check the result?
FOR-DEC Facts, Options, Risks and Benefits, Decision, Execution, Check Facts: what they gather first. Risks and Benefits: how they compare options. Check: whether they confirm after acting.
DODAR Diagnosis, Options, Decision, Assign Tasks, Review and risk assessment Assign tasks: who does what, which suits team scenarios.

Treat the models as scaffolding, not as proven. Soll and colleagues wrote that “none of the models has been evaluated considering their usefulness in real-world aeronautical decision-making,” concluded that FOR-DEC is useful “when there is enough time,” and reported pilots saying the check step is often omitted. So build a time-critical event as one fast node, and keep the full model for diagnosis and planning.

Pro tip: Give the Check Step Its Own Node. Add a node after the action where new information arrives. Reward the learner who confirms the result, and let the one who assumes it worked meet a changed situation.

Which structure should your branching scenarios use?

For most aviation courses, branching scenarios should use a branch and bottleneck structure, where paths split at a decision and then rejoin at a shared event. Christy Tucker explains that a bottleneck or two sharply cuts the screens you must build.

In her branch and bottleneck article, a tree with three options per decision and only three decisions already needs 40 screens (1+3+9+27). Our scenario-based learning design guide compares six structure types. The matching below is our judgment.

Training need Structure Why
One quick go or no-go drill Single node, or a tree of up to three decisions Tucker says a tree is generally limited to about three decisions per path.
A flight or task with several linked events Branch and bottleneck with a state variable Every path reaches the shared events, so you write them once.
A procedure with one approved order No branching Teach it linearly and test recall.

How many decision points should one scenario have?

Plan four to six decision points per path for most aviation modules, and add more only when the skill needs it. Sources disagree, so this figure is our judgment. That is roughly one node per step of a decision model. Confirm it in a pilot.

Cathy Moore recommends at least seven decisions per path. TalentLMS suggests about ten, and Tucker’s limit of about three applies to trees without rejoining paths. Branch and bottleneck reaches five or six decisions per path without exploding the screen count.

How do you build branching scenarios, step by step?

To build branching scenarios, write the decision a learner must make on the job, choose one decision model, map the paths and bottlenecks, then write consequences and coaching for every option. Review the draft with a subject-matter expert (SME) and pilot it before building screens.

  1. Start from the approved syllabus. Take the objective from your client’s approved program. Never change a procedure.
  2. Pick one decision model and decide which steps this scenario tests.
  3. Interview the SME. Ask what cues the person has and what a rushed colleague does.
  4. Write three options per node. Use one approved response, one rushed but plausible response, and one cautious but uninformed response.
  5. Map on paper first. Mark nodes, bottlenecks and any state variable, such as a margin that changes later options.
  6. Write consequences, then coaching. What the learner sees comes first, then the explanation.
  7. Review and pilot. The SME checks every option against the syllabus, and a few learners check difficulty. Record the version.

What does a decision node worksheet look like?

A decision node worksheet lists, for each node, the model step tested, the cue, three option types and the consequence. The example below is a ground school cross-country exercise in which the weather changes. It is illustrative: we invented it, it is not an incident, and your SME must rewrite it. Copy the column headings as your template.

Node Step tested Cue the learner sees Options (A approved, B rushed, C cautious but uninformed) Consequence and state
1 Detect An observed cloud base lower than the forecast used in planning A: compare it with the plan and note the gap. B: carry on because departure weather was fine. C: turn back without checking. A keeps the margin “known”. B reaches node 2 with a “reduced” margin. C ends early with a prompt to return to the cue.
2 (bottleneck) Estimate and Choose Updated weather and fuel remaining A: judge severity against the criteria in the syllabus. B: assume it will improve. C: pick the nearest field without comparing. The margin value changes which options appear.
3 (bottleneck) Evaluate A new report after the action A: confirm the result against expectations. B: assume it worked. C: ask for more information but take no action. B meets a changed situation. A closes the scenario.

Every path reaches nodes 2 and 3, so you write them once. Check that your authoring tool can carry a state variable first.

How should feedback work in aviation branching scenarios?

Feedback in aviation branching scenarios should pair consequences, which show what happened, with coaching, which explains why. Show consequences immediately and give coaching before any retry. For experienced learners such as recurrent trainees, consider delaying coaching until the scenario ends.

This follows Christy Tucker’s reading of Will Thalheimer’s research. She recommends immediate coaching for novices, and says experts are better at diagnosing problems from consequences alone. A 2023 medical education study she cites found no discernible difference between immediate and delayed feedback, but it tested multiple-choice questions, not scenarios. Pilot your timing.

Write feedback differently for the two kinds of decisions:

  • Approved-procedure decisions: name the procedure and the reason, without debate.
  • Judgment decisions: show the trade-offs of each defensible option.

How do you track branching scenarios in SCORM or xAPI?

SCORM can report a branching scenario’s completion, score and time, and its interactions data model can record each decision. xAPI statements can carry decision-level data in more detail. Neither shows that a learner will decide well on the job, so label results as practice evidence.

The table uses the Rustici SCORM run-time reference, as of October 2026.

Item SCORM 1.2 SCORM 2004 What to do
Per-decision data Interaction elements (id, type, student_response, result, latency) are write-only Same elements, learner_response, read/write Record one interaction per node, using the result value “neutral” for judgment calls, and test whether the client’s LMS reports it.
Bookmark and state (suspend_data) 4,096 characters 4,000 in 2nd Edition; 64,000 in 3rd and 4th Store a short path code and the state variable.

A six-node path code and one margin value take a few dozen characters, so the limit bites only if you store option text. According to the xAPI.com overview, xAPI is an IEEE standard (IEEE 9274.1.1-2023) whose statements follow a noun, verb, object pattern. Our SCORM 1.2 vs SCORM 2004 comparison helps with the export choice, and our SCORM package QA checklist covers testing in the client’s LMS.

Pro tip: Store Option IDs, Not Option Text. Name nodes and options with stable IDs such as wx-n1-a. When the SME rewrites a screen, old records still map to the same decision.

What mistakes weaken aviation branching scenarios?

Five mistakes weaken aviation branching scenarios: wrong options nobody would pick, content that drifts from the approved procedure, forced paths, scores read as competence, and inaccessible choice screens. Each is cheap to avoid at storyboard stage and costly to fix after the build.

  • Obvious wrong options. As our scenario guide says, “Options nobody would pick teach nothing.”
  • Drift from procedure. Have the SME review each revision, and version modules as in course version control when regulations change.
  • Forced paths. Do not send every wrong choice back to the right one, or learners never meet a consequence.
  • Scores as competence. A module score shows what a learner chose on screen, not how they will act on the job.
  • Inaccessible choices. Test keyboard and screen reader use of choice screens. Six of the ten top pages we read do not cover accessibility.

What should you do next?

Ask your SME for one decision that learners get wrong, fill in the worksheet for three nodes, and pilot it with a few learners before building more. That small test shows whether the options feel realistic to the people who will take the course.

SimpliAuthor is made by the same company that publishes this site, and it is a SimpliTrain product. Its AI Course Authoring page describes editable blocks that include interactive media and assessments, and SCORM-ready courses. It does not mention branching scenarios, and we have not tested building the node pattern above in it. Bring your worksheet and ask for a SimpliTrain demo to see whether it fits.

Frequently asked questions

What are branching scenarios in aviation training?

Branching scenarios are eLearning activities where a learner makes a decision in an operational situation and sees a consequence that depends on that choice. They practice judgment, such as diagnosing a fault, and complement simulator, aircraft and instructor-led training. Your approved program decides what counts as correct.

What is the FOR-DEC model?

FOR-DEC is an aviation decision-making model with six steps: Facts, Options, Risks and Benefits, Decision, Execution and Check. According to SKYbrary, Lufthansa and the German Aerospace Center developed it in the 1990s. In a branching scenario, a node can test each step.

How many decision points should a branching scenario have?

Sources disagree. Cathy Moore recommends at least seven per path, Tucker limits plain trees to about three, and TalentLMS suggests about ten. For aviation modules, we suggest four to six on a branch and bottleneck structure, then a pilot with a few learners to confirm the difficulty.

Should feedback in a branching scenario be immediate or delayed?

Show consequences immediately and give coaching before any retry. Christy Tucker suggests immediate coaching for novices and allows delayed coaching for experts, but she also notes that research on feedback timing is sometimes contradictory. Pilot your timing with real learners.

How do you track branching scenarios in SCORM?

Record one SCORM interaction per decision node, and store a short path code and state variable in suspend_data, which holds 4,096 characters in SCORM 1.2. Because SCORM 1.2 marks interaction elements write-only, test what the client’s LMS reports. Label results as practice evidence.

Want to learn more?

Reach out to us to learn more.

One Platform for
All Your Training Needs

Get a personalized demo.