580
edits
Line 104: | Line 104: | ||
* If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is /no/ requirement for the generic autopilot dialog to work successfully, but would be nice to note if it does or doesn't. | * If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is /no/ requirement for the generic autopilot dialog to work successfully, but would be nice to note if it does or doesn't. | ||
** If the aircraft has a custom AP, but the generic dialog is enabled, but non-functional, note this. (The generic dialog should be disabled in this case) | |||
* Intercept a VOR / leg : check the turning to intercept, and overshoot / roll out when reading the correct position | * Intercept a VOR / leg : check the turning to intercept, and overshoot / roll out when reading the correct position | ||
* check the AP is stable at 2x time acceleration, and see if it is at 4x or 8x (lots aren't....) | * check the AP is stable at 2x time acceleration, and see if it is at 4x or 8x (lots aren't....) | ||
* Setup a basic route in the route-manager, and check interaction with the AP if supported: especially following waypoints and sequencing above them. This is more important for glass cockpits. | * Setup a basic route in the route-manager, and check interaction with the AP if supported: especially following waypoints and sequencing above them. This is more important for glass cockpits. |
edits