Flight log

The Flightlog tab provides a complete, aircraft-centric record of every flight. Entries appear in reverse chronological order, with the most recent flight at the top.

For fleet aircraft that operate through the Aerolync Pilot app, the flight log is populated automatically when pilots complete the departure and arrival flow. You can also add entries manually for corrections or flights that were not logged through the app.

Opening the flight log

1. Open Fleet from the main navigation.
2. Click the aircraft you want to review.
3. Select the Flightlog tab.

How the Pilot App and Fleet work together

The Aerolync Pilot app and Fleet are not separate systems maintaining independent flight records. They work together on the same flight data:

1. At departure -- the pilot starts the flight in the app. Departure details (aerodrome, time, Hobbs start) are recorded.
2. At arrival -- the pilot completes the flight in the app. Arrival details (aerodrome, time, Hobbs end) are recorded along with billing information.
3. In Fleet -- the Flightlog tab shows the combined result. Each row represents one complete flight with all the data entered during both departure and arrival.

---

Flight log columns

Each row in the flight log contains the following fields:

Understanding the Bill-to column

The Bill-to column tells you the current billing state of each flight:

---

Hobbs input format

Hobbs values always follow the format configured on the aircraft's Configuration tab:

This format is consistent everywhere Hobbs appears, including in the Pilot App when pilots register departure and arrival.

---

Billing base

Each flight log entry records how the flight should be billed:

• Engine time -- billing is based on the time the engine was running.
• Flight time -- billing is based on the time from takeoff to landing.

The billing base can be set per flight log entry, which allows overriding the aircraft default when needed. In the normal app flow, the billing base follows the aircraft's rental configuration automatically.

The billing base connects directly to Finance for invoicing.

Adding a flight log entry manually

1. Open the aircraft in Fleet and go to the Flightlog tab.
2. Click Add Flightlog from the subnavigation.
3. Fill in the required fields:
   • Departure and arrival aerodromes
   • Pilot name and pilot function
   • Flight type
   • POB (persons on board)
   • Departure date and time
   • Arrival date and time
   • Hobbs start and Hobbs end
   • Billing base (engine time or flight time)
   • Bill-to relation
4. Optionally add remarks for operational context.
5. Save the entry.

Manual entries are useful for:

• Correcting data from flights that were logged incorrectly in the app
• Recording flights that were not processed through the app
• Adding historical flight records

---

Editing and deleting flight log entries

How to edit a flight log entry

1. Open the flight log entry you want to modify.
2. Update the fields as needed.
3. Save the changes.

How to delete a flight log entry

1. Open the flight log entry.
2. Use the delete action.
3. Confirm the deletion.

---

Connection to defects

Flight logging interacts with the defect system in several ways:

• Before departure -- when defect visibility is enabled for the aircraft, the Pilot App checks the aircraft airworthiness state. If unresolved defects have grounded the aircraft (AOG status), departure is blocked in the app.
• On arrival -- when defect reporting is enabled for the aircraft, pilots can report a defect from the app. The defect is linked to the flight context, so maintenance staff can review it alongside the flight details.

Use the Defects tab for technical issue handling rather than the flight log remarks field. Remarks are intended for short operational notes, not for tracking maintenance issues.

Troubleshooting incomplete flight logs

If a flight log entry looks incomplete or inconsistent, check the following in order:

1. Was departure registered? -- verify that the pilot started the flight in the Pilot App.
2. Was arrival completed? -- check whether the pilot finished the arrival flow in the app. An incomplete arrival is the most common reason for missing data.
3. Is the flight still active? -- look at the Bill-to column. If it shows "To be assigned. Flight is active." the flight has not been completed yet.
4. Is the Hobbs format correct? -- confirm that the aircraft's Hobbs meter type in Configuration matches how the data was entered.

Common tasks

Review recent flights for an aircraft Open the aircraft, go to the Flightlog tab, and scan the top of the list. The most recent flights appear first.

Find flights with billing issues Look for entries where the Bill-to column shows "To be assigned. Flight is active." or is empty. These flights need follow-up.

Verify Hobbs continuity Compare the Hobbs end of one flight with the Hobbs start of the next flight. They should be the same or very close. Gaps may indicate unrecorded flights or data entry errors.

Check a specific pilot's flights on this aircraft Scan the Pilot column or use the free-text search if available. For a pilot-centric view across all aircraft, use the Flights module instead.

---

Good practices

• Verify Hobbs start and Hobbs end values before saving any manual entry. Incorrect Hobbs readings affect maintenance threshold warnings and billing calculations.
• Confirm the Bill-to assignment on every flight, especially when flights are active or recently completed.
• Use the remarks field for short operational context only. Do not use it as a substitute for defect reporting.
• When correcting a flight log entry, check whether the correction also affects the Maintenance threshold or billing in Finance.
• Regularly review the flight log for active flights that may have been abandoned without completing the arrival flow.