Evidence Capture
In CBTA the assessment is only as good as the evidence behind it. If the instructor cannot point to a specific moment in the session that demonstrates a competency was or was not met, the mark cannot stand up to audit. Evidence capture is the discipline of recording what actually happened (what the trainee did, when, against which observable behavior) so that the judgment that follows has something solid underneath it.
We saw instructors struggling to capture all the data they need, manage the training session, a complex (simulator) interface or challenging flight condition and educate the trainee all at the same time. We think the instructor should focus on educating the trainees. So we automated the data capture, while strictly applying the toughest regulations on earth regarding data capture: the EU GDPR framework.
WingMentor’s evidence layer is tracing paper. It lays over the session and preserves what was there. Designed to help you. And nothing else.
What we capture
The pieces that matter for an evidence-based assessment:
- The flight phase or training event at each moment of the session.
- The observable behaviors demonstrated, mapped to the competency framework your operator uses.
- The trainee’s actions in the operator’s own words, not summarized, not paraphrased, not interpreted.
- The instructor’s annotations, timestamped against the moment in the session that produced them.
- The references the instructor consulted (operator SOPs, regulatory excerpts, prior session notes) at the moment of the mark.
The structure is anchored in ICAO Doc 9868 PANS-TRG, which defines the observable behaviors framework that EBT and CBTA depend on. The mapping between PANS-TRG, your authority’s interpretation (EASA EBT Manual, FAA Advisory Circular 120-71B, or your local regulator), and your operator’s specific framework is visible at every level. You see where each behavior comes from. We do that while protecting your sensitive data using the most secure protocols.
What we do not capture
We do not capture inference. If the instructor watched the trainee and concluded that workload management was deteriorating, the conclusion is the instructor’s. The evidence is the specific behaviors observed (rate of cross-check, response to abnormal callouts, communication tempo). The conclusion is yours to mark. The evidence supports it. It does not produce it.
We do not capture off-topic or candid communications. We do not capture our guess at what the trainee was thinking. We do not capture flight or simulator-generated scores as the assessment. Where the operator chooses to include flight or simulator data, it is recorded as one source of evidence among others, not as a verdict.
The instructor’s editorial control
You can mark a piece of captured evidence as ambiguous. You can mark it as evidence for one competency rather than another. You can mark it as evidence against your initial read of the trainee. You can withdraw a mark and replace it. Every change is timestamped. The audit trail shows what you saw and what you concluded, not just the final mark.
The trainee’s record is the instructor’s record. The instructor edits it. The system stores it.
See it
What the evidence layer is anchored in.
- ICAO Doc 9868, PANS-TRG (Procedures for Air Navigation Services, Training, incl. Amdt. 7)
- ICAO Doc 9995, Manual of Evidence-Based Training
- EASA EBT Manual, latest edition dated 09.04.2024
- FAA Advisory Circular 120-71B (Standard Operating Procedures and Pilot Monitoring Duties for Flight Deck Crewmembers)