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.

How to recover proper ATC guidance after P2A restart?

Featured Replies

Hi,

 

Sorry if the answer is already in the forum, I was unable to find it.

 

In the case I have to restart P2A during for example the cruising phase, I proceed like this:

 

  • Load and "validate" the initial flight plan in P2A, verify the computed TOD to be in front of my current position
  • Connect to the sim
  • "File" Flight Plan
  • Find the nearest ATC Center or Approach/Departure frequency
  • Contact the controller to try synchronize the guidance with my current position: contact is made, I request my current flight level to be sure controller have it. Controller gives me clearance to the good FL

 

Despite this process, controller NEVER takes the initiative to start descend after TOD, request ATC frequency change, attribute a STAR and approach, clear me for landing. I have to request each step, and find/change frequency myself.

 

Can someone tell me what I miss to get back in the automated guidance process?

Yes I know I have still much to learn :Tounge:

 

Thanks

Roland

MSFS my local airport release: LFOR Chartres-Metropole

MSFS Plugins RAAS (registered FSUIPC7 required)

MSFS FX for Objects & Landmark in France (Steam and smoke) and Aerial coverage for French nuclear sites

  • Commercial Member

Roland,

The only thing you missed is that the initial call to Center must be a first contact call something like "Center, <CallSign> at FL 230"  Or "<CallSign> with you at Flight Leven 230".  That is the normal first contact call and triggers P2A to realize where you are.

After that initial call you can request your cruise altitude and you should then be on your way. 

 

In this scenario, be sure you have a desired approach in the flight plan and if you don't get the "Expect xxx arrival with the xxx approach " call sometime before TOD or the first STAR waypoint, then you may need to request an approach verbally.

 

Regards,

Dave

  • Author

 

 


The only thing you missed is that the initial call to Center must be a first contact call something like "Center, at FL 230"  Or " with you at Flight Leven 230".  That is the normal first contact call and triggers P2A to realize where you are.

 

 

That's the way I engaged the first contact.

 

 

 

 


In this scenario, be sure you have a desired approach in the flight plan and if you don't get the "Expect xxx arrival with the xxx approach " call sometime before TOD or the first STAR waypoint, then you may need to request an approach verbally.

 

 

I'm a little bit confused with this one, interesting subject.

 

 

I usually build a P2A flight plan without SID or STAR waypoints. I only make sure that first and last waypoints match the end/start of existing SID/STAR's.

 

 

With that method, controller is always able to propose a suitable SID during departure clearance, so my understanding is it's not required to insert SID/STAR waypoints in flight plans to get a valid one from the controller.

 

 

In real life I believe also that at least the STAR is dynamically selected by controller during approach as the wind direction can change and so the active runway.

 

So do you confirm it's required to insert a STAR in P2A FP?

Then what happens if the valid runway changes, or I (as a pilot) requires another one?

 

Thanks

Roland

MSFS my local airport release: LFOR Chartres-Metropole

MSFS Plugins RAAS (registered FSUIPC7 required)

MSFS FX for Objects & Landmark in France (Steam and smoke) and Aerial coverage for French nuclear sites

Archived

This topic is now archived and is closed to further replies.

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.