Ummm, the plot thickens.

Today I reversed a flight plan from Cannes to Venice which worked perfectly in the G1000the first time round. Once reversed (Venice to Cannes) it was only part imported and locked (G1000 does this automatically when there is an error).

Anyway, this time I looked through the flight plan and found the locked waypoint which was x thousand miles to that point (maybe that's how they pick it out?) anyway, I deleted that and the flightplan worked fine.

I didn't have time to work out which waypoint it was on the ground as I needed to dodge some imminent CBs forecast, however next time I could and manually enter the coordinates, although I've got no clue how to do that.

Off to read the manual, in the meantime if anyone has any ideas how to avoid this error please help!

Thanks

J

If I had any clue what was happening or why, I would certainly chime in, but I don't. It'll be down to how the G1000 is loading the file.

Thanks for the response Tim. Can I ask, does SD rename the waypoints when you save it as a Garmin FPL or is the G1000 that names them when it imports them?

Many thanks

I don't think we rename anything. We encode waypoints in a format the Garmin should understand, but we can only do that with known waypoints such as radio navaids and five-letter airways reporting points. Other things need to be encoded as user waypoints, I believe, with the exception of ICAO airfields where their ICAO identifier is used.

Thanks Tim.

The error has happened on every FPL I've done since I posted this.  I'm going into the G1000, deleting the locked waypoint and it seems to work. 

When I have ground power back home I will have a further play with it.