When FSNAV is displayed, I don't have my Approach Arrowed markings (IFR) displayed for KJFK and KORD. There may be other airports, but I have not researched that far.I use SimFlyer airports for these locations (among others which have no problem)and thought that might be the problem. Disabled SimFlyers and went to the default airports and the same thing, no markings. I assume this lets SimFlyers off the hook.What I mean is that the approach arrowed markings which also include the frequencies on the FSNaV map display. The airport only is shown as having no IlS approaches.All other airports that I have checked, including those adjacent to KJFK and KORD include the displayed markings (i.e. KEWR, Midway) with no problem.I have updated the FSNavDBC.exe files and the SimFlyer updates. I know the SimFlyer updates took as the errored Glideslope approaches have been corrected. This is somewhat academic when they are disabled and I go to the defaults.Please check your map if you implement FSNav and see if you have these displayed. I would have sworn that I did in the past, but have lost them for some reason.Any ideas?Thanks:RTH1585368CFIEdit: One word of clarification. The approaches work fine. The markings just are not shown on the FSNAV map display.

I've had this with FSNav too. One thing I have found is that FSNav still reads exclude files. Even though you cannot exclude navaids in FS2004 I suspect FSNav isn't aware of this (it's not been updated for a while) so ANY exclude will remove navaid data. It's not just ILS's that disappear - you can also lose NDB's and VOR's.Check that there isn't an exclude buried away somewhere for these locations. It might be worth also disabling any AFCAD's as these may also cause a problem.boneshttp://fsaviation.nethttp://www.precisionmanuals.com/images/forum/ng_driver.jpg

Thanks Bones:Somewhere in there I think you were on the right track.After installation of FS, I always save all default folders and files that I think might be critical.I went back to the default scenery, addon scenery, and scenery.cfg and reran FSNavDBC.exe, and then put my current files back in action.The ILS display is complete again. Probably was tied to my SimFlyer installations for the airports in question. I never did rerun FSNavDBC.exe before when I was omitting files in my hunt and peck routine. I'm probably missing something, but will deal with that on an individual airport basis if it turns out to be a problem.Thanks again:RTH