Hi Dave.

I had an enjoyable flight with P2ATC (it gets better and better!) and X-Plane 11.25 this morning until I was being vectored to the final.

LGAV/03R VARI1E VARIX UL995 RDS UM601 BONEK DCT LCLK/04

http://vau.aero/navdb/chart/LCLK.pdf

I was brought down to 5600 ft at BONEK, then was vectored on Hdg 132 towards final VOR/DME Z Rwy 04. After (just) skimming the tops of the Cyprian mountains I was not told to descend further which meant I was too high at D12 and unable to make the 2000 ft constraint at D6.9 (FF04). I therefore reported a Missed Approach and was told to fly the published MA procedure which I did and held at AMAKO. I sat in the hold for a while and heard no further instructions, until eventually I lost patience and vectored myself towards final again. Out of curiosity I tried reporting Field In SIght and got my Cleared to Land instruction.

Did I do something wrong here or miss a step, or was P2ATC at fault?

Many thanks.

I can't tell without the log file, but if you were cleared for the VOR approach, that clears you for descent to the published altitudes in the approach.  So at LCA you should have started your descent to 2000 ft.

When you executed missed approach, you should have been told to contact approach and at that time, you would need to request another approach.

If you send me the log file to [email protected] , I can have a look.

Log files are located in: 
C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs 
where <UserName> is your PC user name. Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, so if you take the most recent one when you have the error, you should have the correct one.  
 

Dave

Edited August 24, 20187 yr by Dave-Pilot2ATC

Thanks Dave, I have sent you the log file.

The problem is that I was vectored not cleared at 5600 ft, and by the time I was cleared to final I was too high to successfully make the approach at 2000 ft.

For this flight P2A did not choose a STAR; ideally it should have been BONEK 1A or 1R via LCA then VOR DME X Rwy 04. As it was it chose a direct vector from BONEK to VOR DME Z Rwy 04 straight in at D12 at 2000 ft.

As for the missed approach, ATC said "Execute the published Missed Approach for VOR_DME to runway Zero Four Approach". The published MA says I should hold at AMAKO and contact ATC, but once in the hold I was at a loss which option to choose next. Upon reflection I should have probably just reported my position so that's perhaps my bad, I was expecting more hand-holding.

Dave,

Thanks for the log file.  

I found a couple of bugs in that scenario, including the poor selection of STAR and Approach for RW 04.  They will be fixed in the next update.

 

On the Missed Approach, when you contact Approach control, you need to request your desired approach.  In this case something like “<Call Sign> request vectors to VOR approach to runway 04” would work.  This is so the controller will know what you want to do next.

Regards,

Dave