Project each student from the lessons left in your syllabus at their own recent pace, then check every week against what your fleet, simulators and instructors can give. Where demand is higher than capacity, everyone slows down, and that difference is what capacity costs you in weeks.
Start from each student
- What's left: the lessons still to fly, in syllabus order, each dual, solo, night or simulator as the syllabus says.
- Their pace: the flights a week they've flown recently (PilotMetrics uses the last 8 weeks), skipping their planned breaks. A student with no recent flights takes their cohort's average.
Then add capacity
Students can only fly as much as the school can give. For each week ahead:
- Aircraft: the share of daylight (and darkness, for night lessons) each type actually flew in its busier recent weeks, which takes in weather, maintenance and turnarounds, applied to that week's own daylight. Capacity then follows the seasons: shorter days in winter, short nights in summer.
- Instructors: their working hours, less briefings and admin, less the days they're away, going to the lessons they can teach. Solo lessons need no instructor.
- Simulators, for the lessons that use them.
When students want more than a week can give, each share is cut in proportion.
Read it by cohort
- When the middle of the cohort (half its students) and its last student are projected to finish, against its expected end.
- The flights a week it's flying, against what finishing on time needs.
- Which phase each cohort will be in, month by month, and how long each phase has actually taken students who finished it.
- Students whose theory exam passes run out before their projected finish (see how long theory exams are valid).
A projection at today's pace from the figures, not a promise, and never a judgement of a student or instructor.