Record a flight that was not booked
Record a flight that was flown without a booking, so it goes on the aircraft’s record and is charged to the member who flew it. If you flew it and it started no more than 4 hours ago, you can add the booking yourself, for example when you turned up, flew and forgot to book. A member can reach back 4 hours, and the server holds to that as well as the app; an admin records anything older.
Before you start
Section titled “Before you start”- You must be the member who flew it, for a flight that started no more than 4 hours ago, or an admin of the syndicate. For an older flight, the member asks an admin to record it: if a member tries to book it, the dialog says “Ask an admin to record a flight that started more than 4 hours ago, or correct the start if you mistyped it.”
- Have the flight’s details to hand: who flew, when, and the readings and times your syndicate records.
- The syndicate must not be closed or in read-only mode.
- If the flight falls inside a booking that already exists, you don’t need a new one: log the flight on that booking instead.
- Go to the Calendar tab and open the booking dialog over the time the flight was flown: in Month view, long-press the day; in Week or Day view, drag across the hours.
- Set Start Time and End Time to when the aircraft was out.
- Leave Pencil in (tentative) unticked. A tentative hold cannot be made in the past, and neither can a maintenance booking.
- Admins only: open Book on behalf of and choose the member who flew. Leave it on Myself if you flew it. A member doesn’t see this picker; the booking is theirs.
- Check the note above the buttons: “This booking is in the past, to record a flight already flown. When you create it, you’ll log its flight.” Tap Create.
- Log Flight opens for the new booking. Pilot in Command, Pre-flight By and Used by start with the member who flew it: you, or the member you booked for. Fill in the flight as usual (see Log a flight) and tap Log Usage.
The flight is now logged on the booking. As with any flight, nothing is charged yet. If the booking is your own and your syndicate lets members close their own bookings, you are offered the close, as after any flight. An admin who booked for a member gets no close sheet, because the booking is not theirs to close. Otherwise it is finalised like any other booking: an admin can finalise it from its Finalise Booking section, the member can close it later, or auto-finalisation picks it up if your syndicate has it on.
Good to know
Section titled “Good to know”- Today’s airworthiness doesn’t stop you. For a window wholly in the past, the dialog does not check whether the aircraft is grounded now, because that says nothing about a flight that is already over.
- Approval doesn’t apply once the flight is over. A booking whose end has passed is confirmed straight away, even when the syndicate requires approval, because there is nothing left to approve. When a member adds one there, every admin gets a Booking added late notification so it doesn’t pass unnoticed.
- A flight still going is just a booking. If the booking started a little while ago and ends later, Create doesn’t open Log Flight. Log the flight from the booking when you land. Where the syndicate requires approval, a member’s booking like this is a request until an admin approves it, like any other.
- Offline is fine. If you add the booking with no signal, the 4 hours count from when you added it, not from when your phone reconnects, so it still goes through when you get signal later. A booking that waits over a day to upload may be refused.
- Leaving Log Flight keeps the booking. If you leave before saving, the booking stays on the calendar. Open it and tap Log Usage: an admin sees it on a member’s booking once the booking has ended.
If it goes wrong
Section titled “If it goes wrong”- “Ask an admin to record a flight that started more than 4 hours ago, or correct the start if you mistyped it.” You are a member and the flight started too long ago for you to book it. Ask an admin to record it, or fix Start Time if you set it wrong.
- “Booking Could Not Be Saved”: “This flight couldn’t be saved. Ask an admin to record it.” A booking you added offline reached the server more than a day later, or was added more than 4 hours after the flight started. It comes off your calendar, but nothing you recorded is lost: the booking and any flight you logged against it are kept on your device. A card on the Home tab says the same thing; tap it to see the aircraft, the booked times, and for each flight the meter readings, times, who flew, notes and defect declaration. Show these to an admin, or tap Copy details and send them, so the admin can record the flight. Once it is recorded, tap Remove from this device. The details are only on this device, so they are lost if the app’s data is cleared or someone else signs in on it first.
- “That time has already passed. Choose a start time from now onwards.” The dialog is set to a tentative hold or a maintenance booking. Only a normal personal booking can start in the past.
- Log Flight didn’t open after Create. The booking was saved, but the app couldn’t load the aircraft’s settings in time. Open the booking and tap Log Usage.
- “Already logged?” appears when you save. The booking already holds a flight whose times overlap this one, or one with the same start and end readings. See If the flight is already logged.