In short
- Each aircraft's airborne hours, from its own counter, read hourly.
- Hours to the next service, and when it's likely due at its recent rate.
- Cancellations by FlightLogger's reason, standbys and maintenance days.
The cards
- Next service: FlightLogger's own hours left (the next service on the airborne log, less the airborne counter), and when it'll reach them at its rate over the last 7 days, or FlightLogger's service date if that's sooner.
- By type and Month by month: hours flown by type, and each month.
- By base (with more than one base): each base's airborne hours by type, flying days, flights and cancellations, and the aircraft based there.
- Hour by hour: how many aircraft are in the air on average in each hour of the day at each base, from the flown bookings' planned flight times.
- Cancellations: by FlightLogger's reason.
- Standbys: standby meetings in your standby classrooms, and how many were activated (as your comments say, so treat it as at least this many).
- Each aircraft: everything by registration, sortable.
- Maintenance: maintenance bookings sorted by what their note says ("OOH" out of hours, "Check hours"), counted as maintenance days on each aircraft.
What's kept
Only aircraft-level facts: never a student, an instructor or a booking's comment. Hours are read with your school's own FlightLogger key, which only ever reads. Before the first hourly reading, hours are estimated from bookings, and the page says so.
The Fleet page is for owners, admins, managers, instructors and schedulers by default; change it per person in School Settings > People.
See a sample fleetAircraft, services, cancellations and maintenance.
Open the demo's Fleet