I was using the NGX and used the SUNST2 approach into RW25R at KLAS. I verified using the Star charts that all altitudes and speeds were correct and they matched the FMC. However something seemed strange. The route brought me very low around the mountains surround Hoover Dam. I crossed Lake Mead at 6000FT. Is this because KLAS elevation is around 2200FT? or are the mountains in FSX placed in the wrong spots. It just doesnt seem right that I flew so close to the ground. In fact most of the final approach was below PAPI (all four were red) What is going wrong here?

Altimeter correct?

I've flown that route too many times to count, and I haven't noticed anything too bizarre. In real life though, the STAR already sets you up for a left downwind for 25L, and the controllers normally give you a visual for that runway. Because of this, you rarely have to fly the entire STAR, and if you do, it's because there is a heck of a lot of traffic.

ya I had to reset it several times during the approach. and above FL180 I had in put into STD mode. Which I assume sets it to the default 29.92

anyone have an idea to work around these situations? I know they will happen with other approaches Im sure What should I do when this comes up?

It looks like you were too low. The STAR never indicates an altitude lower than 8000 until the APP FACF. Following the STAR to final for the ILS 25L has an 8000 crossing alt at PRINO. Verify your charts to make sure your data is correct. Just my 2cents, maybe I'm not reading the charts right.

I was using the NGX and used the SUNST2 approach into RW25R at KLAS. I verified using the Star charts that all altitudes and speeds were correct and they matched the FMC. However something seemed strange. The route brought me very low around the mountains surround Hoover Dam. I crossed Lake Mead at 6000FT. Is this because KLAS elevation is around 2200FT? or are the mountains in FSX placed in the wrong spots. It just doesnt seem right that I flew so close to the ground. In fact most of the final approach was below PAPI (all four were red) What is going wrong here?

You're too low per the STAR and the ILS 25L approach charts. You need to examine both charts to determine your overall vertical profile. The last published altitude constraint on the STAR is 8000 feet at SUNST, so the aircraft should remain at 8000 feet after SUNST until reaching PRINO, the IAF for the ILS25L. There are additional hard speed constraints after SUNST: 210 KIAS at KIMME, and 170 KIAS at CHIPZ. The glideslope interception should occur at PRINO at 8000 feet. You wouldn't descend below 6000 feet on the approach until reaching LARRE, at which point you're already well past Lake Mead.

Ooo! I know this one! You're talking about the point where you fly over waypoints CHIPZ and POKRR for what looks like a downwind-crosswind leg of a standard pattern. The only real requirement on this arrival is that you hit SUNST @ 8000 feet, the following waypoints (KIMME, CHIPZ, POKRR, PRINO) have speed restrictions (from 210 to 170 knots) only. It looks like you just fly @ 8000 (or below) until you hit PRINO in which case you get radar vectors to your final approach course for 25L/25R. Or so says my (up to date) NACO chart. Edit: Beaten by Barret. Blast

I see. while I'll re fly this one. And if I let default ATC vector me in. I will end up even lower than planned. ATC from FSX is retarded

I've flown this route into LAS many many times and the altitude restraints are spot on for me as well safe altitudes. Approaching Hover Dam and over Lake Mead I'm @ or above FL080. No clue why you had this happen, wish I could help more then providing my personal experience.

I've flown this route into LAS many many times and the altitude restraints are spot on for me as well safe altitudes. Approaching Hover Dam and over Lake Mead I'm @ or above FL080. No clue why you had this happen, wish I could help more then providing my personal experience.

The problem is that the STAR that is in the system has the plane descend all the way through 8,000 down to the runway in a constant descent. In reality you're either vectored before hitting Lake Mead or if you're not, you won't be cruising over the Dam at 6000 feet. (I fly over the Dam at least once every 4 months and I'm flying higher than that in my 172SP!) NACO/Jep charts supplement the PMDG 737. I wouldn't fly without'em, even in the sim.

...NACO/Jep charts supplement the PMDG 737. I wouldn't fly without'em, even in the sim.

I totally agree. You'd have to be crazy to fly around without having all the charts for the departure and arrival airports. A lot of the time the navdata from navigraph is flawed and doesnt correspond to the charts, especially stuff like altitude and speed constraints

The problem is that the STAR that is in the system has the plane descend all the way through 8,000 down to the runway in a constant descent. In reality you're either vectored before hitting Lake Mead or if you're not, you won't be cruising over the Dam at 6000 feet. (I fly over the Dam at least once every 4 months and I'm flying higher than that in my 172SP!) NACO/Jep charts supplement the PMDG 737. I wouldn't fly without'em, even in the sim.

Well I've never have a constant descent on this STAR and don't get to FL060 until on approach also maybe you mis-read my post or for some reason replied to my post and not the original posters but I use charts from Navigraph or AIRNAV.com witch should be fine so no different then the NACO/Jep charts IMO (say what you like). Plus the original poster even said he cross checked the charts against FMS altitude restraints so I doubt charts are in question. Not sure why your referring this info to me as I'm not the one descending past my restraints?

I get my charts from flightaware. Can I stop the plane from doing a constant descent all the way down so this doesnt happen?

I totally agree. You'd have to be crazy to fly around without having all the charts for the departure and arrival airports. A lot of the time the navdata from navigraph is flawed and doesnt correspond to the charts, especially stuff like altitude and speed constraints

I wish more people would read before they post not to be rude to you, but the original poster said he checked the charts so not sure why the criticism about using or witch charts are used when people here are using them. No one here said they were not using charts, as your post of "You'd have to be crazy to fly without" sounds like you think someone here is programming routes blindly. I mean it's common since past the simple fact the OP said that he cross checked but the real common since part is, how else would he know he was below a altitude restraints if he never had the info provide too know what that altitude restraints was! Unless he was kicking up dust or ######in' Betty barking! Weather NAVAID.com or Navigraph.com I've yet to see contradictions between the two. If we want to make a best charts (I'm a ###### of this) post; my all means, but that is outside the OP question as his mentioned altitude restraints of 8000 is correct.

Edited September 2, 201114 yr by VLJ510