Under Frontier policy, when should the autoland setup be performed?

Under Frontier policy, when should the autoland setup be performed?

• A. Reported RVR/Vis At Or Below 1/2 Mile Or 2400 RVR And All Requirements For An Autoland Can Be Met
• B. When ATC Instructs An Autoland
• C. On CAT II Approaches Only
• D. Autoland Is Never Used

Answer: (A)

Autoland readiness is about setting up the system as soon as the flight is entering low-visibility conditions and the aircraft can meet the autoland requirements. The policy calls for performing the autoland setup when the reported RVR or visibility is at or below half a mile (or 2400 RVR) and all necessary conditions for an autoland are satisfied. Having the system configured in advance gives the crew time to verify altitude, approach mode, runway alignment, and braking/flare preparations, so if the approach proceeds to a CAT II/III landing, the autoland can engage smoothly without scrambling to configure it. Relying on ATC instruction alone isn’t the trigger for setup, since conditions can change quickly and early readiness avoids delays. Autoland isn’t limited to CAT II approaches only; it applies to appropriate CAT II/III scenarios, and it isn’t never used when the minima are met.

Autoland readiness is about setting up the system as soon as the flight is entering low-visibility conditions and the aircraft can meet the autoland requirements. The policy calls for performing the autoland setup when the reported RVR or visibility is at or below half a mile (or 2400 RVR) and all necessary conditions for an autoland are satisfied. Having the system configured in advance gives the crew time to verify altitude, approach mode, runway alignment, and braking/flare preparations, so if the approach proceeds to a CAT II/III landing, the autoland can engage smoothly without scrambling to configure it.

Relying on ATC instruction alone isn’t the trigger for setup, since conditions can change quickly and early readiness avoids delays. Autoland isn’t limited to CAT II approaches only; it applies to appropriate CAT II/III scenarios, and it isn’t never used when the minima are met.