The thesis
I don’t build courses. I build the qualification standard that generates courses. One document per platform — the Platform Qualification Standard (PQS) — defines every task a qualified pilot must perform, to what measurable standard, where it is trained, and how it is evaluated. The syllabus, the lesson plans, the written exams, the practical evaluation, the grade sheets, the training records, and the change-control process are all derivations of that one document. That is how one person delivers the output of a department: not by working faster, but by building the object everything else generates from.
The model isn’t invented — it is the FAA Airman Certification Standards fused with the USAF specialty training standard: a task list with measurable standards that doubles as the test. Draganfly’s platforms don’t have one. Building it is the job.
One standard, six programs
Initial, recurrent, transition, mission-specific, customer, and instructor training are not six builds — they are six rules applied to the same task table:
| Program | Rule |
|---|---|
| Initial | All rows, to stated proficiency |
| Recurrent | The safety-critical and perishable subset (rows flagged R), on an interval, plus the full memorization bank |
| Transition | The delta between two platforms’ standards: common rows credit with differences training, platform-specific rows retrain |
| Mission-specific | Base qualification + an appended task block (payload profile, waiver-governed operation) |
| Customer | Initial or transition set scoped to the customer’s approved operations and equipment |
| Instructor | Teach-and-evaluate proficiency on designated rows + the instructor qualification standard (see Instructor Standardization) |
See the Qualification Standards page for the working sample — PQS-HL-01, built for the Heavy Lift from Draganfly’s own operator and GCS manuals, with a source reference on every row. The two published courses on this site (Courses) are both derivations of it.
Worked example: the transition delta, Heavy Lift → Commander 3XL
Because every PQS row carries a transferability code, a transition course is generated by subtraction, not authored from scratch. The crew procedures, callouts, planning discipline, and emergency decision logic carry over as differences training; what retrains is the new airframe’s numbers and hands-on tasks:
| Element | Heavy Lift | Commander 3XL | Transition treatment |
|---|---|---|---|
| Max takeoff weight | 80 kg | 25 kg (55 lb) | New memorization bank — retrain |
| Max payload | 30 kg | 10 kg (22 lb) | New memorization bank — retrain |
| Wind limit | per ops policy | 35 km/h (21 mph) | New memorization bank — retrain |
| Operating ceiling | per ops policy | 2438 m (8000 ft) ASL | New memorization bank — retrain |
| Endurance | mission-planned | 50 min (55 min hover) | Planning differences |
| Assembly / inspection | 2-person, 8-arm | platform-specific | Retrain (P rows) |
| Callouts, crew brief, site survey, RTL/abort logic, records | Common across Draganfly multirotors | Credit with differences training (C rows) | |
Roughly two-thirds of the Heavy Lift standard carries across — which is the difference between a two-week transition build and a two-day one, repeated for every airframe in the fleet.
Records & continuous improvement
The records test every system must pass: “For any pilot, on any date, produce the evidence they were qualified for that flight.” The record model is simple because the standard does the work: the grade sheet is the PQS task table, graded and signed; the training matrix is person × qualification × expiry with automated alerts at 60/30/0 days; and every grade sheet carries the PQS revision in effect, preserving the audit chain — grade sheet → PQS revision → manual revision. When Engineering changes the aircraft and the manual revises, the standard identifies exactly which lessons, exams, and checklists are affected, and which qualified pilots need a bulletin, differences training, or re-evaluation, with an effectivity date.
Program health is measured, not assumed: first-attempt pass rate per task (a heat map of which lesson is broken), instructor grading variance on identical tasks (standardization health), time-to-qualification, currency compliance, time-to-field a training change after a product revision, and field safety findings traced back to task IDs. Each metric closes a loop back into the standard.
Where I’d start
Days 1–30: inventory and gap analysis — contractually and regulatorily obligated training first, then risk exposure, then fleet size, then rate of change; pick the pilot platform. Days 31–60: build that platform’s PQS and one complete course from it, as the template. Days 61–90: instructor standardization, fielding, and the change-control loop live. The framework then repeats per platform at a fraction of the first build’s cost — accelerated by AI drafting inside the fixed schema, with field instructors validating and nothing fielded without their sign-off.
Sample material prepared for an interview demonstration. Not an official Draganfly Inc. publication.