Ottawa, Ontario
We build the scripts your simulator sessions run on.
Session scripts, evaluation design, and the structured data underneath them — written by people who have flown the line and taught in the box.
Fleet experience
- A220
- A320
- A330
- B737
- B767
- B777
- B787
Seven transport categories, plus military multi-engine operations.
The problem is rarely the content. It is the structure.
Most training departments already know what they want a crew to experience. What goes wrong is everything around it: scripts that drift out of alignment between fleets, event sets that mean different things to different instructors, weather in the briefing that contradicts the weather in the simulator setup, and a revision process that lives in tracked changes across a dozen Word files.
We fix that layer. We take the material a training department already has, give it a structure that holds up under revision, and hand back scripts that are consistent, checkable, and in the format the client actually uses.
What we do
Simulator script development
Complete scripts for full-flight simulator and FTD sessions, written to your SOPs, your fleet, and your training footprint. AQP and traditional recurrent, initial and upgrade, LOFT and qualification checks.
Script library modernization
Decades of inherited Word documents and PDFs converted into one structured, validated library — with instructor, student, and IOS-ready output from a single source.
Currency and compliance
Training material maintained against ATC procedures, AIRAC cycles, SIDs, STARs and approaches, weather formats, and regulatory change — with every affected session identified.
Fleet entry-into-service
Training material built from nothing for a fleet type new to the operator — script library, examinations, and program structure ready before the first aircraft arrives.
Training program support
Examination content and question banks, structured reference datasets, and advisory work for organizations building or restructuring an AQP-style program.
Entry into service
A new fleet type, and a date that will not move.
Entry into service is the one engagement where nothing exists yet and the deadline is set by an aircraft delivery. Everything has to be built from nothing — script library, examinations, program structure — and it has to be right first time, because there is no previous cycle to fall back on. We build the structure first, so the material scales as the fleet does rather than being rewritten after the first year.
- Built from zero No legacy material to inherit, and none to work around
- Fixed deadline The delivery date sets the schedule, not the other way round
- Regulator-facing Material has to satisfy approval, not just instruction
- Built to scale Structured on day one so year two is a revision, not a rebuild
Have a program that needs untangling?
Tell us what you are working with. First conversation costs nothing.