First, filled out the POS INIT page with KBOS. The displayed longitude for KBOS was wildly incorrect (east of 0). I line selected the last position and used that for the IRS position. I have yet to be able to enter a position by hand.Then, I entered the route to KJFK: LUCOS SEY PARCH CCC ROBER, and activated it. Looking at the plan page, it clearly had a bogus idea of where KJFK was; it was significantly east of CCC. When I entered a runway (22L), it magically put KJFK in the right place. Shouldn't the plan show the airport in the correct location without a runway selected? What if ATC hasn't given me the runway yet?Then, I went to the ROUTE 1 page, line selected DEST, got KJFK, and then pushed that into DEST. The result: FS2002 crashed an ugly death. Whether or not that key sequence is allowed by the FMC, crashing FS2002 isn't acceptable.I have not loaded any new navdata. Is it using my already installed 767PIC navdata?Lee Hetherington (KBED)

Lee,Some people reported in this forum they had airport positions problems until they installed the latest AIRAC cycle.As for the crash... hum... I'll try to reproduce it but I've done that many times (re-setting the dest with same...)stay tuned.anthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com

Lee,I did exactly what you describe above. I had no crash.Did you forget a step ?What I found out was that when I tried deleting the runway entry on either RTE or LEGS page, I had a crash, but it was handled (ie did not lead to FS crash).Also, I found out that inputting a new destination deactivated the route, which is a problem. I fixed that.anthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com