(Importing a new version from external source) |
(Importing a new version from external source) |
||
| Line 2: | Line 2: | ||
: Block-on will be set when the aircraft stops. After 90 seconds with no movement, the flight will be stored in the logbook. This is to ensure that the block-on time will be registered in case you have to stop on the taxiway for example. | : Block-on will be set when the aircraft stops. After 90 seconds with no movement, the flight will be stored in the logbook. This is to ensure that the block-on time will be registered in case you have to stop on the taxiway for example. | ||
---- | ---- | ||
| − | === Landings === | + | ====Landings==== |
Multiple take-off landings will be added to the landings count. Our filters are designed to not record events in case the GPS signal is | Multiple take-off landings will be added to the landings count. Our filters are designed to not record events in case the GPS signal is | ||
poor or invalid. Therefore you should check that the GPS signal is good (yellow or green symbol) before using the automatic logbook. | poor or invalid. Therefore you should check that the GPS signal is good (yellow or green symbol) before using the automatic logbook. | ||
Latest revision as of 16:31, 7 October 2016
- Block-On
- Block-on will be set when the aircraft stops. After 90 seconds with no movement, the flight will be stored in the logbook. This is to ensure that the block-on time will be registered in case you have to stop on the taxiway for example.
Landings
Multiple take-off landings will be added to the landings count. Our filters are designed to not record events in case the GPS signal is poor or invalid. Therefore you should check that the GPS signal is good (yellow or green symbol) before using the automatic logbook.