Thanks. That’s very helpful. I presume that it may depend on the operator whether or not CAT I autolands are authorized.
Not only that. Some operators won’t allow autolands to be conducted even to CATIII capable runways unless Low Visibility Procedures have been declared in the airport (LVP Enforced) to suit Low Visibility operations. One of the reasons for this is that when LVPs are enforced, the airplanes taxing to and near a runway will be instructed to hold at holding positions farther away than the usual CAT I holding positions to prevent interference with the ILS.
In my previous airline we were allowed to conduct autolands (aka. dual channel approaches on the 737) to non CATII/III runways in VMC for training purposes or recency purposes. In my current airline we can only do them to approved CATII/III runways as long as the airport has approved and enforced LVPs. The exception to this rule is in case of emergency, for example pilot incapacitation (whenever the commander deems it the safest course of action).
I took the plunge two weeks back and have most parts covered. Are there any recommended settings for the yoke (I use TCA sidestick)? I duplicated existing profile that I use for Fenix A320 and feel it is a bit too sensitive.
If anyone is like me and don’t want to sit for a 12 hour flight and maybe want to save a flight to continue later or want to just warp to their destination. Then this is worth looking at.
Not had much chance to test it thoroughly but it looks promising..
I purchased the Advanced version about 6 months ago. Could be my favorite MSFS addon. Love all the updates, new scenarios, etc. And, has really helped me with my landings!
Yes I bought mine about three months ago to help practice landings (still ■■■■ at them but) and it seems to be evolving into so much more. Like you say lots of updates and scenarios.
Wish I’d discovered it sooner it seems to be one of MSFS’s best kept secrets.
The price did put me off at first, but it’s really worth it. Training all kind of approaches in all kind of conditions in almost every plane, over and over again! I cannot miss it anymore. Btw (until aug 31’) it’s 25% less expensive. Well spend money for me.
I’ve had FSIPanel on my back burner shopping list for a while. Pretty extensive list of planes it works on (below). Hmmmm… might have to snag it tonight.
I just need an American Airlines livery for it and I’ll fly it
Why you guys from PMDG don’t lauched any livery for LATAM on the MP yet? two or more weeks since the packs Vol 1 e 2 been launched and any operator from South america (LATAM) were contemplated yet. We here from south america deserves some attention too.
The operations center has one, if you’re on PC (doesn’t matter if your 777 is from the marketplace or direct from PMDG).
I was flying all the airlines and destinations out of Charlotte so that is awesome
I forgot to say.
I’m on XBOX. so I have to wait!
It doesn’t look like anyone has answered you.
No, it means there are no altitude restrictions (as per SIDs or clearances, etc.). In the U.S. you need a specific clearance to break the 250 knot below 10K ft restriction.
https://www.faa.gov/air_traffic/publications/atpubs/aim_html/chap5_section_2.html
See the Note in 5-2-9 section h. 8 (all the way at the bottom of the page)
When calculating V speeds for takeoff using performance calculator on EFB, they are inevitably different from the speeds that come up on CDU. There have been times when the difference is almost 10 Kts.
What is the recommendation in such case; use the CDU or perf calculator speed?
I’ve never had them be off by that much - that suggests something may not have been loaded into the CDU properly. Double check that you have the correct weights, TO flaps, and that you’ve set the N1 limit that the EFB produces. For me they’re almost always within 1-2kt of each other in most cases, except for V1 if the RWY is short. Double check your weights match up
That being said, typically you go with the EFB if there is a variance. A 10kt difference does suggest they’re both calculating off different things though.
I made it a habbit to click “calculate” twice. Often the first output is corrected then, at least for me.