![](https://www.avsim.com/uploads/set_resources_1/84c1e40ea0e759e3f1505eb1788ddf3c_flag_banner.png)
Search the Community
Showing results for tags 'STAR'.
Found 5 results
-
Are there any updates that can be downloaded for departures and arrivals? ENAT requests UDSA2Q but Fenix a320 only has UDSA1Q arrival. It's like it's not updated and running an old system. Any ide?
-
I have been flying with P2A for two weeks or so. The version I have is Pilot2ATC_Update_2700_x64_Beta7L. I've found that the program assigns altitudes to the different legs on the plan and that's fine. The cruise altitude is accepted but altitudes are added after the TOD. This is also fine but as the flight plan gets closer to the approach segment it gives me some doubtful altitudes. On one of my flights ATC had me descend to 3000 ft when I was 119 nm from the IAF. Certainly that is too low for a B738. The altitudes in the flight plan were good but ATC decided to send me low. The STARs sometimes have dual altitudes, a minimum ATC assigned altitude for turbine powered and a MEA that is could be used by aircraft not landing at the main airport in the STAR. If we look at the Bradford 8 STAR for KORD we see that the distance from IKK VOR to the BDF VOR is 150 nm. There is a FL180 for the entire route which is assigned by ATC but there's an MEA of 3000 and 2300, both also assigned by ATC if relevant. Certainly you don't want to fly an airliner at 3000 feet for 150 nm, but that's what appears that P2A is doing. I was flying another STAR when ATC told me to descend to 3000 but I used this one to illustrate. How does P2A decide the altitude assignment? If I see an altitude that is too low or at the MEA during planning, is there a way to change it? Thanks in advance.
-
Hi Guys, I recently purchased the PMDG 737NGX and I have completed a few flights in it. However, on every flight, I've not been able to land the plane like I should be able to. I've been following LNAV and VNAV throughout the entire flight. My SID and STAR was entered correctly and everything appeared to be running smoothly. I was still on VNAV and LNAV when I was moments away from turning onto final. I had NAV 1 and NAV 2 armed. I engaged VOR LOC just before I turned onto final. The plane began to turn and then successfully lined up with the runway. After it had lined up I engaged APP expecting it to capture the G/S; somehow, I missed the G/S and had to descend manually. Now, I think the reason it is doing this is because I was going to fast. At the point of capturing the G/S I am normally traveling at a steady pace of 150KIAS; this time it was 220KIAS. I had speed brakes fully extended yet it made little difference. So I think the VNAV speeds are too fast and I can't slow down in time for my landing. I've been told that I should allow VNAV to bring the plane down during the initial decent but then descend at my own choice of vertical speed and my own speed input. If this is correct, how shall I slow down during my STAR. I know it's a strange issue but I'm only 14 so I don't have the broadest of knowledge for this complex aircraft. I need recommendations quite urgently if possible. Thank you.
-
Hi there i got some problems with my fbw a320nx . For example today i tried to fly from epwa (Warsaw) to eddb (Berlin) , i done everything as always and when time came for approach to set in fplan i could not enter any STAR there was no stars to choose only. I had this problems on every german Airport i tried and on some of not german ones too.
-
Hi my name is Alex Makoviecki. I recently got the PMDG 737NGX and I really... really love it! The only problem I have with it is descending. I am about thirty miles back from the TOD (top of descent) and I set in the altitudes in the FMC that I should be at for each waypoint and VOR for the OMN.HILEY2 STAR at Miami Intl. I was using a chart that shows you the altitudes for each waypoint and VOR. I then set the altitude for descent to 5000ft which was the altitude for one of the waypoints that I would descend to and stay at for a while until descending to the glideslope intercept altitude. When I reached the top of descent the engines went to idle and the aircraft started descending but then leveled out at 37000ft (my cruising altitude was 38000ft). I noticed that the FMC had a message that said DES PATH UNACHIEVABLE, that was weird because I set the right altitudes for each waypoint and VOR for exactly what they should have been. I got the aircraft to descend a little more by copying of the speed and altitude of the first descent waypoint and pasting it again on the same waypoint. But I only got the aircraft to descend to 32000ft. I also noticed that when I am climbing above 25000ft the aircraft slows down the climb to 1000fpm, compared to 1800fpm in other payware aircraft. I would appreciate some help here!Thanks,Alex.
- 10 replies
-
- Descent
- Descending
-
(and 8 more)
Tagged with: