A-check manpower planning: the 50-hour inspection that eats a week
The 600-hour check gets the planning meeting. The small check gets a line in the maintenance programme — and that is exactly why it breaks the roster. Whether your programme calls it an A-check, 50-hour, 100-hour or equivalent inspection, the demand arrives one aircraft at a time, all month, until it quietly consumes more manpower than a base input.
01Count events, not aircraft
The common mistake is to write “six aircraft” beside the monthly plan and treat the small check as background noise. It is not driven by aircraft count. It is driven by forecast utilisation divided by interval. If the fleet flies more, the same six aircraft generate more events — and the events bunch into the weeks the operation is busiest.
Worked example: six AW139s forecast at 65 flight hours each per month. Fleet utilisation is 390 FH/month. With a 50-FH inspection interval, the plan must absorb 390 ÷ 50 = 7.8 events. In a real roster, that means eight inspections, not an average of 0.8 per aircraft.
02Price the whole event, not the task cards
A clean 50-hour package might be only 14 man-hours on paper. The aircraft still has to be positioned, opened, inspected, rectified, ground-run, closed and released. If your plan only carries the printed routine package, it is guaranteed to be short.
| Monthly work block | Planning basis | Man-hours |
|---|---|---|
| Routine inspection cards | 8 events × 14 MH | 112 |
| Recurring SBs and local work orders | 8 events × 2 MH | 16 |
| Findings allowance | 35% of routine cards | 39 |
| Ground run and operational checks | 8 events × 3 MH | 24 |
| Records, work pack and release | 8 events × 2 MH | 16 |
| Total monthly demand | all drivers included | 207 |
That “14-hour check” is actually a 207-man-hour monthly demand. Divide by 4.33 weeks and the fleet needs about 48 productive man-hours every week. At a realistic 30 productive hours per engineer per week, that is 1.6 FTE before daily line rectification, aircraft-on-ground response or training.
03The release window is the real constraint
Headcount alone still does not release the aircraft. Each event has three points where the right licence category must be available: task certification as panels close, ground-run oversight, and final release to service. If the only available B1 is committed to a departure troubleshooting job at 17:30, the finished inspection waits until morning and your “one-shift check” becomes an aircraft-day lost.
- Plan by tail number: carry-forward hours tell you which aircraft reaches the interval first, but utilisation drift changes the order.
- Reserve a release slot: protect a certifying-staff window before the planned completion time, not after the work cards are signed.
- Do not stack events: two aircraft due in the same week need two release windows, even if the routine hours fit one crew.
04The five-line planning method
Use this in the next man-hour plan review: forecast fleet hours; divide by interval to get events; multiply by the true package hours; add a findings factor from your own history; then convert the total to productive FTE and check the B1/B2 release windows. If the answer exceeds one full engineer, the “small check” deserves its own line in the AMC1 145.A.30(d) plan and a quarterly planned-versus-actual review.
Enter your fleet hours, inspection interval and package size in the calculator to turn small checks into monthly man-hours, FTE demand and a coverage gap you can show management.
Plan the inspection workload →