When a flight school adds a new aircraft or a new simulator, the mood is celebratory. There are photographs, announcements and an eager queue of students. Yet the weeks after any new arrival are when small oversights turn into cancelled lessons. A pre-mortem for a fleet addition is a simple way to reduce those surprises: before the new trainer or simulator enters service, the team pretends the introduction has gone badly and writes down why. This explainer describes the method in everyday language. Treat it as background reading: the regulator’s rules, the manufacturer’s documentation and your school’s own procedures always take precedence.

The idea in two sentences

A pre-mortem asks you to imagine that something has already failed and to list the reasons. Because the failure is imagined as certain, people speak more freely about weaknesses they would otherwise politely avoid.

Why a new aircraft or simulator is a good candidate

Introducing new equipment changes many things at once. Instructors need to become comfortable with it. Students need to be scheduled across it. Maintenance and record-keeping need to cover it. Lesson plans need to be adjusted for what it can and cannot do. Each of those is a small project, and a plan that only celebrates the arrival tends to ignore all of them. Schools that have announced such additions publicly, such as in an announcement of an advanced twin-engine trainer joining the fleet or a note about a new instrument-procedures simulator, usually describe the capability. The pre-mortem covers the quieter question of readiness.

Running one, step by step

1. Set the scene

Gather the people who will touch the new equipment: instructors, schedulers, maintenance staff and a student representative if possible. State the goal plainly, for instance “the new trainer is in regular use for scheduled lessons without disruption by the end of the first few weeks.”

2. Announce the failure

Say, “It is a couple of months later and the introduction was a mess. Write down the reasons.” Allow silent writing first so that senior voices do not set the tone for everyone else.

3. Read the reasons aloud

Collect every item without comment. You will usually hear a mix of the practical and the human, such as “nobody had time to learn the avionics,” “bookings did not account for the new time blocks,” “spare parts were not sourced,” “students were confused about which lessons applied,” or “paperwork was incomplete.”

4. Group and rank

Sort the reasons into themes: people and training, scheduling, maintenance and parts, documentation, and communication. Then decide which are both likely and costly. These are your priority list.

5. Turn reasons into actions

For each priority, name one preventive step and one early warning sign. If “instructors were not comfortable” is a reason, a preventive step might be a structured familiarisation period, and a warning sign might be instructors avoiding the new equipment in the schedule. Follow your authority’s rules for any required checks and approvals; the exercise adds to those, it does not replace them.

A sample list for a new simulator

To make this concrete, here are imagined failure reasons a school might write about a new simulator. They are examples, not claims about any particular school.

  • Instructors had only informal exposure before students arrived.
  • Session lengths were assumed to match older equipment, so bookings overran.
  • The lesson plan did not state which exercises belong in the simulator and which in the aircraft.
  • Records of simulator time were kept in a different place from flying hours.
  • A software or hardware fault had no agreed backup plan for booked students.

Notice that almost none of these are about the equipment itself. They are about the organisation around it. Readers who like to see the training side, for example the school’s write-up on choosing a multi-type simulator for instrument currency and unusual-attitude work, will recognise how much surrounding structure good training needs.

Who owns the follow-through

A list is only useful if someone carries it forward. At the end of the session, give each priority item a single named person and fix a date for revisiting it. In a flying school that is often the chief instructor for training items, the maintenance lead for parts and technical items, and whoever runs scheduling for booking items. Keep the list somewhere visible to all of them, and update it as items are closed. Over time the same document becomes a record of how past introductions went, which is valuable the next time equipment arrives.

What the exercise is not

It is not a safety case, a risk assessment required by a regulator or a maintenance programme. Those have formal content and formal owners. A pre-mortem is a quick, informal thinking tool that sits alongside them. It also is not a forecast: you are not claiming the failures will happen, only that they are plausible enough to deserve a few minutes. And it is not a blame session, since the point is to find weak spots in the plan, not weak people.

A parallel from software

Teams that run software delivery do something very similar before big releases. If you want to see how that world talks about safeguarding the path code takes from commit to deployment, DevSecOps Now offers a blog on securing CI/CD pipelines for engineers and security practitioners. The vocabulary differs, but the underlying instinct of anticipating breakage in a multi-stage process is identical to what a flying school does with a new aircraft.

Common pitfalls

  • Too many people talking at once. Silent writing first keeps quieter staff from being drowned out.
  • Staying vague. “Poor communication” is not actionable; “students were not told the new booking blocks” is.
  • Forgetting follow-up. Schedule a short review a few weeks into service to see which imagined problems appeared.
  • Using it to skip required steps. Official checks come first, always.

Why it pays off

The cost of the exercise is an hour of staff time. The benefit is that the first weeks of a new aircraft or simulator are spent flying and learning rather than untangling avoidable confusion. For students, that means fewer cancelled sessions and clearer expectations. For the school, it means the investment reaches its purpose sooner. Celebrate the arrival, certainly, but make time to ask how it could go wrong first, and let the answers shape the plan.

© 2024 ADVANCED INTERNATIONAL AVIATION ACADEMY. ALL RIGHTS RESERVED.

STAY CONNECTED WITH US: