aeroEBT
EBT & CBTA platform for airlines and ATOs
Keep your EBT programme from drifting. Prove it to your authority.
We turn EBT from a complex process into a simple daily operation.
AeroEBT runs the full ORCA cycle (observe, record, classify, assess, debrief, report, calibrate) and standardisation compliance is monitored underneath it. Instructors get one practical procedure: open the session, grade, debrief. Nobody has to learn a tool. Aligned to ORO.FC.231 and ICAO Doc 9995.
Setting up AeroEBT
Set up in under 15 minutes. Your EBT settings and your whole programme, not months of work.
AeroEBT sets up your EBT settings and your whole programme in less than 15 minutes instead of months, with compliance assured and quality for your fleet.
- Setting up an EBT programme by hand
- Months
- With AeroEBT
- Under 15 minutes
It starts from ready-made data
Procedure lists, failure databases, event libraries and the A/B/C topic lists for the whole programme are already there for your aircraft type.
Compliance assured
Built around EASA ORO.FC.231 and ICAO Doc 9995, with A/B/C topic coverage (ORO.FC.232) checked as the programme is built, not in a meeting afterwards.
Quality for your fleet
Every instructor on the fleet works from the same programme and the same scenario reference, and concordance is measured from the grades they enter.
SkyDynamics' figure for setting up the EBT settings and the programme in AeroEBT on an aircraft type with ready-made data. Importing records, training instructors and the parallel run follow in your first 90 days.
A technology developed by SkyDynamics
Every action already knows its background. The Contextual Composition Protocol, behind every AeroEBT application.
The Contextual Composition Protocol works behind the scenes of every AeroEBT application: the Scenario Builder, the instructor app, concordance and reporting. It holds all the data relevant to a specific task or workflow in memory, so whenever someone acts, the system already knows the background.
Comment on an event or a failure, for example, and the protocol is already holding the scenario, the failure information and the whole scope of the programme. It correlates them with any other data attached at that moment, with high specificity.
In the EBT Scenario Builder
High-clarity scenario generation: training departments go from the A/B/C topic list to a finished, compliant scenario without separate evaluation rounds and review meetings.
- Every comment and change is made with the whole scenario and its failure information behind it, so scenarios come out clear and compliant in fewer steps
- A/B/C topic coverage (ORO.FC.232), malfunction equivalency and competency distribution are checked while the scenario is written, not in a meeting afterwards
In the instructor app
In the CBTA and ORCA process it works during recording and assessment, so every instructor observes and assesses with the same correlated context. That is how an airline works towards world-class concordance and instructor standardisation.
- The app holds the scenario phase, the event in play and the observable behaviours it is designed to elicit, so every instructor looks for the same evidence
At these key points the protocol works behind the scenes, giving every scenario decision and every grade the fullest possible justification, and it supports instructor standardisation where required. It never intervenes in what a designer or instructor decides, and nobody has to learn how to use it.
Airline use case · EBT scenario development
Steps 1 to 9 in about two hours, by one person.
An airline training department builds each EBT scenario through thirteen stages today: a specification approval, design drafts and meetings, a compliance check, an email review round, two simulator runs and a classroom standardisation meeting before the scenario reaches its instructors. With AeroEBT, the Contextual Composition Protocol already gives every step its context, so one person completes steps 1 to 9 in the EBT Scenario Builder in about two hours. Validation becomes one optional simulator run, and the scenario goes straight to distribution. The result is far fewer man-hours, a scenario that carries its own compliance evidence, and instructors who start from the same reference.
- Steps 1–9, specification to checked scenario
- Today A team, meetings and email
- With AeroEBT: One person, about 2 hours
- Draft versions
- Today 3
- With AeroEBT: 1
- Simulator runs before release
- Today 2
- With AeroEBT: 1, optional
- Classroom standardisation meeting
- Today 1
- With AeroEBT: None
- Main flow
- Feedback loop
- Approval, meeting or review round
- 1
OMD & manuals
EBT·CBTA standards
- 2
SpecificationEvery semester
A/B/C list approved
- 3
Designers
scenario & training
- 4
DraftsMeetings
shared & iterated
- 5
Draft 1
consolidated
- 6
Compliance checkRework loop
balance & smoothness
- 7
TRE reviewEmail round
optional, by email
- 8
Draft 2
revised
- 9
Sim 1
instructor trial
- 10
Sim 2
instructor trial
- 11
StandardisationMeeting
classroom meeting
- 12
Final version
distributed to instructors
- 13
In useCalibration loop
TREs with trainees
- 1–9
Scenario Builder sessionone person · about 2 hours
The OMD standards and the approved A/B/C specification are already in the builder. One person drafts with AeroBrain, sees compliance, smoothness and the distribution of competencies, complexity and difficulty while writing, and checks every event against the aircraft procedures and the simulator's failure list. The drafts, meetings, email review and design check in the simulator fold into one session.
- 10
One validation runoptional
If the training department wants it, one simulator run from the instructor app confirms the scenario. A second run to catch design errors is no longer needed.
- 11
Standardisationmeeting skipped
No classroom meeting. Each instructor receives the scenario's intent and the observable behaviours it calls for at each step of the instructor app.
- 12
Distributionto every instructor app
The approved scenario goes straight to the instructor app on every iPad, the same version at every base.
- 13
In useconcordance measured
Grades feed concordance automatically. Calibration goes only where drift shows, and the findings flow into the next specification.
The Contextual Composition Protocol holds and correlates
- OMD & A/B/C specification
- Competency framework & grading scale
- SMS findings
- Aircraft & simulator catalogue
- Grading history & concordance
What changes for the training department
Man-hours
Today. Designers, TREs and instructors spend time across drafts, meetings, an email round, two simulator sessions and a classroom meeting.
With AeroEBT: Steps 1 to 9 become one person's session of about two hours. The second simulator run and the classroom meeting drop out.
Observability
Today. Why a scenario looks the way it does is spread across meeting notes, email threads and draft files.
With AeroEBT: The scenario carries its own evidence: the specification topic behind each event, the coverage and balance checks, and the approval.
Compliance
Today. Compliance and balance are checked after Draft 1, and an unbalanced draft goes back for rework.
With AeroEBT: A/B/C topic coverage (ORO.FC.232), malfunction equivalency and competency distribution are checked while the scenario is written.
Concordance
Today. Instructors align in a classroom meeting, then drift apart again between cycles.
With AeroEBT: Every instructor gets the same intent and observable behaviours at the same step in the app, and drift is measured from the grades that follow.
About two hours for steps 1 to 9 is SkyDynamics’ figure for one trained user of the EBT Scenario Builder; it varies with scenario complexity. The specification is still approved by the training manager or a designated person, and the simulator validation run stays available whenever your training department wants it.
Enhanced EBT · from your SMS to the simulator
Train for the risks your own safety data shows, not a generic list.
Enhanced EBT starts where your safety management system ends. The occurrences, flight-data trends and audit findings your SMS already holds are translated into the EBT scenario design method: each finding becomes the threats, errors and competencies a scenario has to elicit. The EBT Scenario Builder, the world's first Scenario Builder for EBT and CBTA training, turns that design brief into instructor scripts from your aircraft catalogue, with competency coverage checked across the whole cycle as it is written. Your safety department sees the risk; your simulator trains for it.
- SMS input: occurrence reports, FDM/FDA trends, LOSA and audit findings: the data your safety department already collects
- Translated into scenario design: each finding mapped to the threats, errors, observable behaviours and competencies it points at
- Built in the EBT Scenario Builder: aircraft-aware events, real-time coverage across scenario, group and cycle, with assist, semi-agentic and agentic authoring
- Flown and graded in the instructor app, so the next cycle shows whether the risk actually moved
- Operator-specific tailoring as ORO.FC.231 and ICAO Doc 9995 intend, evidenced, not asserted
EBT Scenario Builder · where every programme starts
Great EBT starts with a great scenario.
No EBT programme succeeds without its foundations. The world's first Scenario Builder for EBT and CBTA training, and still the only one of its kind, makes the foundation simple: your safety data in, the Contextual Composition Protocol holding the whole scenario behind every change (the AeroBrain assistant is optional), and requirements, coverage and difficulty checked in real time, then the same scenario runs in the instructor app.
Your safety data
- Occurrences
- FDM / FOQA trends
- Audit findings
Contextual Composition Protocol
- The whole scenario held in memory
- Every change made in context
- AeroBrain assistant, optional
Checked in real time
- Requirements
- Coverage
- Difficulty
Instructor app
- The same scenario
- Its intent and observable behaviours
- Offline on iPad
Built from your SMS data
Occurrences, FDM / FOQA trends and audit findings translated into prioritised training needs and scenarios.
Contextual Composition Protocol
Every comment and change is made with the whole scenario and its failure information behind it. The AeroBrain assistant is optional: Draft, Fill gaps, Coverage and QA, with every draft checked before you apply it.
Real-time requirement checks
Competency and observable-behaviour coverage, regulatory topics and equivalency checked as you write.
Complexity and difficulty
Load, difficulty and complexity per phase and for the whole scenario, against the target for the trainee group.
Tailored to the group
Weight the design focus toward the competencies a trainee group is struggling with.
Day-one aircraft database
B777, B787, A320, A220, A330, A350, Q400 and ATR 72 procedures, and a failure list per simulator.
Where EBT programmes break
Three problems every Head of Training recognises
Drift
Within two to three years, many programmes slide back from training to checking. Nobody decides it; it just happens.
Concordance
Two instructors, one crew, two different grades. Without measuring it, your training data is partly noise.
Evidence
The data exists, but the story your authority asks for (what you saw, what you changed, what improved) takes weeks to assemble.
Find your version
The same cycle, whoever you train
What has to be evidenced differs by organisation and by role. Start where you actually sit.
One cycle
Observe, record, classify, assess, debrief, report, calibrate
- AirlinesRecurrent and mixed or full EBT under ORO.FC.231, across fleets and bases, with concordance measured and authority evidence from live data.
- Flight schools & ATOsAb initio from the first lesson under Part-FCL, with competency marks per lesson, and students leave with their digital logbook.
- Maintenance training organisationsPart-147 and Part-66 competency assessment, plus a digital logbook for engineer experience and authorisations.
- Cabin crewInitial, recurrent, differences and SEP training assessed and recorded in the same system as the flight deck.
- Air traffic controllersUnit training, OJT and continuation training on the same assessment method.
What it asks of your people
Nobody has to learn the tool.
Standardisation monitoring, competency mapping, coverage analysis and audit evidence are complicated problems. That complexity belongs to us, not to a line captain who instructs eight days a month. Your instructors get one procedure (open the session, grade, debrief) and everything else assembles itself underneath.
- One practical procedure for the instructor, unchanged from session to session
- Concordance measured from the grades they already enter: no extra step, no separate exercise
- No parallel forms, no second system, no "remember to also tick this"
- Training standards get the analysis without asking instructors to produce it
- An instructor can be productive in their first session, not after a course on the software
In the simulator
Focus on training, not the app.
In the simulator, an instructor's attention belongs to the crew. The AeroEBT instructor app on iPad is built to stay out of the way: notes are written as the session happens, typed or handwritten, online or offline. Those notes power everything else. AeroEBT proposes the observations and related competencies from them, the instructor confirms, and the evidence behind each grade is ready for the debrief and the EBT training record.
- Notes, typed or handwritten, become proposed observations that the instructor confirms
- Grading to your competency framework and your grading scale, in three taps or fewer
- Works offline inside the device; synchronises automatically
- Signatures and paper-parity PDF records
Instructor concordance
See who grades differently, and why.
AeroEBT measures inter-rater reliability per instructor against your fleet baseline, so your training standards team can target calibration where it matters instead of re-briefing everyone.
- Grading drift per instructor against the fleet baseline
- Calibration sessions planned and recorded in the same system
- Grading can be reopened and corrected with a full audit trail
Debrief
Grades say what. Notes say why.
The most useful evidence in EBT is in the instructor's narrative, not the number. AeroEBT reads free-text notes and proposes the observations and related competencies they contain; the instructor confirms or corrects. The instructor remains the assessor.
- Observations extracted from instructor notes, confirmed by the instructor
- Trends across the pilot population, not just individual sessions
- Suggestions checked against your regulatory references
The ORCA cycle
Observe · Record · Classify · Assess · Debrief · Report · Calibrate
Evidence-based training is a loop, not a checklist. AeroEBT is built around the seven steps that loop actually contains, and the two most programmes never close are the last two.
Observe
The instructor watches behaviour, not items: what the crew did, when, and under what pressure. The app stays out of the way so the eyes stay on the crew.
Record
Observations and notes are captured in the moment, on iPad, offline in the device, not reconstructed from memory an hour after the session.
Classify
Each observation is tied to the competency and behaviour it evidences, so the record says what was seen rather than only what was scored.
Assess
The instructor grades against your framework and scale. The grade carries its evidence, and can be reopened with a full audit trail.
Debrief
The facilitated debrief is where the learning happens. Notes become confirmed observations, so the narrative survives the session instead of evaporating.
Report
The pilot record, the programme view and the authority pack come from the same data: no assembly week before an audit.
Calibrate
Concordance is measured against the fleet baseline and calibration is planned, run and re-measured. Without this step the loop degrades and the data drifts.
The product
Five screens, one cycle
The ORCA cycle as your instructors and your standards team actually work it.
Observe & Record
Behaviour captured in the moment, on iPad, offline in the device.
Step 1 of 5
Classify & Assess
Observations tied to competencies and behaviours, then graded against your framework.
Step 2 of 5
Debrief
Notes become confirmed observations, so the narrative behind the grade survives the session.
Step 3 of 5
Report
The pilot record and the authority pack come from live data rather than three weeks of assembly.
Step 4 of 5
Calibrate
Concordance measured against the fleet baseline, calibration planned and re-measured.
Step 5 of 5
The full framework
The whole EBT cycle in one record
The session
Scenario assessment, grading and inter-rater reliability.
The programme
Competency matrix, cycle planning and the line training phase.
The evidence
Audit-ready reports and one record per pilot.
Scenarios on devices that can credit them
With FCS++, your programme sees each simulator's FSTD Capability Signature, so EBT sessions are scheduled on devices whose fidelity supports them. Required-fidelity tags on scenarios are on the roadmap.
Migration
Mixed EBT today, full EBT on your timeline.
Full-EBT programme template
Start from a pre-built programme; your existing data comes with you.
Scenario coverage
AeroBrain highlights coverage gaps against your regulatory references.
Same app for instructors
The iPad flow, signatures and notes stay the same through the migration.
Migration timeline
See where your programme is today and where it will be at each step.
For the Accountable Manager
What the programme costs, and what it delivers
Cost visibility
Training spend per pilot, per course and per simulator hour, so utilisation decisions rest on data.
One standard across bases
Every base, instructor and fleet grades to the same framework and scale.
Audit-ready records
Records for your authority, always current: no scramble before an inspection.
Early warning
Competency trends across the pilot population, visible before they reach the line.
Implementation
Your first 90 days. From mapping your EBT programme to go-live, with a parallel run.
A typical rollout. Timings are agreed with you after the demo.
Week 13 of 13: Go live
Ready-made training data
Aircraft types with existing scenario data
Pre-built scenarios, training documentation, procedure lists, failure databases and event libraries are available for these types, together with the A/B/C topic lists for the whole programme.
Airbus
- A320Airbus A320
- A220Airbus A220
- A330Airbus A330
- A350Airbus A350
- A380Airbus A380
Boeing
- B777Boeing 777
- B737Boeing 737
- B787Boeing 787
De Havilland Canada
- Q400Dash 8-400
ATR
- ATR 72
Embraer
- E195Embraer E195
- E190Embraer E190
- E175Embraer E175
- E170Embraer E170
EBT does not end at the simulator. It connects to the device, the fleet baseline and the pilot's path to the line.
The simulator session
Observed, graded and debriefed in AeroEBT.
FCS++
Each simulator's Capability Signature, visible to the training programme.
Learn moreAeroBrain
Grading drift flagged against the fleet baseline.
Learn moreMPL programme
Competency tracking from the first cadet lesson to the line.
Learn morePilot pipeline
One pilot record from the ATO to the line.
Learn more
Further reading
Instructor concordance
How to measure and close the grading gap.
Learn moreMixed to full EBT
Prerequisites, phases and the pitfalls that stall programmes.
Learn moreFor Heads of Training
The programme, the standard and the evidence.
Learn moreHow AeroEBT compares
Administration suites, grading apps, OEM programmes, and the questions to ask.
Learn more
Security & data
Your training records, under your control. Processed in the EU, on your own infrastructure where required, and exportable.
Pick a point to mark it in the diagram.
Plans
Licensing for every organisation
Priced by pilot population and modules. Every plan includes EU data residency and GDPR-compliant processing. Talk to us for a quote.
Professional
For ATOs and flight schools.
- AeroEBT core
- Up to 50 pilot profiles
- Scenario Builder (Basic)
- Offline sync
- Standard reports
- Email support
Enterprise
For airlines and large ATOs.
- Full AeroEBT suite
- Unlimited pilot profiles
- Advanced Scenario Builder
- AeroBrain analytics
- Custom reports
- API access
- On-premises option
Complete
The full training ecosystem.
- Everything in Enterprise
- TMS integration
- FSMS integration
- Custom integrations
- Dedicated success manager
AeroEBT: questions Heads of Training ask
What is the Contextual Composition Protocol?
It is a technology developed by SkyDynamics that works behind the scenes of every AeroEBT application: the Scenario Builder, the instructor app, concordance and reporting. Nobody operates it directly. It holds all the data relevant to a specific task or workflow in memory, so at every moment the system knows the background to what the user is doing. When a designer comments on an event or a failure, for example, the protocol is already holding the scenario, the failure information and the whole scope of the programme, and it correlates the comment with any other data attached at that moment. In the EBT Scenario Builder this gives high-clarity scenario generation with fewer steps and review meetings. During recording and assessment in the CBTA and ORCA process, the instructor app gives every instructor the same correlated context, which is what instructor concordance depends on. At these key points it works behind the scenes, giving every decision and every grade the fullest possible justification and supporting instructor standardisation where required. It never intervenes, and nobody has to learn how to use it. To see how it works on your programme, contact us.
How much training do our instructors need on the software?
One session with a colleague, in practice. There is a single procedure (open the session, grade, debrief) and the concordance monitoring, competency mapping and audit evidence are produced from that, underneath. If instructors need a course to use it, the tool is wrong.
Do instructors have to do anything extra for standardisation monitoring?
No. Inter-rater reliability is calculated from the grades they already enter. There is no separate form, no additional tick-box and no parallel exercise.
What is enhanced EBT, and how does our SMS data feed it?
Enhanced EBT tailors the programme to your own operation rather than the generic baseline. Findings from your safety management system (occurrence reports, FDM/FDA trends, LOSA and audit findings) are translated into the EBT scenario design method: the threats, errors and competencies each scenario must elicit. The EBT Scenario Builder turns that into instructor scripts from your aircraft catalogue, and the graded results show in the next cycle whether the risk moved. Your SMS stays the owner of safety management; AeroEBT uses its findings to design training.
What is the ORCA cycle?
Observe, record, classify, assess, debrief, report, calibrate: the seven steps an evidence-based training loop actually contains. AeroEBT is built around all seven, including the last two that most programmes leave open: reporting from live data, and calibrating instructors against the fleet baseline.
Does AeroEBT support mixed EBT as well as full EBT?
Yes. You can run a mixed programme today and move to full EBT on your own timeline, with the same app for instructors throughout.
Can we keep our own grading scale and competency framework?
Yes. AeroEBT is configured to your programme, framework and grading scale during the first weeks of implementation.
Does the instructor app work offline in the simulator?
Yes. The iPad app captures grades and notes offline and synchronises when the device reconnects.
How do you measure instructor concordance?
Inter-rater reliability is measured per instructor against the fleet baseline, and calibration sessions are planned and recorded in the same system.
Does the AI grade our pilots?
No. AeroBrain proposes observations from instructor notes and highlights trends; the instructor remains the assessor and confirms every entry.
Can it connect to our training management and rostering systems?
Yes. AeroEBT integrates with SkyDynamics TMS and offers API access on the Enterprise plan for other systems, including rostering.
Who owns the data, and can we export it?
You do. Training records can be exported, and an on-premises deployment is available.
How long does it take to set up an EBT programme in AeroEBT?
Less than 15 minutes for your EBT settings and the whole programme, instead of months, on an aircraft type with ready-made data: procedure lists, failure databases, event libraries and the A/B/C topic lists are already there. That is SkyDynamics' figure for the setup itself; importing records, training instructors and the parallel run follow in the first 90 days.
How long does implementation take?
A typical rollout takes about 90 days from programme mapping to go-live, including a parallel run.
Complexity behind. Simplicity ahead.
Talk to our training team. In a 30-minute demo we look at your current EBT or CBTA programme, where it is drifting and what the first 90 days with AeroEBT would look like.
We respond within one business day.
Up next