The H160 arrives with zero history: man-hour planning for a brand-new type
Your man-hour plan is only as good as its logged history — and a new type has none. No task-card actuals, no findings ratio, no unscheduled burden, and usually no certifying staff yet. I've watched organisations sign an H160 entry-into-service date with a staffing plan built on the sales brochure's maintenance figures. Here is the method that survives contact with the first year of reality.
01Why "the OEM number" under-plans year one
The maintenance planning document gives you task-hour estimates from a mature, optimised programme — compiled from design analysis and early operators whose data was cleaned before publication. Three things it does not include:
- The learning curve. Every inspection on a new type takes longer: unfamiliar access panels, first-time task cards, tooling you locate by reading the manual. Year-one tasks routinely run 25–40% over estimate.
- Infant-mortality findings. New airframes generate snags, SB embodiments and warranty rectification at a rate a mature fleet never sees. Your unscheduled-to-scheduled ratio will be higher, not lower.
- Certifying-staff scarcity. Task estimates assume a certifier is standing there. On month one of a new type, your entire type-rated certifying pool might be two people — one of whom is on leave.
02The proxy-uplift method
You cannot plan from data you don't have, so plan from the nearest comparable fleet you do have, then apply explicit uplift factors you can defend to a surveyor. Worked example: two H160s entering service, 550 flight hours per aircraft per year, alongside a mature AW139 operation:
| Step | Mature-type basis | H160 year-one factor | Planned value |
|---|---|---|---|
| Annual utilisation | 1,100 FH | — | 1,100 FH |
| Scheduled burden (proxy MPD rate) | 2.6 MH/FH | × 1.30 learning curve | 3.4 MH/FH |
| Scheduled man-hours | 2,860 | — | 3,718 |
| Unscheduled ratio (findings/rectification) | +40% of scheduled | +60% (infant mortality) | +2,231 |
| Total year-one demand | 4,004 MH | — | 5,949 MH |
At roughly 1,300 productive hours per engineer per year (after leave, training and indirect work — the availability waterfall in our AMC1 145.A.30(d) guide), the naive plan says 3 engineers; the honest plan says 4.6, so 5. That is a 48% demand uplift over the brochure math — and it is all in factors you can show an auditor line by line.
1,100 × 2.6 × 1.30 × 1.60 ≈ 5,950 MH → 5 engineers, not 3
03Certifying staff: the six-month head start nobody budgets
Manpower is divisible; certification is not. A B1.3 or B2 certifier needs the type course, then OJT on the actual aircraft, then company authorisation — a pipeline of four to six months that cannot start before course slots exist. For the two-aircraft example above, assume certifying involvement on 25% of the 5,949 hours — about 1,490 certifying man-hours. Two freshly rated certifiers, each able to spend perhaps 35% of their productive year certifying while also working the floor, deliver roughly 900 hours. You are 40% short on the one resource you cannot subcontract at short notice. The fix is unglamorous: send three people, not two, on the first courses, and schedule the second course wave before entry into service, not after the first AOG night.
04Treat year one as a live re-forecast
The uplift factors above are planning assumptions, and AMC1 145.A.30(d) expects you to test assumptions against actuals. Log task-card actuals from day one, compare them against the proxy rate every quarter, and collapse the uplift factors as real data arrives — most fleets reach the mature rate between months 12 and 24. If actuals run hotter than the uplifted plan, you are in deviation territory and the quarterly review is where you catch it, not the audit. The organisations that get new-type introductions right are not the ones with the best guess — they are the ones who wrote down the guess so they could correct it.
Model the new type before it lands: set the proxy rate, apply your uplift factors, and see headcount and certifying coverage in numbers — with an auditor-ready PDF for the EIS planning meeting.
Run the scenario →