Version 1.21.0

We're pleased to announce the latest updates to the Tech Log suite of products. A number of the following updates are upcoming and should be live by 20th February 2023, but we wanted to let you know what to expect ahead of time!

 
Global Enhancements

Intermittent Faults / Observations

Further features have been added to the Intermittent Faults / Observations module, which allows for the reporting of non-airworthiness events and observations regarding the aircraft's systems. Functionality that is being added to the next release will include:

• The ability to add additional occurrences to any existing Fault / Observation allowing for accurate repeat item tracking. Adding an occurrence will allow for further details of the Fault / Observation to be recorded and this action can be accessed through the three dot menu icon on both the iPad Application and Web Dashboard.
• Previously submitted Intermittent Faults will now be able to be edited, in order to add additional information or correct mistakes in both interfaces.
• In occasions where Intermittent Faults / Observations require further consideration, the type can be converted to a defect. Once this is completed, the issue will no longer appear on the Intermittent Faults / Observations list and will impact aircraft serviceability. These can be inspected and signed off as per normal defect resolution.
• When adding a new Intermittent Fault / Observation, the ability to search the recorded items will be available on the iPad application to prevent duplications on item creation.

If you would like to discuss adding this module to your account, please contact support.

Fuel Uplift Tracking

It is now possible to remove either just the fuel uplift and adjustment fields or all fuel uplift related fields which include the departure and arrival fields. Once enabled these values will be removed from sectors, uplift, and MX checks workflows. Please contact support if these fields should be removed for your organisation.

Engineer Signoff

For operators who require an engineer to complete defect signoffs, an additional optional field for the deferral approval reference can now be provided.

Web Dashboard Release

New Features

• Notes to Crew, previously an iPad Application only feature, is now available on the Web Dashboard allowing the ability to add, edit or delete notes linked to a specific aircraft. If you do not currently have this module turned on and would like to discuss adding this to your account, please contact support.
• Logbook data can now be generated for a maximum of a 12 month period. When selecting the 'Generate CSV' button, a modal will give options for the desired months which will then be emailed to you as standard.

Enhancements

• Totals have now been added to the Maintenance list, quickly highlighting the number of items within each status.
• The ability to select an aircraft before its details have fully loaded has now been added so you no longer need to wait for all aircraft details within the fleet overview to load before continuing.
• You can now choose to view the new MEL table in a different table style to match what is used within our MEL Manager product.

Bug Fixes

• An issue where the cycles widget on an aircraft overview would still show even though cycles were not being recorded has now been resolved.
• Some signatures created within the iPad Application were previously not displaying on the trip drawer. This has now been resolved.
• An issue that could cause defects to display on SRPs in the order they were added to the system, rather than the order defined by their reporting time, has been resolved. This fix will resolve the problem retroactively with no further actions required.

 
iPad Application Release

Enhancements

• Similar to the recent addition on other modals, an aircraft banner highlighting the aircraft registration and current serviceability status has been added to the Defect flow, highlighting the aircraft being impacted.
• For trips that require multiple crew, validation has now been added when logging crew duty times to ensure that at least one user's duty time ends after the trip has ended.