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.

Lost ATC Control

Featured Replies

Don't know what I may have done wrong but here's what happened>I filed for an IFR VOR to VOR flight from Anchorage (PANC) to Kodiak (PADQ) at 12000 ft. ( Was going to fly the Baron but changed my mind and flew the Lear). After being vectored on route by ATC, I requested a higher altitude of 17000 ft. which was approved.Somewhere along the flight I no longer heard from ATC. Never a command to reduce altitude, so I flew all the way to Kodiak and at least 15 miles past it at 17000 ft.My question is why did I lose ATC control? As I neared the field (at 17000 ft) I had the menu option of either a visual approach or an IAP approach. Didn't do either one. It was supper time so I just ended the flight. I expected to be vectored to the field for landing as I had at other flights at other airports.Am I missing something here. (Wouldn't be the first time).Thanks for any help on this.Jim

  • Author

I think I may have discovered my error. On the controller info section, the "Arrival" Departure and Approach blocks were unticked.Does that mean that Arrival/Approach controllers are not available at that airport? Maybe I should RTFM a little more.I would still appreciate an explanation for this if you don't mind. These blocks were always checked on every other flight I have done so I didn't notice them being unticked.Thanks,Jim

  • Commercial Member

i'm guessing padq doesn't have an approach controller, and eventually center would have started you down and asked if you had the field in sightjd

PADQ does not have a local controller according to the airport approach plates. It is surrounded by steeply rising terrain on the north, west, and south sides to almost 6,000 within 25 nm.I suggest going to www.flightaware.com - resources. Input PADQ and then download the bundled procedures. I had trouble tonight with the bundle but individual procedures downloaded OK. The only allowed IFR runway is 25 by flying over the airport, descending east, and then turning west to catch the ILS. The other option is to route to the SE IAF point HINBU. Get the ILS and STAR procedures. Include the STAR in your plan and many but not all the waypoints will be followed untgil vectoring starts. An appropriate entry from the north would be a DME arc from the CINEK waypointFor this airport there is no local control but initial separation should be provided by Anchorage center. Chances are their radar can't make the range at lower altitudes. In this situation I'd select an IAP to follow the STAR and approach plate.If weather determines you land on other than 25 then you must do a circle to land procedure. The only allowed IFR runway assignment is the 25 procedure breaking out at 660 feet for the circling approach if needed.Check the MSA in the controller page for that airport.Also, at least in reality, you are for landing on 25 requires to do so visually at 2.2 nm from the threshold at I-ADQ DME 3.5.I assume you were at 17,000 feet well before 40 nm out and did not ask for higher within that range. I assume if you had the comms that you acked all ATC commands so RC would progress to the next step.

Create an account or sign in to comment

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.