1. I have a standard aircraft.cfg that I use to ensure every aircraft I download will work in FS2002. I've not had a single aircraft failure because of aircraft configuration. The standard is:

Here is what you do. The very first thing after unzipping your aircraft file, you copy this "standard cfg" into your aircraft's "aircraft.cfg" file. Paste it directly below the one in the file you just unzipped. Carefully take the entries from the new configuration and replace the ones in the "standard." Make sure you keep the naming convention in the standard cfg i.e., Manufacturer, aircraft type, airline or military service, or I use "Per" to indicate an aircraft is a private aircraft. For example, if the new aircraft's "aircraft.cfg" file says the "title=" is b47. Replace that with the example in the "standard" - Boeing B-47 Stratofortress US Air Force. When your done, delete the data above the "standard." Also, if an entry is blank don't worry about it. You may at some point fill in the new information so its OK to keep it in there. The following are the critical entries that MUST BE THERE.

It may not be obvious but the "ui_manufacturer=" statement ensures the aircraft manufacturer will show up in its drop-down list. The "ui_type=" drives entries in the next drop-down list. The "ui_variation=" ensures there is an entry in the "Variations" list. If you want to check how FS2002 displays your new aircraft, try removing the data after the "=" sign using this statement - "ui_type=" - before you load FS2002. I think you'll find some part of your aircraft cannot be selected.

I didn't mention the "sim=" statement. If you don't get that one exactly you don't have an aircraft at all. Make sure it matches the *.AIR file label. If you think that doesn't happen-GUESS AGAIN. So far, I've found about a dozen aircraft that had the wrong *.AIR reference in the aircraft.cfg file. It happens so check it.

2. Now, copy the "title" statement you just made and replace your aircraft's folder label with it. Using our b47 example, WinZip might make a folder for your aircraft with a label "Aircraft." Replace that with the above. You now have a match in your config file with your aircraft's folder label.

3. Drag the new aircraft to your FS2002 Aircraft folder. If you use the same convention every time you will find all your Boeing aircraft, your Embraer planes, and the like together and in decending order of type. If you have been religous about this standardizing, you will find that when you select the "Manufacturer" from the FS2002 "Create a Flight" menu, you will have all (for example) our Boeing aircraft in one place, the "Aircraft Type" drop-down list will reflect how folders look in the Aircraft Folder, and you should completely eliminate any "Unspecified" aircraft in that list.

NOTE: Be sure to do the same thing for every "(fltsim.n)" section in the aircraft.cfg file. That way all the aircraft variations will be listed under the Aircraft Type entry.

NOTE2: You probably noticed the 4 "checklist" entries in the "standard" above. Personally, I don't like having a lot of loose files running around in my main aircraft folder. So, I put all checklists, references, and note files into a container I call "chk-ref-notes." I use a similar nameing convention to the "title=" statement so that I maintain the standard naming convention. These 4 statements allow you to move those three files to that folder. (Yes, you need 4 statements to move 3 files)

NOTE3: In addition to the above, I also use a folder labeled "docs." I move all the "readme" files and manuals into this folder.

NOTE4: In addition to the "standard" aircraft configuration NotePad file I mentioned above (I keep it on my desktop for easy access), I also keep two blank folders on my desktop. Their labels are "chk-ref-notes" and "docs." That way, when I get a new aircraft I just copy and paste the two empty folders into the main aircraft folder and "presto-chango" I'm ready to arrange my new aircraft.

NOTE5: If you really want to be tidy, remove all the picture files from the main aircraft folder. I put them in a folder outside FS2002 for reuse later. You'd be surprised how a picture of an aircraft can help you determine things like sound or smoke. If you know an aircraft needs a 4-engine sound package it doesn't make sense to load a 737 sound file. You want to get things as close as you can. So, what is left in your main aircraft folder. You should now have the following:

Main aircraft folder: Label = Mfg, afct type, airline or mil, Per (Example: Boeing B747-400 American Airlines) Note: If an aircraft supports more than one airline, I use two-digit codes in place of the airline name. For example this B747 might support Orbit Airlines, Landmark Airlines, American Pacifica Airlines. I use a code - OA-LA-AP for the airline in the standard labeling convention. One more CRITICAL piece of the naming standard. I like to keep track of the DEFAULT FS2002 aircraft so I don't modify (unless very carefully) those aircraft. If you screw up one of these you could disable FS2002. What I do is add "STD" to the folder label. This tells me that the aircraft is a default one.

Subfolders and files: (ONLY ONE OF EACH OF THESE CAN BE ACTIVE AT THE TIME YOU LOAD FS2002)

1. model folder
2. sound folder
3. panel folder
4. texture folder
5. chk-ref-notes folder
6. docs folder
7. *.AIR file
8. aircraft.cfg file

Try it, you'll like it. Mikey did.