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.

ILS approach EDDM not being read correctly

Featured Replies

I have a flight KEWR/22R DCT MERIT DCT HFD DCT PUT DCT BOS DCT BRADD DCT RAFIN NATZ NASBA DCT RATKA N521 LARLA DCT ABRUL DCT AMUGU DCT ARSUK DCT RESMI UN491 EPL UM164 LUPEN T107 GESLU GESLU1A EDDM/08R created by SIMBRIEF and imported into Pilot2ATC 2018 v.2.6.1.2_x64.  I've done this several times now and it's worked well. 

I validate (GREEN) then press FILE and get the error Altitude Restriction Violation The Minimum Altitude at BEGEN is 5000 feet.  You need to increase your cruise altitude or remove the procedure that contains this waypoint.  BEGEN is part of the ILS approach to EDDM RW08R.  Pilot2ATC has Alt Restr Above 5000 Ft and Pln Alt at 1487ft.  However the ILS approach was done by Pilot2ATC when I selected the APPR button.  The imported flight plan into FlightFactor 767 has BEGEN 170/5000A which matches NAVAGRAPH cycle 2009 charts.  It looks like Pilot2ATC is calculating the Pln Alt. at BEGEN incorrectly.  I tried the same plan with 8L and got the same results, only with MAGAT instead of BEGEN at 5000'.

I've also found that even though I am following a STAR Pilot2ATC will often tell me I'm off course, then a couple of minutes later say Resume Navigation as well as missing TOD.

Is there a way to work around this?  I had to scrap using Pilot2ATC for this flight as it needed to get going.  Thanks!

 

  • Commercial Member

I just tried this and it Filed correctly.  I entered the route you gave, added the GESL1A STAR and ILS to runway 08R.  BEGEN has an Above 5000 ft restriction and P2A planned it at FL050.  When I pressed File, it added the SID and missing NAT points and filed without error.

Something must have gone wrong when you tried it.  You may need to shut down P2A and restart to clear some bad memory or something that is messed up.

There could be a minor difference between your Aircraft GPS location and where P2A thinks you are that would cause the off course call.  Or the waypoints may be different in the STAR in P2A vs the aircraft FMS.  That would definitely cause this.  

Dave

I experience the same issue with "off course and resume own navigation"

The reason behind is, the LNAV is drawn in the ND much more accurate and curved than in P2A.

As an example just see my pictures from departure in LGTS

Cheers 🙂

oz082TK.jpeg

 

epvVEjV.jpeg 

Frank J. Herter

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.