Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

PerWel

Members
  • Joined

  • Last visited

Everything posted by PerWel

  1. This have happen sometimes in the past. I ignored it.
  2. Thanks I was only looking in the ATC tab and Ignore Airway alt was in FLP tab. Validate OK now. But one thing is strange and that is: I changed all FL in far right column to be inside restriction FL but still Validate failed!?
  3. Ignore settings have worked before.
  4. This FLP Validate fails with Alt Restrictions even with settings set to ignore Altitudes. All of them. Strange is that it is after the SID. Restrictions must have been added by P2A EGNX/27 TNT2N TNT M868 ADELU L60 MAMUL L603 LAMIX UT29 LIBSO UL975 ERDOW DCT ROPAL DCT LESRA DCT EPILO DCT KULUD DCT GELDA DCT ORVIX ORVI2T EVRA/36
  5. OK I suspected something like that so I have changed my CO pilot voice. Will see/hear how it works 😊
  6. OK misspelling?😄 English is not my first language I'm Swedish When ask for flight and get TO RWY and so on?
  7. Clerance gives me RWY 14 for TO then when asking for taxi GRND tells me to taxi to 32. I did ask for taxi to RWY 14. Some times it switches between L and R. Eg Clerance 18L then GRND 18R. So it seems like Clerance does not give GRND what RWY for TO
  8. Just a report. So far no major problems. Only that ATC and my CO pilot is the same voice 😄
  9. Only response from ATC is Good morning Tried both climb to FL390 and New FL390 Same answer, Good morning
  10. I have seen those too, ghost planes sometimes on RW or Taxi and sometimes way outside airport. Not visible in XP
  11. I take this back working now, yesterday it did not. Change is that XP released a new beta 3. Yesterday I had beta 2. So maybe XP is the problem with sending AI info.
  12. FYI Just now starting a flight with latest XP beta and latest Zibo and radios works with no problems
  13. On this flight Center did not start do descend me I had to ask to descend and no handover to Appr so I had to ask for ILS landing. OK got that and started to vector me, I was way to high. So at FL120 they told me 2 nm from ILS turn xx, totally impossible to land so I had to turn away from that point to go down. So approach needs some work. Previous flight I was descended in time, no problems. Feel like random approach events. By it is an early access release and I understand that there lots of work to do.
  14. Thanks for IRL info how it's done.😎
  15. Thanks for info 👍
  16. I am not complaining I like P2A very much and prefer to use it over other ATC. 😎👍
  17. I have done that so far. Is it only the way? In other ATC I enter final Cruise level from start and ATC prevents me from higher because of restrictions. But in P2A if I enter eg. FL360 as final Cruise altitude Validate says no because it violates restrictions.
  18. Forgot to add..... I understand that on long flights like 10-12 hour and lots of fuel is burned so you get lighter then it is up to me to ask for higher level because I can. ATC does not know that. What I asked about is SC because of airway restrictions both lower and higher.
  19. How do I deal with step climbs? If Cruise level is FL200 after loading from Simbrief, first two legs are that but after that FLP says FL360. If I change Cruise level to FL360 all navpoints are changed to FL360 that is wrong first two nav points should be FL200. How do I do, is it ATC that will tell me when it is Ok to climb to FL360 or is it up to me to keep track of that. I have no idea how SC works IRL. I wonder how to program step climbs in P2A
  20. Approach needs a lot of work and to believe Dave is doing that. This flight LMML -> LGAV was OK until approach started, ATC told me to descend but way way to early. Was a FL330 Got info about vector to ILS 03 where IF is at 1900 feet When 200 nm to go told me to desc to FL250 Then 150 nm to go order to desc to FL170 Then 100 nm to go desc to 1500 feet !!!?? What?? So I disconnected and did the rest by myself. It is a VA flight and can not let it go wrong/crazy, must do at least nice landing. Does it not check the Profile that I am a Airliner??
  21. Again no descend order!? Vector again but this too did not have any STAR so nothing to say about it. Can it have to do with no STARs that descend does not work? Should not ATC follow what is in the FLP window in P2A, Trgt Alt. It did not descend me at TD so I was still at FL350 at LPD (FL245)and when closing in to LUZOT (FL195) and no descend order I asked for descend to FL110 and then ATC started to descend me. Had to do a long detour to get down.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.