According to your log, only one of the four runways at KACV has ILS (runway 32) and it is a nontowered airport (only Multicom, Unicom and FSS), so by itself the following can be correct:
Piper 16 Juliet Cleared for the ILS runway 32 Approach Radar service terminated. Squawk 1200, change to advisory frequency approved on 123.5 |
Wind direction was 360, so runway 32 sounds fine, too. Runway 2 might have been a little bit better, but it seems PF3 wanted to give you ILS. It logged "Weather conditions do not require ILS", so you could have switched to a visual approach (either send "report runway in sight" or request a different runway).
Regarding the U-turn, here are the relevant parts of the log, "UAlt" is the aircraft altitude:
9/26/2016 8:34:44 PM: 770 - Transcript: 'Piper 16 Juliet maintain Heading 275 expect vectors for the ILS runway 32 Approach '
9/26/2016 8:35:10 PM: 370 - Transcript: 'Piper 16 Juliet Turn right heading 340 '
9/26/2016 8:35:15 PM: 620 - Dist to Runway: 28.53731
9/26/2016 8:35:19 PM: 320 - Transcript: 'right to 34016 Juliet '
9/26/2016 8:35:24 PM: 500 - Ulat: 40.5538010531091 ULon: -123.811545073872 UHdg: 275 UAlt: 7701 UIAS=99 UGS=105 TOD: 16 OTG=False
--
9/26/2016 8:37:35 PM: 220 - Transcript: 'Piper 16 Juliet Descend and maintain 6 thousand 5 hundred '
9/26/2016 8:37:48 PM: 460 - Transcript: 'Out of 7 thousand 5 hundred for 6 thousand 5 hundred 16 Juliet '
9/26/2016 8:37:59 PM: 340 - Ulat: 40.6273536374456 ULon: -123.841768341628 UHdg: 334 UAlt: 7448 UIAS=108 UGS=113 TOD: 16 OTG=False
9/26/2016 8:38:00 PM: 610 - Dist to Runway: 23.75764
--
9/26/2016 8:39:16 PM: 400 - Transcript: 'Piper 16 Juliet Descend to 6 thousand '
9/26/2016 8:39:21 PM: 570 - Dist to Runway: 21.23993
9/26/2016 8:39:25 PM: 230 - Ulat: 40.6745461956231 ULon: -123.851779882594 UHdg: 334 UAlt: 6520 UIAS=93 UGS=98 TOD: 16 OTG=False
--
9/26/2016 8:39:40 PM: 300 - Transcript: 'Piper 16 Juliet Contact Approach on 123.5 '
9/26/2016 8:39:46 PM: 550 - Transcript: '123.51 6 Juliet '
9/26/2016 8:39:58 PM: 130 - Transcript: 'Piper 16 Juliet Descend to 2 thousand 5 hundred '
9/26/2016 8:40:12 PM: 300 - Transcript: 'Roger Out of 6 thousand for 2 thousand 5 hundred 16 Juliet '
9/26/2016 8:40:22 PM: 050 - Ulat: 40.7039987112179 ULon: -123.858066696704 UHdg: 334 UAlt: 5667 UIAS=96 UGS=101 TOD: 16 OTG=False
9/26/2016 8:40:23 PM: 230 - Dist to Runway: 19.4788
--
9/26/2016 8:47:56 PM: 560 - Transcript: 'Out of 4 thousand for 2 thousand 5 hundred 16 Juliet '
9/26/2016 8:48:02 PM: 680 - Ulat: 40.9276387460518 ULon: -123.904412861142 UHdg: 334 UAlt: 4073 UIAS=105 UGS=107 TOD: 16 OTG=False
9/26/2016 8:48:03 PM: 810 - Dist to Runway: 9.370623
--
9/26/2016 8:49:24 PM: 750 - Transcript: 'Piper 16 Juliet Cleared for the ILS runway 32 Approach Radar service terminated. Squawk 1200, change to advisory frequency approved on 123.5 '
9/26/2016 8:49:38 PM: 370 - Transcript: 'Out of 4 thousand until established on the ILS runway 32 16 Juliet '
9/26/2016 8:49:45 PM: 590 - Dist to Runway: 8.502624
9/26/2016 8:49:49 PM: 110 - Ulat: 40.9782685923284 ULon: -123.916299130701 UHdg: 334 UAlt: 4044 UIAS=97 UGS=97 TOD: 16 OTG=False
|
You did not descend to 2500, but stayed at 4000 until you reached the FAF (which you have configured at 9 miles, which is a good value). ATC did not tell you to make a U-turn, but you did it on your own to descend and catch the ILS.
In the real world you probably would have announced a missed approach or go-around, and this is what you can do in PF3, too.
Or request a different runway and enter the local pattern for a visual approach, though I don't know exactly what the correct procedure would have been in this situation, as you approached a nontowered airport and radar service already has been terminated. Probably something like 8 to report airport in sight or Ctrl+Shift+W to select a different runway, tune to Multicom or Unicom, and then 0 to Check-in and 2 to enter downwind.