Differences Training

Differences training is the economical answer to a fleet that is not uniform. When a crew member already qualified on a type is to operate a variant of it, retraining the whole type would be wasteful; differences training covers only what actually differs, and leaves the rest of the qualification standing.

For cabin crew the rule is ORO.CC.130, sitting immediately after aircraft type specific training and operator conversion training at ORO.CC.125 — and the two are addressed together in the acceptable means of compliance, because in practice the boundary between a new type and a variant of an existing one is where the judgement lies. The same concept runs through flight crew training, where differences and familiarisation requirements are defined against the operational suitability data for the type.

What counts as a difference is anything that changes what the crew member must do or know: cabin layout and exit configuration, the location or type of emergency equipment, door operation, evacuation procedures affected by the layout, and any safety equipment the variant carries that the base type does not. A variant that differs only in engines or avionics may make no difference at all to cabin crew while making a substantial one to pilots, which is why differences requirements are assessed per crew discipline rather than per aircraft.

The record-keeping consequence is subtle and is where fleets go wrong. A crew member's qualification is no longer a single fact about a type; it is a base type plus a set of variant differences, each completed on its own date. An operator with several variants ends up with a matrix of person against variant, and assignability depends on reading the right cell. When that matrix lives in a spreadsheet maintained alongside the training records rather than inside them, the two drift, and the drift is invisible until somebody is rostered onto a variant they were never trained for.

There is also a decision to be made before any of this, and it is a judgement rather than a lookup: whether a given aircraft is a variant requiring differences training or a different type requiring the full course. That determination follows the operational suitability data for the aircraft and the operator's own assessment of what actually differs for the crew discipline in question, and it has to be documented. Getting it wrong in the permissive direction — treating a type as a variant — produces crew who have had a short course where a full one was required, and every subsequent record built on that qualification inherits the defect.

Differences training is where fleet planning and training administration meet. Every variant added to a fleet multiplies the training matrix, and the cost of that is borne by the training department long after the aircraft acquisition decision is made.

The administrative problem is one of granularity. A system that records qualifications at type level cannot express 'qualified on the type, current on two of its three variants', which is the actual state of most crew members in a mixed fleet. Organisations compensate with side records, and side records are exactly what audits find.

ORO.CC.250 adds the related constraint for crew operating on more than one type or variant, which is the point at which the matrix stops being a convenience and becomes a limit on how the operator may roster.

That rule is worth reading alongside the matrix rather than after it. Operating on more than one type or variant is permitted, but the operator has to define how — which combinations it allows, what training and checking support them, and how currency is maintained across all of them simultaneously. An operator that adds variants without revisiting this ends up with crew who are individually qualified on paper and collectively difficult to roster, because every assignment has to be checked against a combination rule nobody has written down.

Aviatize records qualifications against the specific aircraft or variant rather than only at type level, so 'qualified on the type, current on these variants' is expressible as data instead of as a note somebody maintains separately.

Differences courses are configured as their own short course structures with their own events and checks, so completing one updates the crew member's record in the same place the base type qualification lives — there is no second system to keep in step.

Because the same records back the Validation Engine's booking preconditions, assignment to a variant the crew member is not current on can warn or block at the point of rostering rather than being caught later.