Jump to content
Sign in to follow this  
BlackBeltMike

Request vectors for landing behaviour

Recommended Posts

Good evening,

I called request vectors for landing and approach directed me back to the airfield's general vicinity and switched me to Tower frequency, and from there I was expecting/hoping the tower would give me turn left/right instructions right the way until onto final approach, but it didn't.  I'm not sure if that's reasonable or whether it doesn't work like that?  Thanks.

Mike  

Share this post


Link to post
Share on other sites

It should work, it has worked for me before. For example I say: <Callsign> requests vectors for <ILS or Visual> approach to runway <RWY>


Joel Pacheco

X-plane 11.5, i7 4790k OC 4.8GHz (1.330V) - Nvidia GTX 1080ti - Asus Sabertooth Z97 Mark 2 - Corsair Hydro Series H115i - Kingston HyperX Fury 16GB 1866MHz DDR3 CL10 - Samsung 860 EVO SSD 500Gb  - Windows 10 Pro - HP Reverb G2 

Share this post


Link to post
Share on other sites

Yes that's the call I made, though I forgot the ILS/visual part - the log file shows P2A assumed visual.  I still expected to be guided around the circuit though until final approach, but what happened was after nearing the airport, Approach handed me over to Tower.  I had been vectored in perpendicular(ish) to the runway heading, then the P2A co-pilot checked in with the Tower, "descending to One Thousand  Seven Hundred feet".  The Tower did the read-back of that.  I continued my current heading for quite some time waiting for the next instruction from the tower but it never came.  After flying away from the airport (too far imo) , I decided to manually turn downwind and called that to the Tower.

I'm still getting used to P2A so I'm not yet sure what I can / can't do, so is the above the expected behaviour?  

The other thing is when Approach was vectoring me in, the P2A map window was showing a very odd diagram for the circuit, which I couldn't really understand (and I have a screenshot of it).  I have had to hand-edit the taxi-ways on this airport as the data was incomplete (by default it just has the runway only), so is it possible I messed that up?

 

 

Share this post


Link to post
Share on other sites

Mike,

When you don't specify that you want vectors to the ILS for runway xxx or to the visual straight-in for runway xx, then ATC assumes you just need help finding the airport and you will be contacting tower and requesting a VFR entry to the pattern.  At about 10-12 miles out, Approach will had you off  to Tower and you need to make a call something like "Tower, <CallSign> is inbound for landing", at which time the tower would give you pattern/runway information and tell you to report downwind.

I suspect the strange looking diagram for the circuit was a VFR pattern with the entry included, so it may have had an overfly of the airport and a turn to get onto the 45 to downwind.

Dave

 

  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...