January 26, 201313 yr Is completely messed up when selecting LNAV+VNAV... Does anyone else have this? The DP calls for a left turn heading 240 to intercept the 196 radial off EHF... the NGX wants to make a loop d doop right turn the long way around to the west. My navdata is about one cycle out of date now... | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
January 26, 201313 yr AIRAC navdata says that you have to climb to 1007' before turning 240*. But the aircraft cannot climb so rapidly to get to 1007 to turn 240 and intercept 196 to fix MARIC (or 196 from EHF). That's why it want to make a right 300* turn. I've checked the charts and there's no 1007 restriction http://155.178.201.1.../00036MARIC.PDF . So looks like nav data is not correct. Not sure how it would be flown in RW, but I would climb to 400AGL, manually turn to 240, intercept 139 and engage LNAV. If needed do a direct to MARIC. Rostyslav S Wanna fly 737NGX with turbulence?
January 26, 201313 yr I think RSVIT's suggestions are good. If you have a screenie of the LEGS page, it would help. Sometimes RW DPs don't work and you have to either monkey with the LEGS or just <gasp> not follow the magenta line for a bit. In this case, I would just have MARIC as the first fix with the 196 crs inbound. After the 240 turn and wings level, select LNAV. Matt Cee
January 26, 201313 yr Author Thanks.... I did just fly with heading... I don't mind flying without LNAV.. When the plane doesn't go where I want or expect I'm taking over hehe... | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
Create an account or sign in to comment