On this flight, the ETA to the TOD and the BGR are the same, even though the VOR is well down the line from the TOD.
Flight plan was KMDW GIJ J554 JHW Q29 KRAZZ BGR KBHB
Some of Aspen's approaches are more than 10,000 ft. and the G1000 doesn't go any higher than this. Also, when you select 10k for the mins, the 1 digit sits outside the BARO MIN display on the PFD.
Thanks.
I'm doing exactly that and it's still nearly impossible to control. I've almost gone off the runway on nearly every take off. What hardware are you using?
Is the Current VNV Profile box supposed to be filled in since I'm about to enter a STAR with constraints? Also, there's no TOD point showing up on nav display. Screenshot attached.
I tried flying the WLEEE 5 arrival into KAUS and none of the altitude constraints loaded. Is this accurate? I'm using AIRAC cycle 1811 from Navigraph.
Alex
Yes, per my original post, I clearly understand that concept - but there are circumstances where it would be nice to reset everything to a default state.
On the ground I can get 40 - 50 FPS with the 737 in the VC. But when I get up to higher altitudes (e.g., above 20,000 ft.) my FPS tanks to about 22 FPS. Anyone else seeing this? It seems to be isolated to IXEG's 737.