You are on page 1of 5

Garmin Prodigy Database Card Files

Airframe_info.xml File:

This file is placed on the card by the Prodigy system. A brand new card will NOT have
this file. It is for information only so you can see the system’s software level it is running
on, and the System ID#. If this file is deleted, the system will add it back onto the card.
It will not interfere with the operation of the databases.

Feat_unlk.dat File:

This file is placed on the card when the databases are written to the card. It is
required. It controls the copy protection for all the databases on the card. If that file is
absent, NO databases on the card will be accepted by the Prodigy system. To get it
back after deleting it is to have the customer re-program each database onto the card
using flyGarmin.com.

Avtn_db_stby.bin File:

This is the optional standby Navigation database. It is loaded onto the card from a
regular Nav DB loader card in the top slot. Removing it does not affect the operation of
the other databases. It can only be used with GDU sw 10.00 and higher.

Apt_dir,gca File:

This is the optional AOPA airport directory file. It can only be used with GDU sw 10.00
and higher.

Prodigy Database SD Card Files

010-00330-41 Card Files:


010-00330-42 Card Files:

“fc_tpc” directory of -42 card:

In the “charts” folder there will be 2900+ files containing the FliteCharts.

010-00330-43 Card Files:

“fc_tpc” directory of -43 card:

In the “charts” folder there will be 2900+ files containing the FliteCharts.
Jeppesen Aviation Database Card Files:

Ldr_sys Folder:

Jeppesen ChartView Card Files:

Charts Folder :
Jeppesen ChartView Card Files (continued):

Fonts Folder:
Database and Unlock Card Notes

Feature Unlock Cards (SVT, TAWS, ChartView, etc.) :

An Unlock card is readable by a computer only when it has NOT been used. If the
computer can not read an Unlock card, it has been used in a Prodigy system. The
System ID the card is locked to is not retrievable.

Last updated 09/06/2010

You might also like