People who join a flight academy as students, volunteers or office staff tend to ask the same few things about how the place keeps running day to day. One of the most common is: what happens when the one person who knows how something works is away? The honest answer, for any aviation training operation, is that it should not matter, because the routine is written down. This FAQ explains how short written routines, or runbooks, work in an academy setting. It is general information only and never replaces the approved checklists, manuals and instructions that govern real flying and maintenance.
What is a runbook, in an aviation training setting?
It is a short, numbered page describing a task the academy repeats: opening the briefing room, preparing the simulator for a session, handing a training aircraft from one instructor’s day to the next, or closing up at night. Each page tells a capable newcomer the actions to take, their sequence, and a contact for when something looks wrong.
Why do academies need written routines when they already have official checklists?
Official checklists cover the aircraft and the regulations. They do not usually say where the headset charger lives, who switches the simulator on first, or how the lesson board gets updated after a cancellation. Those practical details usually sit in the heads of long-serving staff. A runbook captures them next to, not instead of, the official material. When there is any conflict, the approved documentation wins.
What goes wrong when know-how lives in one person’s head?
Three things, mostly. Tasks slow down when that person is absent, mistakes creep in when someone guesses, and new staff take far longer to become useful because they must ask questions that a page could answer. The risk grows with success: the more students an academy trains, the more routines there are to remember.
Which routines should be written down first?
Start with the ones that cause the most phone calls or the most delays. Common first picks are:
- Opening and closing the training building.
- Preparing a simulator or classroom for the day’s sessions.
- The handover between one instructor and the next for shared equipment.
- Greeting and registering a new student on the first morning.
- Recording that a routine inspection walk was done, without replacing the official procedure itself.
How long should a runbook page be?
One side of one sheet. If it spills over, split it into two tasks. People read short pages under pressure and ignore long ones. Aim for around eight to twelve numbered lines, each starting with a verb.
Can you give an example for a simulator session?
Here is a plain sample, which any academy would adapt to its own equipment and manuals.
- Sign in on the session board and note the start time.
- Power up the equipment in the order the manufacturer’s guide gives.
- Check the room is clear and the lesson plan for the session is at hand.
- Run the quick functional check the academy has approved.
- Log any fault, however small, in the shared notebook.
- At the end, shut down in the approved order and write the finish time.
Academies that use advanced training devices have a lot to gain from this. If you are curious about the kind of equipment involved, the notes on a simulator added to support instrument procedure practice and on a twin-engine glass cockpit aircraft joining the training fleet show how much modern kit a team has to look after, and why repeatable routines matter around it.
Who writes the runbooks?
The people who do the task, with help from someone who takes notes. Experts tend to skip steps they consider obvious, so pair them with a newer team member who asks “and then what?” until the page is complete. A supervisor should read the page, and check it against the official documents, before it goes into use.
How do you know a runbook works?
Hand the page to a person new to the job and simply observe. Every pause marks a line that is missing. After one or two rounds of testing, most pages become reliable. Date each page and write the name of the person who last checked it, so nobody wonders how fresh it is.
Is this idea used outside aviation?
Very much so. Technical operations teams use runbooks heavily, and data teams in particular document recurring jobs so that whoever is on call can handle them. For a taste of how that field describes the practice, a DataOps publication tracing the journey from DevOps to dependable data practice is one example, though you will not need any of it to start writing pages for a hangar or classroom.
What about students: do they need to know this?
It helps. Students who see runbooks in daily use learn early that safe, orderly operations come from habits that anyone can follow, not from heroics. Students who write a page themselves, say for how they prepare their flight bag, learn to describe their own work clearly, which is a useful skill in an instructor’s or supervisor’s role later on.
How often should pages be reviewed?
After any incident or near miss, whenever equipment changes, and at least every few months otherwise. An outdated page does harm, since staff keep following it. Retire old versions clearly.
What if staff say they have no time to write things down?
That objection is common and fair. The answer is to write while doing, not afterwards. Keep a notebook beside the equipment and jot the steps as you perform them once, then tidy the notes into a clean page at the end of the week. Ten minutes of tidying beats an afternoon of reconstructing a routine from memory, and the saved phone calls repay the effort quickly. A monthly half-hour spent skimming the busiest pages keeps them honest.
What is the simplest way to begin?
Pick one routine this week. Write it as numbered steps right after you do it, ask a colleague to try it, fix what they stumble on, and have a supervisor check it against approved procedures. Then pin it where people will see it. That single page is a better start than a large binder nobody opens, and the habit spreads quickly once colleagues notice how much easier the next shift handover feels.