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.

Weird TOD in 2.5.0.3

Featured Replies

Hi Dave,

   Was flying from KLGB to KLAS (see attached screen of p2atc setup).  The TOD looks like it was calculated incorrectly for some reason.  You can see it put the TOD almost at the approach start.

https://photos.app.goo.gl/nYJZncLTz3PCicKH2

Joe

 

  • Commercial Member

Joe,

When I enter KLGB, KLAS and then press AutoPlan, I get the SID and Approach, no STAR.  I then added the KEPEC6 STAR with the MISEN transition and get a route much like yours.  However, the TOD is properly placed about 195 NM before destination, right before HEC.

What process are you following to get the bizarre result you have in the picture?

Thanks,

Dave

  • Author

Hi,

   I didn't use the auto plan.  I entered as follows:


1) Enter KLGB way point (manually)
2) Enter KLAS way point (manually)
3) Click SID button, selected Runway 30, ZOOM1 with MISEN trasition
4) Click STAR button, selected KEPEC6 with MISEN transition
5) Click APPR button, selected 01L ILS with Vectors to CODNO
6) Selected cruise altitude 270
7) Filed flight plan

(Ground speed 450 and Descent 1200FPM were auto populated from previous flight)

Joe

 

 

Edited by mihalich

  • Author

BTW, i just repeated those exact steps and got the exact same TOD right before the approach.

The problem starts when i select the STAR.  After selecting the star (before selecting the approach), the TOD is right at the last star waypoint.

Joe

 

Edited by mihalich

  • Author

Btw, there appears to be another small bug while you're in there looking at this...just saw this by accident.

It appears that if you add a way point, and then delete it, and then add another waypoint, it adds the new waypoint, but also re-adds the one you deleted.

Steps:
- Launch app

- add waypoint KJFK

- click on icon left side of jfk and click Remove in the window

- add back waypoint KJFK

- add waypoint KROC

- now in the waypoint list, you have KJFK, KROC, KJFK.

Reproducible, so should be easy to find.

Joe

 

 

Edited by mihalich

  • Commercial Member

OK.  I fixed both issues.  They only crop up if things are done in a specific order, but now they should both be fixed.

On the KLGB-KLAS issue, it was because there were not en-route waypoints and the last SID Wpt was the same as the first STAR Wpt.  Avoiding this situation should be a good work-around.

On the Add/Remove problem, using the "X" Wpt button instead of the Remove option is a workaround.

Joe, thanks for the detailed steps to reproduce the problem!

Will be in the next update.

Dave

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.