Documents to prepare when onboarding a Mi-8 or Mi-171
Before onboarding into CAMOLOG, assemble a source list and agree the date at which the helicopter's records will be confirmed. The administrator prepares the package, the engineer checks values and supporting evidence, and management agrees how the participants will work together.
This checklist supports preparation of opening records. The exact package depends on the variant, installed configuration and aircraft history. The responsible engineer reviews the documents establishing applicability and actual completion.
Prepare information from the helicopter records, component records, utilisation logbook and maintenance documents. The checklist organises data preparation for a continuing airworthiness recordkeeping system while retaining a separate engineering review of the applicable bases.
Start with the date and responsibilities
Choose the opening snapshot date. In CAMOLOG, it represents the end of that day; subsequent daily entries start the next day. Counters, component details and maintenance history need to be reconciled to that boundary.
Appoint someone to assemble the files and handle questions. Separately identify the engineer who will confirm the data. Where documents pass through several people, retain their provenance and a contact for requesting a legible copy.
Begin with an inventory. It shows what is available, what needs clarification and which package can be submitted. File count alone says little about readiness: several scans may cover the same page while a necessary record is still absent.
A working document inventory
| Information group | Prepare | Review |
|---|---|---|
| Aircraft identity | Type, variant, registration and serial number | Consistency between sources |
| Initial counters | Values at the snapshot date and supporting entries | Units, starting points and included period |
| Configuration | Installed-component list | Designations, serial numbers and status at the selected date |
| Component history | Component records, installation and overhaul evidence | Connection to the individual item |
| Limitations | Life-limit and interval sources, additional tasks | Applicability, counter and document revision |
| Latest maintenance | Completion records for existing checks | Date, accumulated values and evidence |
| Directives and bulletins | Status information and completion documents | Distinction between applicability and execution |
| Access and roles | Participants and required actions | Preparation, review and viewing responsibilities |
Add an owner for clarification and a specific open question. “Check the archive” is broad; “obtain a legible page showing the component serial number” gives a usable next step.
Prepare the configuration spreadsheet
Identify the worksheet and rows representing installed components. The preliminary import accepts XLSX or XLSM; save an older XLS file as XLSX. Hidden worksheets, rows and columns are excluded from the preview.
Formulas are neither calculated nor imported as values. Where source information is calculated, prepare a reviewed values-only copy and preserve the original. Clarify the meaning of each column, especially accumulated time and remaining values.
Serialised tracking requires individual items to be distinguishable. Repeated descriptions can be valid. An unreadable serial number requires clarification; a likely match should not be recorded as an established fact.
Check scan quality
Include the column headings and document identification needed to interpret the entry. A cropped digit or information on an adjacent page can change its meaning. Check the order and completeness of related pages.
Keep the original file separately from an annotated working copy. Use de-identified or purpose-made data for demonstrations. Before transferring a real archive, agree the content and transfer channel: signed records may contain personal information.
The onboarding wizard supports file upload, manual entry and preliminary spreadsheet import. Automatic extraction of every field from arbitrary scans is outside the first version's scope. Preparing usable evidence remains part of onboarding.
Identify contradictions before upload
In a training example, the component record contains a legible serial number that differs from the summary spreadsheet. Identify both sources in the inventory and ask which item is actually installed. This keeps the question visible during migration.
Different “last completion” dates require interpretation too. They may refer to execution, document preparation or spreadsheet entry. Selecting the later date alone does not resolve the issue.
Unknown values remain subject to clarification. Zero is appropriate when it is supported. This prevents documentary gaps from entering calculations as apparently reliable opening values.
Turning the package into an opening snapshot
The administrator creates a draft, enters the opening information and attaches files. Submission fixes the version. Each counter, component, limitation, maintenance completion and file receives a separate engineering decision.
A package requiring correction returns to editing. A new version undergoes a new review; previous decisions remain in the history. After every item is confirmed, the administrator enters the snapshot into the operational records. Daily entries then follow the agreed boundary.
Directive history is handled in the appropriate section of the created aircraft, with supporting documents. A bulletin's presence among the files does not automatically establish applicability or completion.
Preparing for the first discussion
Initially, describe the fleet, current file formats and principal gaps. The inventory helps determine the next step and whether spreadsheets need preparation. Onboarding time is assessed after the package is understood; no single duration fits every archive.
A CAMOLOG demonstration can walk through a sample draft, one review decision and entry of a confirmed snapshot. It helps allocate responsibilities before work begins on real records.
Alexander Filimonov
This article describes a records workflow. Applicability, maintenance limits and airworthiness decisions require engineering review against the applicable documentation.
See the workflow in action
Discuss your source package and see how CAMOLOG organises the work.
Request a demo