AW169 man-hour planning: the light-intermediate that isn't a small AW139
When an operator adds AW169s, the first man-hour plan is usually written by someone who knows the AW139 — and it shows. The logic sounds reasonable: the 169 is roughly 80% of a 139 by weight and seats, so take the 139 rates and scale down. I've reviewed three of these plans in the last two years. Every one was short by around a third. Here's why, and the method that gets it right.
01Why scaling by size fails
Maintenance man-hours don't scale with aircraft weight. They scale with three independent drivers, and the AW169's driver mix is completely different from the AW139's:
- Flight-hour-driven work — scheduled inspections, engine and dynamic-component servicing. Yes, this scales down a bit.
- Cycle-driven work — and this is the killer. A typical AW169 EMS or utility role flies short sectors: 800–1,000 cycles against 500 flight hours per year. Cycle-counted items hit their limits far sooner than a flat MH/FH rate assumes.
- Calendar-driven work — 12-month and 24-month packages, component lives in months, AD/SB compliance. These don't care how much you fly. A low-utilisation 169 still eats its calendar packages whole.
A small AW169 flying 500 h/year is not consuming 80% of an AW139's maintenance. It's running nearly the same calendar programme on a fraction of the hours — which pushes the man-hours-per-flight-hour rate up, not down.
02The split-driver method, with numbers
Worked example: a 3-aircraft AW169 EMS fleet, 500 FH and 900 cycles per aircraft per year, single base, day-shift maintenance with planned night cover for returns.
| Demand driver | Basis | Annual MH |
|---|---|---|
| Line maintenance (daily, weekly, transit) | 0.8 MH/FH × 3 aircraft × 500 FH | 1,200 |
| Scheduled inspection packages (600 FH / 12 M) | 4 packages/yr × ~1,000 MH | 4,000 |
| Cycle-driven items (limits hit at 900 cycles/yr) | ~0.15 MH/cycle × 2,700 cycles | 405 |
| Unscheduled defect rectification | 35% of scheduled + line | 1,820 |
| Total annual demand | 7,425 |
Now divide by what one engineer actually delivers. Gross 1,760 h/year minus leave, training and admin leaves ~1,450 h; at a realistic 65% wrench-time ratio that's roughly 940 productive MH per engineer per year:
naive "80% of AW139" plan for the same fleet: 5 engineers
The naive plan doesn't look wrong on paper — it looks wrong in week 41, when the third 12-month package lands, unscheduled rectification is running at 40%, and the overtime bill tells the real story. That gap between plan and actual is exactly the variance AMC1 145.A.30(d) asks you to monitor monthly.
03The certifying-staff fragility nobody models
Eight engineers on a small single-type fleet hides a sharper problem: typically only two or three hold B1/B2 certification authorisation on type. One resignation, one long-term sickness, one type course that slips a quarter — and your plan still shows 8 heads while your certifying capacity has halved. For the AW169 specifically:
- Budget the 6-month pipeline for a new type-rated certifier (course, OJT, authorisation) as a standing plan assumption, not an emergency.
- Keep the certifying headcount at N+1 above your peak-week requirement, not above your average. Peaks cluster when calendar packages bunch — and 12-month packages always bunch, because operators take aircraft at the same time of year they were delivered.
- Track certifying hours separately in your monthly deviation review. A fleet-wide 25% deviation trigger is too late for a two-person certifying pool — a single absence is already a 50% event.
04What to put in the plan document
Write the AW169 plan with the three drivers stated explicitly: FH rate, cycle rate, calendar package count. When the surveyor asks why your MH/FH ratio is higher than the AW139 fleet next door, that's your answer — three lines, and the table above. If you're offshore as well, layer the rotation factor on top of the headcount, not instead of it.
Build the split-driver model for your own fleet: set flight hours, cycles and calendar packages per aircraft, and see the headcount the plan actually needs — with an auditor-ready PDF export.
Run the scenario →