You know the feeling. The aircraft is open on the hangar floor, the work order is half done, and the one component you ordered has either not shown up or arrived looking nothing like the picture. Suddenly a routine job is a grounded aircraft, an annoyed owner and a phone that will not stop buzzing. If you have lived that scene, read on. We will handle it the way you would handle a fault on the airframe: describe the symptom, find the cause, and fix it, with a fallback decided before the next order goes out.
The symptom: one part holds up the whole job
Start with what you actually see. A task that should take two days stretches into two weeks. Everything else on the checklist is finished and the aircraft sits waiting on a single item. Nobody can sign off, nobody can fly it, and every day of waiting has a cost, whether that shows up as hangar fees, a missed trip or simply a very quiet owner.
The usual reaction is to chase the supplier harder. That helps a little, but it does not touch the real problem, which is that the whole job was leaning on one source and one delivery date.
The diagnosis: three common causes
When we look back at stalled jobs, the root cause tends to be one of three things.
Cause one: a single supplier for a critical item
Maybe the shop has always bought a certain fitting from one place, and it worked for years. Then the supplier runs out, or the stock is on a slow shipment, and there is nowhere else to turn because nobody ever built a second contact.
Cause two: an order placed too late
The part was ordered the day the job was opened rather than when the need first appeared. Any delay, however small, lands directly on the aircraft’s downtime.
Cause three: the wrong part on the shelf
A part number was copied incorrectly, an old revision was supplied, or two similar items were mixed up. The box arrives on time and is still no use. That is a delay as real as one caused by a late truck.
If you read through our notes on common avionics parts buying mistakes, you will recognise how often the third cause hides inside what looks like a logistics problem.
The fix: decide plan B before you order
All three respond to one habit, and it is a cheap one: before you place the order, decide what you will do if this exact order does not work out, and decide what event tells you to do it. Think of it as writing the repair for the repair.
Here is what that looks like on the bench.
- Name the critical item. For each job, pick the one part that would stop everything if it were late. You do not need a plan B for every washer, only for the item whose absence ends the day.
- Line up an alternate source. Have a second supplier contact saved, and ask them in advance whether they can quote on the same part number. A relationship that already exists replies faster than one built in a panic.
- Set the switch date. If a confirmed shipping date has not arrived by a particular day, that is your trigger. On that day you contact the second source, not the next day, and not after another round of waiting.
- Check the alternate is acceptable. Whatever the fallback is, its suitability for the aircraft is a decision for the responsible licensed engineer and the approved documentation, not for a spreadsheet or a sales message.
That last step matters more than the rest. A fallback that creates an airworthiness question is not a fallback at all, so the alternates you line up should be ones your engineer already knows how to approve.
Variations that suit different jobs
Not every job needs the same style of backup. A few options crop up often.
- An alternate supplier: same part, different seller.
- An approved equivalent: a part your engineer is already able to accept in place of the first choice, identified before you need it.
- A serviceable exchange or overhaul route: useful when new stock is scarce, provided the paperwork supports it.
- A resequenced job: if the part cannot arrive soon, can other work on the aircraft be brought forward so the hangar slot is not wasted?
The last one is easy to forget. A fallback does not always replace the part. Sometimes it simply reorganises the work so waiting hurts less.
Worked example: a brake job
Say you are planning a brake overhaul on a small aircraft. The critical items are the friction linings and one specific seal kit. Before the aircraft comes in, you confirm with your usual source that the kit is in stock. You also note a second supplier and keep the exact part number and revision on a sticky note. Your trigger: if the kit is not shipped by close of business the day after the order, call the second source.
If the first order goes smoothly, you cancel nothing and lose nothing. If it does not, you are already dialling. Our brake parts checklist for aircraft maintenance is a handy companion for working out which items on that list are the critical ones.
Worked example: a fuel system fitting
Fuel system work has a different rhythm because many fittings look alike and small differences matter. Here the main risk is the wrong item, not the late one. So the fallback is partly a verification step: when the part arrives, compare its number and revision against the documentation before the old one comes off, and if it does not match, the alternate order goes out the same hour. The fuel system parts checklist for owners shows what to confirm before you commit.
When people are involved
Parts are only half of it. Owners and crews also have weekends, plans and trips that depend on the aircraft being back. Part of a good fallback is deciding in advance how you will tell them. If the trigger fires, send one clear message with the new expected timing and the next checkpoint. Silence is usually worse than slow news.
It is worth remembering that downtime does not have to be dead time for the people around the aircraft either. When a job runs long, crews and owners often want something to do with a freed-up weekend. A site like MyEventNow, an events-listing website with a venue section, category pages and a forum, can help someone find a different plan for the days they had set aside, which keeps the mood easier while the workshop sorts out the part.
Quick troubleshooting table, in words
If the part is late, switch on your date trigger and contact the second source. If the part is wrong, check the number and revision first, then reorder from whichever source can supply the right revision fastest. If the supplier has gone quiet, treat silence past your cut-off as the signal. If everything fails, resequence the work and free the slot.
Keep it light
Do not turn this into a binder. A line or two on each work order is enough: the critical item, the alternate and the switch date. Reread it at the start of every job. If a fallback never gets used for a year, check that the contact still answers the phone, because a stale plan B is just a nicer-looking plan A.
The aircraft will still occasionally surprise you, and that is part of the trade. What you can change is how long a surprise lasts. A fallback written down before the order goes out makes that surprise a short phone call rather than a long wait.

