Flight log

The Flightlog tab shows the recorded aircraft logs for the selected aircraft in reverse chronological order.

For fleet aircraft, this is not a standalone list. It is closely linked to the Aerolync Pilot app and to the platform flight workflow.

What this page is for

Use Flightlog to review the aircraft-based history of a flight.

• It shows who flew, where the flight started and ended, and how the aircraft time was recorded.
• It gives Fleet staff the Hobbs, duration, and billing context for one aircraft.
• It is also the link between app-based flight logging and follow-up handling in Fleet, including defects.

How the app and platform work together

For reservation-based fleet flights, the Aerolync Pilot app and Fleet support the same flight from start to finish.

At departure in the app, the flight is started and the departure details are stored.

At arrival in the app, that same flight is completed with the arrival details, Hobbs values, and any follow-up billing information.

In Fleet, the Flightlog tab shows the combined result for the aircraft. That is why this page often reflects information that was originally entered in the app.

This means the app and the platform are not maintaining separate flight histories. They are showing different parts of the same flight information.

Movement list versus Flight log

These two views serve different purposes:

• the movement list in the app shows departures and arrivals in time order
• the Flightlog in Fleet shows the full aircraft-based log for one flight, including Hobbs, duration, billing context, and defect context

That distinction matters when you troubleshoot missing data.

• you may see that a departure or arrival was registered in the app
• the Fleet view may still look incomplete if the flight was not properly completed
• that usually means the flight is still active or the arrival flow was not finished correctly

What the list contains

Each row includes:

• date
• pilot name
• pilot function
• departure and arrival
• departure and arrival time
• flight time
• flight type
• POB
• Hobbs start and end
• duration
• bill-to information

Departure and arrival times in Fleet can come from the departure and arrival registrations made in the app.

How to read one row

When you open the flight log for an aircraft, read each row as one complete flight entry:

• Date, Departure, Arrival, and the time columns tell you when and where the flight took place.
• Pilot name, Pilot function, and POB tell you who was operating the flight.
• Hobbs start, Hobbs end, and Duration tell you how aircraft usage was recorded.
• Bill to tells you whether the financial side is already assigned or whether the flight is still active.

This makes the page useful for both operational review and back-office follow-up.

Adding a flight log

Use Add Flightlog from the Fleet subnavigation for manual or corrective entries. For normal reservation-based fleet flights, the log is usually created automatically from the app flow.

The form includes:

• departure and arrival
• pilot name and pilot function
• flight type
• POB
• departure date and time
• arrival date and time
• Hobbs start and Hobbs end
• billing base
• bill to
• remarks

Hobbs input

Hobbs input always follows the aircraft configuration:

• decimal notation when the aircraft uses Decimals
• H:MM notation when the aircraft uses Minutes

The same Hobbs configuration is also used in the app when pilots register departure and arrival.

Billing base

Each log can be billed based on:

• ENGINE TIME
• FLIGHT TIME

This makes it possible to override the default aircraft billing basis when needed.

In the app flow, arrival billing follows the aircraft billing setup, so Fleet and app interpretation should stay aligned.

Interpreting the Bill to column

The Bill to column reflects the current flight and billing status:

• a relation link means the flight has already been assigned to an internal relation
• To be assigned. Flight is active. means the flight is still in progress or not yet assigned for billing
• In/Outsourcing partner means the aircraft log belongs to another client context

This makes the column useful for spotting flights that are still in progress or still need back-office follow-up.

When editing or deleting is possible

Logs can only be edited or deleted once the flight is fully completed. If a flight is still in progress, those actions stay unavailable.

In practice, this protects flights that are still being completed through the app. If a flight is still active, Fleet should not allow the final log to be changed as if it were already finished.

Defects and dispatch impact

Flight logging also interacts with defects:

• before departure, the app checks the aircraft airworthiness state
• if unresolved defects make the aircraft AOG, departure is blocked in the app
• on arrival, a pilot can report a defect from the app when defect reporting is enabled for the aircraft
• that defect is linked back to the same flight context, so Fleet maintenance can review it in context

Use the Defects tab for technical issue handling rather than the flight log remarks field.

Practical troubleshooting

If the flight log looks incomplete or inconsistent, check the flow in this order:

• verify whether departure and arrival were both registered in the app
• check whether the flight is still active
• confirm that the arrival flow was fully completed
• verify whether the Bill to state is still showing an active flight

Good operational checks

• verify Hobbs start and end before saving
• confirm the Bill to assignment, especially on active flights
• remember that departure and arrival timing may come from what was registered in the app
• use remarks for short operational context, not for defect handling