FLTA Alert when landing at MMLT

The IFD540 FLTA algorithm did not recognize MMLT as an airfield and therefore did not create the standard airfield exclusion area which suppresses FLTA calls in the terminal environment.

Now the reason the IFD540 FLTA did not recognize it as an airfield is due to a situation that we just recently found.   MMLT has some special fuel types associated with it in the database - it has 100/130 and JetA1 fuel, both non standard fuel encodings in the Jepp data.    Data logs also indicate you changed the map fuel filtering setting from the default fuel filter (any fuel) to 100LL.  That is a perfectly plausible thing to do operationally but inadvertently filtered out that airfield as an airfield and therefore the FLTA algorithm was projecting an imminent impact with the ground and issued the warning. 

We are making a software change that provides more flexible fuel preference filtering so that this isn't an issue anymore.