An Aviation Maintenance Technician school tracks students through a long curriculum and answers for every hour. AviationAlleykeeps the program hierarchy, enrollments, classroom attendance, and training records in one place — the same training engine that runs Part 141 and 142, pointed at your A&P courses, with a Part 147 cohort dashboard on top.
A curriculum hierarchy that mirrors your A&P program. The catalog and the student records share one structure, so what you teach and what you record stay in step.
Enroll students into a program; each enrollment tracks completed lessons and a live progress percentage that updates as work is logged.
Schedule classroom sessions against the roster and capture attendance per session — tied to the same students and programs everything else uses.
As lessons are logged, training records accumulate the completion history automatically, so the record isn't assembled in a panic the week before an audit.
Each student has a self-service portal that shows their own schedule and progress — the same progress the school sees, scoped to just that learner.
Each program becomes a cohort: enrolled / in-progress / graduated counts, active student body, classroom seats, and a graduation funnel for managers — all on one dashboard.
The operator view — challenges, wins, and the features that matter to an A&P school.
The same training engine for pilot training — stage checks and lesson tracking.
Run an A&P school alongside other FAR Parts in one login, each its own workspace.
Not yet. AviationAlley runs the training machinery an A&P school works from — a program → course → lesson hierarchy, enrollments and progress, classroom attendance, and training records — using the same training engine that runs Part 141 and 142 schools. A dedicated AMTS competency framework (competency-based curriculum subjects and AMTS competency records) is on our roadmap, not in the product today. The Part 147 cohort dashboard says so on its own face.
As a program → course → lesson hierarchy that mirrors how an A&P program is laid out. Each program is a cohort; courses sit under it; lessons sit under the courses. The catalog and the student records share the same structure, so what you teach and what you record stay in step.
Students are enrolled into a program, and each enrollment carries its completed-lesson count and a progress percentage that updates as lessons are logged. The cohort view rolls those per-student counts into a school-wide picture: enrolled, in progress, and graduated.
Yes. Classroom sessions are scheduled against an instructor and a roster, and attendance is captured per session. That gives you an attendance record tied to the same students and programs the rest of the system tracks.
Yes. Each student has a self-service portal where they see their own schedule and enrollment progress — the same progress the school sees. Portal access is scoped to that student only.
The Part 147 view treats each training program as a cohort and shows enrolled / in-progress / graduated counts, the active student body, classroom seats, and — for managers — a graduation funnel from enrolled through to completed. It reframes the platform's training data as an A&P-school cohort and progress view.