September 23, 200421 yr Pardon my second request at getting answers to some questions.....I have searched everywhere for the answer to my questions, and I hope some one will help me out. I posted yesterday but no luck-guess I am a bit anxious and hope the second time is the charm. I will simplify my questions too. 1. Regarding VNAV, for a published STAR with waypoint altitude and airspeed constraints, must I modify the LEGS page and manually place the constraints or does the FMC "know" the restrictions?2. OR do we enter the STAR, rwy, transition, path/speed descent type, and the FMC flies it after we lower the altitude in the MCP to appropriate alts?There, thats all I need to know. I seem to keep reading different approach techniques,and I am confused as to what to do procedurally. Cheers.......Joe Swier
September 23, 200421 yr Hi Joe,It's not a simple answer to your questions as there as many approach techniques as there are pilots, or at least airlines. ;-)1. What you do when you enter a terminal procedure such as a SID/DP or a STAR into the FMC is that you check it against your charts. If you find any discrepancies you alter the FMC legs to comply with the published charts. The FMC doesn't know anything more than the person who programmed the procedure. True here as in real life. Though I suspect the QA for the FMC databases are much more rigid in real life. ;-)2. You should use the MCP in conjunction with the FMC. Not either or. Operating the MCP will give you a procedural and situational awareness that is good in the terminal environment. On final approach you are rarely flying VNAV and LNAV. More likely V/S and HDG before ILS capture.Hope it helps, Mats JohanssonPMDG Flight Test Dept | Asus Z270-A | Intel i5-7600K @ 4.8 GHz OC/H2O | nVidia Geforce GTX 1070 8GB OC/O2|
September 24, 200421 yr >Pardon my second request at getting answers to some>questions.....I have searched everywhere for the answer to my>questions, and I hope some one will help me out. I posted>yesterday but no luck-guess I am a bit anxious and hope the>second time is the charm. I will simplify my questions too. >>1. Regarding VNAV, for a published STAR with waypoint altitude>and airspeed constraints, must I modify the LEGS page and>manually place the constraints or does the FMC "know" the>restrictions?>>2. OR do we enter the STAR, rwy, transition, path/speed>descent type, and the FMC flies it after we lower the altitude>in the MCP to appropriate alts?>>There, thats all I need to know. I seem to keep reading>different approach techniques,and I am confused as to what to>do procedurally. >>>Cheers.......Joe SwierJoe,1. Mats answer is very good, your published STAR chart rules first, not the FMC data base but usually the FMC data base will have all the speed and altitude constraints entered on the LEGs page. You should always verify they are correct and enter any missing data.2. ???? Personally I don't like to have too many "At or Above" constraints instead reentering them as an "At" constraints. I think VNAV PATH descents work better with the PMDG bird this way.Floyd John Floyd
September 24, 200421 yr Author Thank you both Mats and Floyd.......I understand exactly what you both have stated. I think I was confused because the other night I flew into KLGA with the MIP3 arrival which has MARCC at FL180, VIBES at 13K and BEUTY at 10K. When I cross checked the LEGS page prior to TOD, there were NO restricted altitudes at all and in fact the speed was cruise speed. I had to manually edit the LEGS page, but I didn't know what speed to put in for 18K. I put 280 in for it and 260 for 13k, 240 for 10K.It just sort of struck me funny that none of the STAR constraints were on the LEGS page.I think your advice to use alternate types of approach methods were good ones with STARs that have multiple constraints. Again thanks!Joe Swier
September 30, 200421 yr Hi Joe,"I didn't know what speed to put in for 18K. I put 280 in for it and 260 for 13k, 240 for 10K."Just a quick point - when entering constraints into the FMC, you need only enter the ones that actually apply. That is, if there is only an altitude constraint at a particular point on the route, you enter that and let the FMC worry about managing the speed that ensures you meet the constraint. If you enter BOTH altitude and speed constraints, you are telling the FMC that you want to be at the specified altitude AND at the specified speed.(Of course, some arrival charts do specify both crossing alt and speed).Hope this makes sense?BR,Frank
Create an account or sign in to comment