580
edits
Aircraft testing checklist: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
* check brakes response and parking brake | * check brakes response and parking brake | ||
* check avionics power: do displays turn on/off, does audio turn on/off based on the power/volume switches. | |||
* tune COM1 and ensure ATIS is audible | * tune COM1 and ensure ATIS is audible | ||
** check volume adjustment if there's a control for it | ** check volume adjustment if there's a control for it | ||
* check altimeter setting | * check altimeter setting (can you set it, can you select inHG vs HPA if the acft supports it) | ||
* tune NAV1 and check behavior | * tune NAV1 and check behavior, including from/to flag | ||
(might need to be done in air) | (might need to be done in air for reception) | ||
* check ground steering (especially if ground tiller mode is supported) | * check ground steering (especially if ground tiller mode is supported) | ||
| Line 33: | Line 34: | ||
* fly a circuit | * fly a circuit | ||
* check takeoff power handling (P-factor on takeoff roll, the sensitivity of rudder inputs, etc) | * check takeoff power handling (P-factor on takeoff roll, the sensitivity of rudder inputs, etc). | ||
* Check the rotation speed is plausible, if you can find some data on it. | |||
* check flaps/gear work as expected | * check flaps/gear work as expected | ||
* check radar altimeter if fitted (the HUD is good to cross-check this) | * check radar altimeter if fitted (the HUD is good to cross-check this) | ||
* check stall performance in clean config (is it vaguely plausible | * check stall performance in clean config (is it vaguely plausible, especially) | ||
* check level flight over-speed performance (time to hit the barber pole) | * check level flight over-speed performance (time to hit the barber pole at full power). | ||
* fly | * fly a visual approach | ||
* check stall performance in approach config (is it vaguely plausible?..) | * check stall performance in approach config (is it vaguely plausible?..) | ||
* check ILS reception / deviation | * check ILS reception / deviation | ||
| Line 57: | Line 58: | ||
* animations work as expected (when implemented) : especially basic ones (control surfaces move is most important). | * animations work as expected (when implemented) : especially basic ones (control surfaces move is most important). | ||
* check all the views work, especially custom views, do they track okay using the joystick had and/or mouse look? | * check all the views work, especially custom views, do they track okay using the joystick had and/or mouse look? | ||
* default livery, is it something or 'unpainted grey'? | |||
= Non-standard stuff = | = Non-standard stuff = | ||
This is nice-to-haves, not mandatory | |||
* Check appearance under a compositor build | * Check appearance under a compositor build | ||
| Line 67: | Line 71: | ||
= Autopilot checks = | = Autopilot checks = | ||
* 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 | * 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. | ||
* 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. | ||