eTechLog is an electronic replacement for an aircraft paper based technical log/log book. Operating on a range of moblile devices, from Toughbooks to Toughpads and various tablets capturing aircraft flight and technical data including flight sector data, Line Defects, Out of Phase control and remote management by Maintrol, along with maintenance monitoring data. The data is transmitted wirelessly via a range of means to the Airlines Maintenance Operations Control Centres allowing Engineering and Flight Ops real time analysis and control.

Electronic Flight Bag (EFB)

OEM’s including Airbus, Boeing, Embraer & BAE are already supported. The applications available include:

  • Lido eRM,
  • Airbus Performance Tools
  • Boeing  EFRAS Performance Tools
  • Vistair Ops manual viewer.
  • Infotrust eManual EFB Solution

Also within the Conduce EFB is the Conduce eTechLog system providing seamless integration and real time connectivity between the cockpit and Airline Flight Ops/Engineering control.

EFB Asset Management


Conduce are uniquely qualified and experienced to provide an EFB Asset Management service. We can manage an Airlines fleet of Panasonic ToughBooks or ToughPads, efficiently ensuring all assets are tracked & kept in the latest configuration for the EFB or eTechLog tools that they support. Conduce are already an airline approved Repair Station for ToughBooks currently maintaining more that 100 devices with a turnkey fixed price exchange/repair program in place.  Most Airlines rely on their IT department to assist in this area, but inevitably the required specialist skill is not available in-house leading to an inefficient service.

Why not ask Conduce for a proposal to out source this entire requirement?

eTechlog Lifecycle


The cycle of an aircraft technical log or log book entry starts when a serviceable aircraft is released after construction or after heavy/base maintenance. In an ideal world the perfect aircraft will come on line with zero defects and zero Out Of Phase (OOP) –  maintenance requirements which  will need to be performed before the next scheduled base maintenance check! However in the real world aircraft come into service with open ADD’s (Acceptable Deferred Defects) and with open OOP’s that will need to be carried out whilst the aircraft is in the care of Line Maintenance. Above is the cycle of an aircraft tech log starting at the release from base maintenance through pre-flight release to the Pilot, then cycling through the flight incurring any additional defects before returning to Line Engineering for the cycle to begin again.  The cycle is further described below:

  1. Serviceable aircraft Released from Base after scheduled maintenance.
  2. Aircraft usually released with some Open ADD’s.
  3. Aircraft also released with some planned OOPs within flying hours, cycles and date limits that will become due prior to the next base maintenance check.
  4. Line Maintenance department perform pre-flight work, solving any defects possible, carrying out any OOP requirements, preparing the a/c for flight with fuel and oil checks/uplifts and signing to release the a/c to service
  5. Pilot accepts aircraft and electronic copy of Engineer/Pilot signoff is transmitted to Ops/Maintrol.
  6. Pilot completes next sector/flight number data, including any in-flight ECM or other required flight data recording
  7. Pilot creates entries for any new defects arising during flight or landing prior to handing a/c back to Line Maintenance Engineering.
  8. Whilst aircraft is on the ground during turn around, Line Maintenance rectify all defects possible, carry out any due OOP’s, raise any new defects found, rectify or make as ADD’s.  –  Make partial transmissions as required to update Maintrol.
  9. Maintrol communicate any new OOP or defect requirements to be carried out as required.
  10. Return to step 4.
The Conduce eTechLog/EFB solution enables all these actions to be accurately captured in real time – enabling swift on-time departures and seamless monitoring/control of an airline fleet.