How One Flying Club Wrote Its Flight-Day Runbook

How One Flying Club Wrote Its Flight-Day Runbook

Every flying club has a person like Harbans. He has been around for fourteen years, he knows which aircraft tends to need a second look at the fuel selector, which examiner likes a tidy logbook, and exactly how to run a Saturday so that six students each get airborne without anyone standing around for two hours. None of this is written down. It lives in his head, and for a long time that worked fine. Here is how one small club in India found out that a flight training runbook is the cheapest insurance a school can buy.

Names and details below are made up for illustration, yet any instructor will recognise the pattern. It has three instructors, one operations coordinator, a handful of aircraft and about thirty active students working towards their licences. Saturday is the busiest day. Harbans runs it from a folding table beside the hangar, and the rest of the team simply follows his lead.

The Saturday Harbans was ill

One Friday evening Harbans called to say he had a fever and would not be in. The coordinator, Meera, had joined only five months earlier. She knew the schedule board and the booking sheet, but she had never opened the day, because Harbans always opened it. She stood at the table at seven in the morning with a list of names and a feeling that she was missing a step she could not name.

She was. By nine, two students had arrived without their medical paperwork in the folder, one aircraft was booked twice, and a student who needed a ground briefing before flying was handed a slot with no briefing time ahead of it. Nobody was unsafe, because the instructors made their own calls on the ramp. But the morning was slow, tense and clumsy, and three students went home without flying.

That evening the team did what good teams do after a bad day. They did not blame Meera. They asked what Harbans did every Saturday that nobody else knew he did, and they wrote it down.

What goes into a flight-day runbook

A runbook is not a manual and it is not a policy. It is a short, plain list of steps for one recurring job, written so that a competent person who has never done the job can follow it without phoning someone. The club’s first draft was one page. It had a title, a trigger, an owner and a numbered list. Here is roughly what Harbans dictated.

  1. The night before: check the booking sheet against the aircraft availability list and look for doubles. Confirm each student has a briefing slot placed before their flight slot.
  2. Arrival: open the document folder at the table. Each student’s folder should hold the current medical and licence paperwork, and the logbook should be up to date. Anything missing is flagged at once, not at the aircraft.
  3. Briefing block: instructors confirm who is flying what, and who is doing ground study instead if weather or aircraft status changes the plan.
  4. Aircraft status: the aircraft technical log is read by the coordinator and the instructor together before any slot is released. If the log shows an open item, the instructor decides, and the decision is written next to the item.
  5. Weather and field conditions: the instructor on duty makes the go or no-go call. The coordinator only records it and tells the waiting students.
  6. Close of day: fuel and fluids noted, hours logged, tomorrow’s open items listed, and the folder returned to its shelf.

Notice what is missing. There is no advice on how to fly, how to read weather or how to judge an aircraft. Those belong to licensed people and to proper training material. The runbook covers the work around the flying: the paperwork, the sequence, who decides what, and where the record goes. That is exactly the kind of knowledge that disappears when one person is away.

Testing the draft on someone who was not there

The most important step came next, and many teams skip it. The club handed the page to a person who had never run a Saturday, a newly joined front-desk assistant named Joseph, and asked him to follow it on a quiet Tuesday as a dry run. He got stuck in three places. The runbook said “check the folder” without saying which folder. It said “confirm briefing slots” without saying where the slots were recorded. And it assumed everyone knew who the instructor on duty was.

Each stumble became a fix. The folder got a colour and a shelf location. The briefing slots got a column on the booking sheet. The duty instructor’s name was added to the top of the page every week. A runbook that has not been tried by a newcomer is a guess, not a procedure. If the person who wrote it is the only one who has tested it, it will quietly leave out the parts that feel too obvious to mention.

Where students fit into this

Students are part of the system too, and a good runbook thinks about them. The club added a short student version: what to bring, when to arrive, what happens if the weather turns, and how to reach the desk. For students preparing for their aptitude and entrance rounds before they ever sit in a cockpit, the club kept a small reading list on its own site. It pointed beginners to a walkthrough of entrance exams for aspiring Indian aviators and to a piece on getting ready for pilot aptitude testing. When a student asked, “What do I do before the first lesson?” the answer no longer depended on who happened to be at the desk.

The same idea applies to the practice questions students use. Rather than letting each instructor improvise, the club kept one agreed starting point, such as the set of typical aptitude questions candidates meet in India, so that every student began from the same material and the instructors could compare notes.

Fixes that worked become new steps

The second rule the club adopted was simple: whenever something goes wrong and somebody finds a fix, the fix goes into the runbook the same week. Early on, a double-booked aircraft was resolved by swapping a student to the following slot and moving a ground briefing earlier. That was a clever fix on the day. Written down, it became step seven: “If an aircraft is double-booked, move the student with the later briefing to the next available aircraft, and tell the instructor before telling the student.”

After two months the page had grown to a page and a half. It had also stopped growing, which is a good sign. Mistakes that used to repeat every few weeks stopped repeating, because the answer was now in the document and not in somebody’s memory.

Looking at how other fields write these things down

It helps to see the same habit in a field far from aviation. Teams that run data pipelines, for example, are famous for writing exactly this kind of short routine for each recurring job, because a failed overnight load at 2 a.m. does not wait for the one person who understands it. Anyone who wants to watch that discipline in its home setting can read TheDataOps.org, where data engineers write about moving from DevOps habits to dependable data work. The mindset carries over surprisingly well to a hangar.

How to start your own, this week

You do not need a software tool or a long meeting. You need one recurring job, one pen and one person willing to follow your first draft. Here is a plain way to begin.

  • Pick the job that breaks when one person is away. For most clubs it is the day-opening routine or the end-of-month paperwork for student records.
  • Write the steps as the person who knows it does them, in the order they happen, in short sentences that start with a verb.
  • Add a trigger and an owner. When does this routine run, and who is responsible for it? A runbook with no owner is a poster.
  • Dry-run it with a newcomer and note every question they ask. Each question is a missing line.
  • Put it where people actually look, such as a printed sheet at the desk and a copy in the shared folder, not in a drawer.
  • Review it after every surprise. If a fix worked, it earns a step.

What changed at the club

Three months later Harbans took a week off for a family wedding. Meera opened the day with the page in hand. Joseph handled the folders. A student who arrived without a document was spotted at the table and sent to fetch it before the briefing, rather than discovered at the aircraft. All six slots flew. Harbans came back to a tidy folder and, to his credit, a few corrections. He had spotted two steps even he had forgotten he did, and the runbook gained them.

That is the real point. The document did not replace Harbans, and it was never meant to. It let the club keep working at its usual standard while he was away, and it let him stop being the single point everything leaned on. If you run or study at a flight school, ask yourself which job in your week lives only in one head. Write that one down first.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *