The thesis
Build the standard first; build every course from it. One document per platform — the Platform Qualification Standard (PQS) — defines every task a qualified pilot must perform, to what measurable tolerance, where it is trained, and how it is evaluated. The courses in the LMS, the written exams, the practical evaluations, the grade sheets, the training records, and the change-control process are all built from that one document. That is how one training lead delivers what normally takes a department: courses get built faster, stay consistent across instructors and customers, and update in step with the aircraft, because every one of them traces to a single source.
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 yet. Building it, and then building the courses from 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 table states only what each source document publishes. Sources: Heavy Lift Operator’s Manual Rev 1.1 and Herelink GCS Pilot’s Manual Rev 1.2; Commander 3XL specification sheet.
| Element | Heavy Lift | Commander 3XL | Transition treatment |
|---|---|---|---|
| Maximum takeoff weight | 80 kg (HL 2.2.1) | 25 kg / 55 lb | New memory item — retrain |
| Maximum payload | 30 kg (HL 2.2.1) | 10 kg / 22 lb | New memory item — retrain |
| Power system | 8 × 6S 25,000 mAh LiPo; 79.2 V minimum (HL 2.2.2) | Not published on spec sheet | Retrain from 3XL manual |
| Wind limit | Not published in Rev 1.1 | 35 km/h / 21 mph | New memory item; Heavy Lift limit to be established (see note) |
| Operating ceiling | Not published in Rev 1.1 | 2438 m / 8000 ft ASL | New memory item; Heavy Lift limit to be established |
| Operating temperature | Not published in Rev 1.1 | −25 °C to +38 °C | New memory item; Heavy Lift limit to be established |
| Endurance | Not published; payload-dependent | 50 min flight / 55 min hover | Planning differences |
| Assembly & inspection | Two-person, eight folding arms, 3-point propeller check (HL 2.3, 6.2) | Platform-specific | Retrain — P rows |
| Callouts, crew brief, site survey, checklists, RTL/abort logic, emergency decision structure, records | Common across Draganfly multirotors (Herelink GCS procedures) | Credit with differences training — C rows | |
By the row count in PQS-HL-01, 29 of 41 tasks are coded C and carry across with differences training; 12 are platform-specific and retrain. That is the difference between a two-week transition build and a two-day one, repeated for every airframe in the fleet.
A finding worth stating out loud: the Heavy Lift Operator’s Manual Rev 1.1 contains no environmental limits table — no wind, temperature, or ceiling limit — while the Commander 3XL spec sheet publishes all three. A qualification standard cannot require a pilot to memorize a number the manual doesn’t state. Establishing and publishing those limits with Flight Operations and Engineering is a change-control action that precedes the memorization bank, and it is exactly the kind of gap this framework is built to surface.
Currency, records & continuous improvement
Flight Operations needs to see at a glance who is current to fly what, pilots need to see and manage their own status, and everyone needs to be told before something expires. That is a system, not a filing cabinet — it gets its own page: Currency & Training Records, with the data model, the three user views (pilot self-service, instructor, Flight Ops dashboard), the email/SMS alert logic, three honest build options with named tools, and a working prototype of the currency matrix.
Two things from that system feed back into this framework. First, the audit chain: every grade sheet is the PQS task table graded and signed, stamped with the PQS revision in effect, so an auditor or accident board can walk grade sheet → PQS revision → manual revision in either direction. Second, program health measured from the same records — first-attempt pass rate per task, instructor grading variance, time-to-qualification, currency compliance, time-to-field a change — each closing 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.