Simulation & Training
Exercising flight software and pilots against conditions that are expensive, dangerous or simply inconvenient to arrange in the air.
Simulation and regression testing
Flight software changes must be tested against realistic conditions before flying, and previously fixed problems shown to stay fixed.
SITL is widely available but used almost universally as a manual sanity check rather than an automated harness. There is rarely a scenario library, so each change is tested against whatever the engineer thinks to try, and regressions are found in the air.
Scenarios as versioned assets: wind, turbulence, sensor degradation, link loss and terrain, run as a suite on every flight software change. The aircraft model comes from Planform and Camber, so simulation reflects the actual design. Failures report as a diff against the last known-good run.
A controller gain revision that passed manual testing and failed two scenarios in the crosswind-landing suite, caught before flight.
Remote pilot training and currency
Pilots must be trained, assessed and kept current, with records satisfying an RPTO or operations manual.
Training runs on real aircraft in real airspace: expensive, weather-dependent, and limited to conditions safe to arrange. Emergency handling is what most needs practice and is hardest to rehearse safely.
Training scenarios run on the same simulation core as Crosswind against the same aircraft models, so what a pilot practises matches what they will fly. Emergencies are rehearsed to competence, and assessment results flow into Hangar as currency records.
A conversion programme where pilots reached assessment standard with a materially reduced share of training conducted on live aircraft.
Tell us what you are flying and where the programme is losing time. We will tell you honestly which of these helps and which does not.