I finally found another example of the "divebomber approach" that I wrote about previously.  The screen cap with all the relevant information can be found here.  Please review and let me know if there are any questions.  Thanks very much, hoping we can find a solution for this!

KKT

If you could email the log file for this flight to me at [email protected], I could see the details of what happened.

P2A 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.
 

Thanks,

Dave

 

1 hour ago, Dave-Pilot2ATC said:

If you could email the log file for this flight to me at [email protected], I could see the details of what happened.

Hi Dave-
I'm not sure I have your email address, but you can find the file here.  (At least I hope it's the right one!)  Please let me know if you have any more questions or I can help in any way!  Thanks for the prompt response!

KKT

And then the same moment I hit post, I see the email address in yours!  DOH!!!  LMK if you still want me to email it or if the link works for you.

Thanks again,
KKT

KKT,

I was able to use the posted log file.

It appears the flight plan had waypoints leading to a nice transition to the ils for Rwy 34L/R, but an approach to Rwy 16.

The TOD calculation assumed it was going to be following the flight plan around to south of the airport, but when the flight got near the TOD, the program calculated the need for vectors and with the 180 from the route to ILS final, it decided to give vectors.  At that point, you were almost on top of the FAF for Rwy 16.

When you planned this flight, you could have planned it with a STAR and approach to Rwy 16L/R or you could have planned it direct to the airport from TEKEL.  Then you would have had the TOD a little after TEKEL and all would have worked out.

Dave