Mi-8 utilisation and component life tracking in CAMOLOG
An aircraft record may show total flight time, installed components, overhaul dates and upcoming work. To use that information for planning, an engineer needs to establish where each value came from, its effective date, the item it describes and the document supporting it. CAMOLOG brings utilisation, components, limitations and documents together within the record of a specific aircraft.
When selecting Mi-8 utilisation software, define the required scope: life-limit and calendar-limit tracking, serialised components, aircraft and component records, and maintenance planning. Continuing airworthiness work connects these records. Software should help the team review those connections.
The system supports work with the Mi-8/Mi-171 helicopter family. It helps maintain records and prepare upcoming work. The engineer remains responsible for reviewing document applicability and the adequacy of the evidence. Remaining-life calculations depend on the completeness of the starting data.
Establish the effective date first
Consider a training example. A component spreadsheet was exported at month-end, several logbook pages cover the following month, and overhaul information arrived separately. Each document may be correct, but their dates must be reconciled before they form a single opening balance.
CAMOLOG onboarding uses an opening snapshot: a reviewed set of aircraft details, initial counters, components, limitations and the latest completions of existing maintenance checks. The snapshot represents the end of the selected day. Daily entries begin on the following day, separating information already included in the opening values from subsequent activity.
An unknown counter value must not be replaced with zero. Zero asserts a specific fact; a blank field may indicate that the evidence is missing. In the onboarding wizard, missing mandatory values prevent the snapshot from being entered into the operational records.
Each counter has its own meaning
Flight time, ground running, landings, cycles and APU counters describe different activity. Their units and starting points matter. A component's time since overhaul cannot simply be derived from the helicopter's total flight time: the component has its own installation and operating history.
Time formats need particular care. 2:30 means two hours and thirty minutes. The decimal value 2.30 means something different. If the spreadsheet and logbook use different formats, agree the conversion before importing the data.
For ground running, establish whether the source contains the original duration or an already adjusted recorded value. Applying a factor twice changes the result. The calculation basis must follow the applicable document; one rule should not be assumed to cover every counter or component.
Connect the component, limitation and evidence
Components with the same description may have different serial numbers, overhaul dates and accumulated values. Matching names alone are insufficient to merge records. Check the designation, individual serial number, installation details and documents.
A component may have several limitations. An hourly limit and a calendar limit need different starting information. The engineer reviews the counter, interval, starting point and supporting basis. Where sources disagree, record a specific question identifying the disputed value and the evidence needed to resolve it.
For a CAMOLOG demonstration, we suggest following that connection all the way through: open a component, inspect a limitation and locate the supporting document. This shows how a calculation can be checked in daily work. A status colour does not replace that review.
Review each new entry
Daily utilisation can be entered manually or prepared from a photograph of a logbook page. After recognition, the engineer compares the proposed rows with the image, checking dates, time, landings and other relevant counters. Errors are corrected before confirmation.
Compare the accumulated total with the last confirmed record as well. A discrepancy may arise from a missing page, duplicate entry, incorrect date or misunderstood column. Do not add assumed time to make the totals match. An error already entered requires a correction supported by evidence.
Image quality remains important. A cropped heading, glare or unclear digit may require a new photograph or clarification from the original. This is particularly relevant when the sequence of historical pages still needs to be established.
Use reviewed records for maintenance planning
The engineer can then examine upcoming work, checking the remaining value, previous completion and applicability to the aircraft or component. A work order can be prepared and the result linked to completion evidence.
A removal, installation of another component and correction of an incorrectly entered serial number represent different events. Overwriting an old number without establishing what happened can attach accumulated values and documents to the wrong item.
A useful first demonstration follows one complete example: opening value, source document, daily entry, limitation and upcoming work. A prepared training aircraft is sufficient; live customer records are unnecessary for an initial introduction.
Prepare the onboarding discussion
Describe the helicopter variants, current records and file formats. Identify who will assemble the evidence and who will review it. Any historical gaps should be discussed before estimating the onboarding time.
CAMOLOG can be demonstrated against your workflow: how entries arrive, where evidence is kept and how the engineer checks the remaining values. The scope and timing of onboarding depend on document quality and readiness.
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