The Training System

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 standard, where it is trained, and how it is evaluated. Everything downstream is built from it: the courses in the learning management system (LMS), the exams, the practical evaluations, the grade sheets, the training records, and the change-control process. The single source is where the leverage comes from: courses get built faster, stay consistent across instructors and customers, and update in step with the aircraft — because every one of them traces back to the same document.

The structure is proven, not improvised: the FAA Airman Certification Standards — a task list with measurable standards that doubles as the practical test — combined with the proficiency coding the Air Force uses in its specialty training standards. Both have been refined over decades of certifying pilots and aircrew. Building that standard for each platform, and then building the courses from it, is the job.

One standard, six programs

Each training program is a rule applied to the same task table:

Program	Rule applied to the qualification standard
Initial	Every task in the standard, trained to full proficiency.
Recurrent	The safety-critical and perishable tasks (skills that decay without practice, flagged R in the standard), repeated on a set interval, plus the full memorization bank.
Transition	Only the tasks that differ between the two aircraft: tasks common to both (C) are credited with differences training, platform-specific tasks (PS) are retrained and re-evaluated.
Mission-specific	The base qualification plus an added block of tasks for that job — payload profile, survey pattern, or specialized tasking.
Customer	The qualification scoped to that customer’s requirements and mission-specific tasks.
Instructor	Teaching and evaluating proficiency (P3) on designated tasks, plus the instructor standard’s own teaching and grading tasks.

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 task. Both courses on this site — Heavy Lift Initial Qualification and Instructor Initial Qualification — are built from that standard, and through it from those manuals.

The standard course sequence

Every platform course is built to the same six-block architecture. Blocks are taught in order, and within each, the ground portion always precedes the flight portion:

1. Operating limitations — the numbers that define safe flight, memorized before anything else.
2. Immediate action items — the boldface: actions performed from memory, before any checklist. Ten of the Heavy Lift’s twenty-one emergency procedures have them.
3. Aircraft and payload systems — deep knowledge of the machine behind the numbers.
4. Normal operations — takeoff, landing, and visual-line-of-sight flying: the procedures required for any flight, whatever the mission.
5. Emergency procedures — every procedure expanded in full, beyond the memory items.
6. Mission-specific operations — mission planning and the add-on blocks for a particular use: payload profiles, survey or inspection patterns, customer- or site-specific taskings.

Crew coordination is trained where the operation calls for it — two-person crews, visual-observer-dependent operations — appended to whichever block it applies to.

The order is deliberate. The highest-consequence items — operating limitations and immediate action items — are trained first and to the highest standard, because they have to be available without reference. Systems knowledge is built underneath them, and mission employment comes after basic qualification. Sequencing every platform the same way makes courses comparable: an instructor, a customer, or an auditor always knows where to find something.

Worked example: transition training, Heavy Lift → Commander 3XL

A pilot moving between platforms doesn’t repeat the whole course. Every PQS row carries a transferability code (C = common across Draganfly multirotors; PS = platform-specific), the transition course is generated by subtraction: credit what transfers, retrain the difference. That difference — the transition delta — is the entire course. The table below states only what each source document publishes. Sources: Heavy Lift Operator’s Manual Rev 1.1 and Herelink ground control station (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	New memory item — retrain
Maximum payload	30 kg (HL 2.2.1)	10 kg	New memory item — retrain
Power system	8 × 6S 25,000 mAh lithium-polymer (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	New memory item; Heavy Lift limit to be established
Operating ceiling	Not published in Rev 1.1	2438 m 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 — tasks marked PS
Callouts, crew brief, site survey, checklists, return-to-launch (RTL)/abort logic, emergency decision structure, records	Common across Draganfly multirotors (GCS 1.2, HL 4.1)		Credit with differences training — tasks marked C in the PQS Transfer column

By count in PQS-HL-01, 33 of 45 tasks are marked C and carry across with differences training; 12 are platform-specific and retrain. The same comparison runs for any pair of aircraft, so adding a platform to the fleet costs only the tasks that are genuinely new.

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.

Both work because every grade sheet is the PQS task table: each evaluation produces a result against a task ID, with no extra paperwork. A low first-attempt pass rate on one task points at the lesson teaching it; a wide grading spread between instructors on the same task points at the wording of the standard. A quarterly review turns those into a revision list, and revisions ship through change control with an effectivity date. The same task IDs carry the audit chain — grade sheet → PQS revision → manual revision — walkable in either direction.

Where I’d start

From there the framework repeats for each platform, customer, and mission type. AI speeds up drafting inside the structure the standard sets — the standard defines what a course contains — and field instructors validate every deliverable before release.