
AeroEBT for maintenance engineers
The engineer logbook, kept as evidence rather than as a memory.
Task experience, type training, practical assessments and authorisations in one digital logbook, recorded at the aircraft, owned by the engineer, and exportable by the organisation when an authority asks.
The problem
Experience is what an engineer is judged on, and it lives in a paper book
The book gets lost
Years of task experience in a notebook that travels with the engineer and cannot be reconstructed if it goes missing.
Entries are inconsistent
What counts as a recorded task varies by person, by station and by decade.
Authorisations take digging
Proving an engineer has the recent experience for a task means assembling evidence rather than reading it.
What it records
One record for everything an engineer accumulates
Task experience
Tasks performed, on which aircraft and system, with date, station and supervising signature.
Type and basic training
Part-147 basic modules and type courses, theoretical and practical, with assessment evidence attached.
Practical assessments
The task-level practical record, captured at the aircraft rather than reconstructed at the office.
Authorisations
Company authorisations held, their scope and their currency.
Continuation and human factors
Part-145 continuation training and human factors, with due dates tracked.
Licence and endorsements
Part-66 licence, ratings and endorsements held with expiry visibility.
For the engineer
It is their career record, so they keep a copy.
An engineer building experience toward a licence or an authorisation should not depend on one employer's filing cabinet. The logbook is theirs: they record at the aircraft, they see their own progress, and they leave with their record when they move on.
- Recorded on tablet at the aircraft, offline
- Progress toward experience requirements visible to the engineer
- Their own copy when they leave, like a pilot's logbook
- The organisation keeps its record for the period its approval requires
The iPad app
One native iPad app for the trainee and the training organisation
The practical logbook runs in the AeroEBT iPad app, offline at the aircraft or in the workshop. The trainee records and signs; the Part-147 organisation reviews, countersigns and closes the record in the same app. Logbook templates and training orders are set up in the web admin.
For trainees
Their practical logbook in their hands, with progress they can see.
- Progress toward the required tasks, by ATA chapter and by task type
- Task list by ATA chapter, filtered by status
- A task recorded in four steps: where, how, evidence, declaration
- Signed at the point of work, offline, synchronised afterwards
- Trainee
- Offline
For the MTO
Instructors and assessors work the same record from the review side.
- Review queue: accept or return with a stated reason, then countersign
- Exceptions to mandatory tasks approved with the reason on record
- Compliance report against the logbook requirements before assessment
- Assessment and reassessment records, a final lock and a PDF of the logbook
- Part-147
- Instructor
- Assessor
For the organisation
What a Part-145 or Part-147 organisation gets back
Authorisation decisions on evidence
Recent task experience visible when deciding scope, instead of a conversation about who has done what.
Audit answers in minutes
Who did the task, who assessed it, and what qualified them, from the record rather than from memory.
Gaps before they bite
Expiring continuation training and thin task experience surfaced before a shift is planned around them.
Consistency between assessors
The same concordance measurement used for flight instructors, applied to assessors in the hangar.
Connected to the tech log
Who is qualified for what, read alongside the defect and airworthiness picture in AeroTechLog.
Your data, exportable
Structured export whenever you need it, including for an authority.
Questions maintenance organisations ask
Does a digital logbook satisfy our authority?
What satisfies an authority is a complete, attributable and retrievable record. A digital record makes that easier to demonstrate, but the acceptance of the format is a conversation with your authority: we support it, we do not assert it for you.
Who owns the data?
The organisation owns its record; the engineer keeps their own copy. Both are explicit rather than assumed.
Does it work offline in the hangar?
Yes. Entries are captured offline at the aircraft and synchronise afterwards.
Is there a mobile app for trainees and the MTO?
Yes, a native iPad app. Trainees record and sign their tasks in it; the training organisation's instructors and assessors review, countersign and close the logbook in the same app. Templates, training orders and monitoring are in the web admin.
How does it relate to the technical log?
AeroTechLog records the aircraft: defects, deferrals and release to service. This records the person: experience, training and authorisation. Together they answer who was qualified to do what.
Can engineers record their own experience?
Yes, with supervision and countersignature where your procedures require it.
Get the experience record out of the notebook.
Thirty minutes on your organisation: what you record today, what an authorisation decision needs, and what changes when the logbook is digital.
We respond within one business day.
