GPU: GeForce GTX 1080 Ti CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Memory: 32 GB RAM (31.96 GB RAM usable) Current resolution: 1920 x 1080, 60Hz Operating system: ... https://www.youtube.com/watch?v=KsPQWD9H9ZQ

GudDawgAlert Pup gets hit by a B’Ville area 25E car-Hero Wife picks him up and brings him home… is he yours? ... https://www.youtube.com/watch?v=WUQFyLApbCQ

Modded StearmanDriver(SD) RNP RNAV Rwy 26 into PAJN, Juneau, Alaska. SD gave us a cool little route that while not LATLONG nor Fixname accurate...It couldnt be without legal and occupational liabilities...and it worked, but if you look at his FixNames and the LATLONG from the PAJN.txt file for the 737 NGX...it did work pretty nicely...at least as nicely as the charted RNAV course into Rwy 8. I created my own procedure LATLONG rightly or wrongly in a multi-step procedure as follows. 1. I took the raw info provided by SD and flew to each of his waypoints,(if you look, almost all of his FIXs were rounded off...to avoid company or legal problems) noting safe altitude, starting out at 7000ft, creating user waypoints in my GTN750, looking around for first, vertical, then horizontal safety...keeping in mind that Ultimately...I would not be using this data for my Duke, but for the Procedure page of my PMDG 737 NGX..which you already saw me fly with SD's fixes. 2. I took my Turbine Duke up and noted the REAL LATLONG as reported by slewing and world map...transposed those numbers into the format that PMDG's procedures needed DDD.mm fractional minutes. I converted using http://www.directionsmag.com/site/latlong-converter/ 3.I created my own mid-point user waypoints from the west CHRTRN,and the NNE CHRTS so we could have approaches from those directions. 4. I put my Duke into autopilot, knowing the lateral info...my flightplan was correct, but I would have to handle the Vnav manually. Turns out its rather manageable with the following info CHRTRN 5000FT ... https://www.youtube.com/watch?v=TZCvio0gTag

... https://www.youtube.com/watch?v=OqaDZohMiPA