The story that follows is an imagined one, told to make an everyday point about flight training: a shift handover is a piece of work in its own right. Names, places and details are invented, and nothing here describes procedures you must follow. Your school’s approved manuals and your authority’s rules always govern real operations. With that said, let us meet Rhea, who has just finished the longest Friday of her season on the flight line of a small training school, and Dev, who is about to walk in and take over.

The Friday that nearly slipped

Rhea had run the line since dawn. Four training aircraft, two instructors on leave, one student on a nervous first solo cross-country, and a hangar door that had stuck twice. By mid-afternoon she was tired in the specific way that makes people quiet and careless. Her relief, Dev, was due at four. She had planned to brief him properly. At ten to four, a student returned early with a question about a radio fault, and the briefing shrank to a hurried hallway conversation.

“Everything is fine,” she said, handing over a clipboard. “Number three is back in the afternoon rotation. Oh, and the late student needs a word about tomorrow.” Then she was gone, because her ride was waiting.

Dev nodded, took the clipboard and thanked her. He did not yet know that “number three is back” really meant “number three is back, except there is a small matter with the cabin door latch that the engineers are waiting on a part for, and which I told the first-hour instructor about but nobody wrote down”. He did not know that the late student was nervous because the previous instructor had cancelled twice. He did not know that the fuel bowser was low and a delivery was promised for the evening.

What Dev found, one thing at a time

Within an hour, Dev had discovered each of those gaps the slow way. A student asked why aircraft three felt different on the ground. Dev checked the board, saw the aircraft listed as available and, being new to the shift, trusted it. A quick conversation with a maintenance colleague stopped him from assigning that aircraft before the issue was properly closed out through the official channels. It was a close call, and nobody was hurt, but the moment hung in the air for a while afterwards.

The fuel was easier. A lineman mentioned it in passing. Still, if he had been busy, the delivery might have been missed, and the evening flights compressed into a cramped window.

The student was the part Dev found hardest. She had been told twice that her flight was off. When she arrived a third time, she was braced for another disappointment. Dev had no idea why she looked so anxious, and he handled it clumsily.

The Monday after

On Monday, the chief instructor gathered the line team for ten minutes. She did not blame anyone. She asked a simple question: “If Rhea had had another ten minutes on Friday, what would she have said?” The answers came quickly. They would have said the door latch was awaiting a part. They would have mentioned the fuel delivery. They would have warned Dev about the student’s two cancelled flights.

From that conversation, the team built a short card, one side of a page, that every outgoing shift lead fills in before leaving. Five boxes: done, still open, where things sit, what to keep an eye on, and whom to call. It was not a new official form. It sat beside the existing records and pointed to them. It deferred, by design, to the school’s approved procedures and to maintenance’s own paperwork for anything that concerned an aircraft’s status.

How the card changed Fridays

The next time Rhea was relieved, she took four minutes with the card. Finished: morning flights complete, two aircraft refuelled. Half-done: one student’s debrief outstanding, one weather call to be rechecked at five. Where things are: spare keys in the office drawer, refuelling log on the clipboard, student files in the instructor room. Watch: gusty afternoon crosswind forecast, one student new to the school. Ask: the chief instructor for anything about scheduling, maintenance directly for anything about aircraft status.

Dev read it back to her in his own words. “Crosswind later, one debrief owed, ask maintenance, not the clipboard, about aircraft.” She nodded. He had it. She left on time, and nobody had to guess.

The students noticed

What surprised the team was how quickly students picked up on the change. A student who had once sat for forty minutes waiting for an instructor who had not been told about the slot now found that the next instructor already knew. Another said it felt as if the school remembered them from one shift to the next. These are small signals, but in training, where confidence is half the battle, small signals count.

Anyone curious about how a modern school presents its training assets might enjoy reading about a newer simulator joining a school’s IFR training program or about a glass-cockpit twin entering the training fleet. Each addition to a fleet is one more thing a shift lead has to know about, and one more reason handovers need a place to record it.

What the story teaches about handovers

None of the failures in this story were dramatic, and that is exactly the point. Rhea was competent and well-meaning. Dev was careful. The gap lay in the thin air between them, in the minutes nobody had. A clean handover is a way of buying those minutes in advance, by deciding what must be said and writing it down before the pressure arrives.

Three habits made the difference at this school, and they transfer anywhere:

  • Write it before you are tired. Start the note when the shift is half over, not when you are walking out.
  • Separate “done” from “in hand”. A task that is half-done is the most dangerous kind to forget.
  • Point to the official source. If something concerns an aircraft’s airworthiness status, the note says where the authoritative record is; it never tries to be that record.

What went into each box

The team argued about the wording for a week and settled on plain examples. Under the first box, only things a relief could cross off their mind: flights completed, refuelling logged, briefings given. Under the second, loose ends with a clear next step: a call awaiting a reply, a debrief still owed, a weather check due at a set hour. The third box named places, not people: office drawer, clipboard, instructor room, the shared schedule. The fourth held the human texture, a nervous student, a new lineman, a gusty forecast. The fifth was a short list of names with their areas, so Dev never had to wonder whether a question belonged to the chief instructor or to maintenance.

They also added one rule at the bottom of the card: if you are unsure whether something affects an aircraft’s status, do not decide it from the note. Ask the people responsible for the official record.

Beyond the airfield

Rhea’s problem is not unique to aviation. In the world of software operations, engineers hired for a short stretch face the same moment when they step away. Readers from technology will recognise the scene. The country-sorted directory of independent specialists at DevOps FreeLancers exists for brief engagements like these, and the engagements that end best are the ones where somebody wrote down the open items, the locations of everything important and the parts that could still bite. Whether the system is a fleet or a server estate, the next person deserves to start with more than an optimistic “everything is fine”.

A last note from the line

If you run a team, try this experiment at your next shift change. Ask the person leaving to say aloud what they would tell their relief if they had ten extra minutes, and write down the answer. Do it for a month. Then look at the notes. You will find the same gaps repeating, and each repetition is a ready-made improvement to your routine.

Rhea, for the record, now keeps a spare copy of the card in her jacket pocket. She says it is the lightest piece of safety equipment she owns.

© 2024 ADVANCED INTERNATIONAL AVIATION ACADEMY. ALL RIGHTS RESERVED.

STAY CONNECTED WITH US: