July 19, 201114 yr Sometimes a STAR will indicate a between altitude. In the boeing FMC it would be entered: "RAINN 240/14000B12000A. Is this possible in the MD-11? Ruben Ruben Schuckit i5 2500k 4.5GHz GTX 560 Ti 8GB memory
July 19, 201114 yr According to the MD-11 FMS manual (very good read), altitude constraints are indicated with a plus (+) or a minus (-). For example, you are asked to cross WAYPT at or above 13000. You would insert SPEED/+13000. Same for at or below. (SPEED/-13000). Hope this helps. Kenny Lee"Keep climbing"
July 19, 201114 yr Author According to the MD-11 FMS manual (very good read), altitude constraints are indicated with a plus (+) or a minus (-). For example, you are asked to cross WAYPT at or above 13000. You would insert SPEED/+13000. Same for at or below. (SPEED/-13000). Hope this helps.Oh, I've read it. Trust me. But that's not what I asked, was it. I asked between altitudes. Look at the waypoint "RIVVR" http://aeronav.faa.gov/d-tpp/1108/00237RIIVR.PDF Ruben Schuckit i5 2500k 4.5GHz GTX 560 Ti 8GB memory
July 19, 201114 yr I completely misread your post. Wow. My bad. Not so sure if the MD-11 has a procedure for this. But with that specific approach you included what I would do would be program HABSO as +14000 and RIVVR at +12000. That's the best that I could come up with.Maybe someone else has a better suggestion... Kenny Lee"Keep climbing"
July 19, 201114 yr Author I completely misread your post. Wow. My bad. Not so sure if the MD-11 has a procedure for this. But with that specific approach you included what I would do would be program HABSO as +14000 and RIVVR at +12000. That's the best that I could come up with.Maybe someone else has a better suggestion...No problem! Thanks for all of your help. Ruben Schuckit i5 2500k 4.5GHz GTX 560 Ti 8GB memory
July 19, 201114 yr Normally when a STAR gives an in-between altitude, it is for a point within the route and not an entry or exit point. If you do not give an explicit height constraint for that point, then the FMC will calculate the expected altitude there depending on the previous and next waypoints. You can then adjust one of those to ensure you stay in the acceptable range if you think it necessary. Paul Smith.
February 10, 201313 yr The way I read this topic it that a waypoint hard below and hard above an altitude can't be set up in the FMC unless it is in the Navigraph cycle that way. The specific example I refer to is the RIIVR2 STAR into KLAX. In that STAR the is waypoint RIIVR which is shown on approach charts with a alitude below 14000 and above 120000. The waypoint preceding is HABSO with a hard above 14000. I can find nothing in the PMDG FMS Operating Manual that addresses this type of below and above entry. Michael Cubine Michael Cubine
February 10, 201313 yr Hi Michael, I guess you are right, but isn't it a bit late for the op? He asked the question July 2011. Best regards, John John Rubens
February 10, 201313 yr Hi Michael, I guess you are right, but isn't it a bit late for the op? He asked the question July 2011. Best regards, John John This is not really a reply to the OP but more a question if it can be done. I could have started a new topic but this one seemed most germaine after I did a search for "altitude constraints" in this forum and found about 5 threads. When I wrote the first post I was about an hour into a LFPG-KLAX flight. On the arrival the MD-11 crossed HABSO at 14240 and RIIVR at 12400. Michael Michael Cubine
February 10, 201313 yr Commercial Member Can't you enter both on the LAT REV page by clicking on the waypoint? My sim comp died, so I'm doing this all off of shady memory... Kyle Rodgers
February 10, 201313 yr Kyle I tried the VERT REV page and not the LAT REV. I will try the LAT REV on the next flight into KLAX with the MD-11. Michael Cubine Michael Cubine
February 10, 201313 yr I haven't flown the MD11 in a while, but as it's a pretty standard VNAV function, I'd be surprised if it couldn't do it.
February 21, 201313 yr no, unfortunately you can not enter both. well, you can, but if you put in an at or above and then an at or below the first will be erased. i think the only way to handle this in the MD-11 is to have one constraint and use the mcp altitude for the other limit. so for RIIVR you could have at or below 14000 as a crossing restriction and set 12000 in your mcp. then, after passing the fix, dial in whatever altitude is required for the descent then. i just recently returned the 11 into "service" after neglecting her since the release of the NGX and i have to admit that somehow i like her even better than the 737. she is just so.... BIG. i think i flew the same STAR when i noticed the missing constraint (i use navigraph) and after some research i remembered that that was a limitation on this FMC. and the way i know PMDG this is probably how it is on the real bird, too. Denis Kosbeck KPHX
February 21, 201313 yr I've always set the floor as a hard altitude on the FCP. In this example try setting the FMC to RAINN 240/-14000 with altitude set at 12100 on the FCP. Billy Bluestar I Earned My Spurs in Vietnam
Create an account or sign in to comment