Aviation likes to celebrate arrivals. A new simulator is installed, a newer trainer joins the line, a redesigned website goes live. Those moments deserve celebration, but every operation also runs on a long tail of things that arrived years ago and still need to work today. This primer is for learners who are new to the idea. It explains, in plain terms and with a mini-glossary, why aviation upkeep of what already exists should come before anything new is added.
One boundary first. This article is general and informational. The legal and technical requirements for maintaining any aircraft come from the relevant aviation authority, the approved maintenance programme and the licensed engineers who apply them. Nothing here replaces those, and nothing here should be treated as an inspection standard.
The basic idea in one paragraph
Every asset an academy owns, whether a machine, a document or a web page, begins life working and slowly drifts. Parts wear, paperwork falls behind, contact details change, links die. Drift is invisible while things are quiet and expensive once it surfaces. A regular look at the existing inventory, asking whether each item works, is still wanted, and sends people to the correct destination, catches drift while it is still cheap to fix.
Six words worth knowing
Operations meetings lean on a small vocabulary. What follows is everyday language, not regulatory wording.
- Maintenance: the planned and unplanned work that keeps equipment in a fit state to be used. In aviation it follows an approved programme, not personal preference.
- Records: the written history of an aircraft or component: what was done, when, and by whom. A gap in the records is a problem even if nothing is physically wrong.
- Obsolescence: when something is still present but no longer supported, current or useful, such as a procedure replaced by a newer one.
- Housekeeping: the dull, routine tidying of facilities and files. Dull does not mean optional.
- Link rot: the gradual failure of web addresses as pages move or disappear.
- Retirement: the deliberate decision to stop using something, as opposed to letting it fade away unnoticed.
Why the order matters: look back before you look forward
The reasoning is analytical rather than moral. Adding a new asset adds new maintenance obligations. If the existing obligations are already behind, the new ones stack on top of an unsteady pile. An academy that has just celebrated a new simulator, as our own news about the FRASCA training device joining the programme or the announcement of the glass-cockpit twin added to the fleet, has also taken on a duty to look after those additions properly. That duty is easier to meet when the older equipment and paperwork are already in order.
We do not claim that skipping review leads to any particular failure. What can be said is that the failures people regret are seldom exotic. They tend to be ordinary: an expired item nobody tracked, a record misfiled, a notice that told students to go to the wrong place.
Three questions for every existing item
A beginner needs a method more than a theory. Take any asset and ask three questions.
- Does it still work? For a document, is it accurate. For a page, does it load. For equipment, does the approved programme show it as in order?
- Is it still needed? If nobody uses it, it is clutter, and you can propose removing it.
- Does each reference land correctly? Checklists reference procedures, web pages reference other pages, and labels reference locations. Each reference can drift out of date on its own.
The first question belongs, where equipment is concerned, to the people qualified to answer it. The other two are open to everyone, which is why a student can contribute to an upkeep review without touching an aircraft.
The web side of the academy
A modern academy has a public web presence: course pages, application forms, resource lists, news items. Each page can point to other pages. Over time some of those links break. Because broken links do not announce themselves, a student may click one, hit an error and quietly conclude that the academy is careless.
Checking links by hand does not scale, so many organisations use software. Some organisations keep their published addresses in a link-management platform, URLSnow being one, where scheduled checks mark any address that has stopped responding. For a beginner, the lesson is not about that particular product. It is that repetitive checking should be handed to tools so that humans can spend time on judgement.
What a first upkeep review looks like
Suppose you are asked to help review an academy’s public resources. A sensible first session might proceed like this.
- List every page, document and link the academy publishes for students.
- Mark the date of the last review beside each, or “unknown” where none exists.
- Test the links and note which fail.
- Read the oldest items first, since they are the likeliest to be stale.
- Propose one of three outcomes for each: keep, repair, or retire.
- Hand any equipment or technical question to the responsible engineer or instructor, with a note of what prompted it.
Notice what is absent: you do not decide anything technical. You are helping to surface questions, which is a real and valuable contribution.
A small worked example
Imagine a student-run resource page that lists a weather service, a regulator’s information page, a recommended reading list and a booking form. A beginner reviewing it might find that the weather link redirects to a home page, the reading list names a title that has since been replaced by a new edition, and the booking form works but mentions a term that ended long ago. None of those are technical matters. All of them are fixable in an afternoon, and each would otherwise mislead a real person at a real moment.
Common beginner mistakes
- Treating review as optional extra work. It is part of running the operation, not a bonus.
- Confusing tidy with correct. A neat folder can still hold outdated pages.
- Retiring too slowly. Holding on to everything makes the useful items harder to find.
- Blurring roles. Administrative review and technical inspection are different jobs with different owners.
Keeping the habit alive
The simplest way to sustain upkeep is to tie it to a calendar event that already exists: the start of a term, the end of a season, a new intake. Put the review on that date, assign an owner, and write down what was found. Without those three elements it tends to remain a good idea rather than a practice.
For a learner, the takeaway is modest and durable. When someone proposes a shiny addition, ask first what it will rest on. If the answer is a stack of untended older assets, the sensible next step is to tend them, then build. Operations that keep their existing things in good order tend to be the ones whose new things actually work.