Maintenance Tasks are defined for each Aircraft Type separately. When you open the Maintenance Tasks table in Backend, you must first choose the Aircraft Type, then click on ‚Submit‘ to show the tasks for the Aircraft Type.
Click on ‚Add Record‘ (Hinzufügen) to create a new task or the ‚edit‘ button to show a task in edit mode. You can also create a new task by copying an existing record and editing it to your needs.
The settings for the task determine where the performed task is displayed in FlightLog and FlightAssistant and when performance is due.
Task Category
LCS: Tasks with category LCS require an LCS license (unless the Aircraft Type has ‚Pilot is LCS‘ activated). Expiry of LCS tasks is reported in FlightAssistant step 1 – Aircraft Status. Performing LCS tasks creates a Release to Service (RS).
Daily: No LCS license required, unless the setting in ‚RSreq‘ requests it. Daily tasks can be performed by every pilot allocated to the aircraft, unless the setting in ‚TaskRSReq‘ requires LCS or MX license. Daily tasks can be checked off in FlightAssistant step 3 – Before Flight. Performance of daily tasks is not limited to the pilot. For tasks of category Daily the PIC must select the pilot/technician performing the task from the list ‚Performed By‘ and certify performance with the pilots/technicians signature.
PreFlight: No LCS license required, unless the setting in ‚RSreq‘ requests it. PreFlight tasks can be performed by every pilot allocated to the aircraft unless the setting in ‚TaskRSReq‘ requires LCS or MX license. PreFlight tasks can be checked off in FlightAssistant step 3 – Before Flight. PreFlight checks are always performed by the pilot in command.
‚Performed by‘, ‚date‘ and ‚Approval‘ (license number) of performed Daily and PreFlight tasks are displayed in the FlightLog form (top left corner ‚DAILY INSPECTION / PRE-FLIGHT CHECK‘).
Periodic: No LCS license is required for periodic tasks, the setting in ‚Task RSreq‘ is ignored. The setting in ‚When to do‘ must be ‚during‘ or ‚after‘ flight. If the setting in ‚When to do‘ is ‚during‘ flight, the tasks and the deadline are displayed in FlightAssistant Step 4 – Flight.
Periodic tasks can be checked as done in FlightAssistant step 5 – After Flight.
Task Title
The task title is a short description of the task which is displayed for notices and expiry warnings.
Task Text:
The task text is a HTML construct consisting of one <ul> (unordered list) tag containing one or more <li> tags.
Each <li>-tag appears in FlightAssistant and RS as a separate checkbox with text. Clicking on one <li> element affects all checkboxes in the <ul> (Click one clicks all).
Task RSreq
Sets which type of RS is required for certifying performed tasks (No RS, LCS RS or MX RS). Only applies to Daily and PreFlight tasks with ‚When to do‘ set to ‚before‘.
Intervals
The intervals rule when the next task performance becomes due, calculating the deadline since last performance.
Days: Number of days
Flight Logs: Number of completed FlightLogs
FT (Flight Time): Flighttime in hours.
RTT (Rotor Turning Time): Block time in hours.
Full Stops: Completed legs (a leg can have more than one landings)
Landings: Number of landings
When to do:
Before: LCS Tasks / Tasks with RSReq: The task is shown in FlightAssistant step 1 – Aircraft Status. Tasks with No RSreq in FlightAssistant Step 3 – Before Flight
During: The task is shown in FlightAssistant step 4 – Flight and in FlightAssistant step 5 – After Flight. Use only for tasks with ‚No RS‘.
After: The task is shown in FlightAssistant step 5 – After Flight. Use only for tasks with ‚No RS‘.
