What testing would you perform to verify APU shutdown after a misbehavior?

What testing would you perform to verify APU shutdown after a misbehavior?

• A. Only perform a ground run-up to observe shutdown.
• B. Manual shutdown verification, review fault logs, and functional checks of start/stop controls; perform self-test if available.
• C. Replace the APU module.
• D. Check the aircraft's flight computer for climate data.

Answer: (B)

Verifying an APU shutdown after misbehavior requires confirming that the shutdown can be commanded, executed, and observed, with evidence of any fault conditions captured. The approach in need is to manually verify the shutdown so you can see that the APU stops when commanded, then review fault logs to understand what caused the misbehavior and to confirm the faults are being properly reported or cleared. Functional checks of the start and stop controls ensure the control inputs actually trigger the shutdown logic and that the system responds correctly in normal and degraded states. If a self-test is available, running it adds a diagnostic check of the APU’s internal health, helping to verify there isn’t an hidden fault that could reappear. Together, these steps provide a complete picture of the shutdown behavior, fault guidance for troubleshooting, and confidence in the control interfaces, which a simple ground run-up or a replacement would not provide. Checking climate data from the flight computer, on the other hand, is not addressing the APU shutdown behavior.

Verifying an APU shutdown after misbehavior requires confirming that the shutdown can be commanded, executed, and observed, with evidence of any fault conditions captured. The approach in need is to manually verify the shutdown so you can see that the APU stops when commanded, then review fault logs to understand what caused the misbehavior and to confirm the faults are being properly reported or cleared. Functional checks of the start and stop controls ensure the control inputs actually trigger the shutdown logic and that the system responds correctly in normal and degraded states. If a self-test is available, running it adds a diagnostic check of the APU’s internal health, helping to verify there isn’t an hidden fault that could reappear. Together, these steps provide a complete picture of the shutdown behavior, fault guidance for troubleshooting, and confidence in the control interfaces, which a simple ground run-up or a replacement would not provide. Checking climate data from the flight computer, on the other hand, is not addressing the APU shutdown behavior.