July 1, 20169 yr Hi, On the (final) approach the FO is calling 'Missed Approach altitude not set.' He does this before the GS is actually captured and therefor he always will make the call. As far as I know, the MA altitude should be set at the moment the GS is captured (i.e. not when GS becomes alive).Before capturing the GS, the aircraft may still be in vertical speed descent so fiddling with the MCP altitude is not a wise idea. Also sometimes the GS is captured from above (happens a lot at EHAM) Please advice Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024 System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro
July 1, 20169 yr Commercial Member The FO will make that call at the FAF or Outer Marker. That's the way do it at the airline we modeled. Treat the call for what it is: namely, an advisory. Just because he says it's not set, it doesn't mean it has to be set right then and there. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
July 1, 20169 yr Author Oki, understood. Thanks Location: Vleuten, The Netherlands, 17.3dme SPL 108.40 | Simulator: FS2024 System: AMD 7800X3D - Gigabyte X670 - RTX 4090 - 64GB DDR5 - 2 x 2TB SSD - 32" 1440p Display - Windows 11 Pro
Create an account or sign in to comment