Hi JayS. Look for a file in the CFS2 root folder named Error.log & open it in Notepad. This will give you the name of the problem mission & the unit number of the offending aircraft in that mission. You can use this information to find the type_id number & the name of the aircraft in that particular mission. This is an example from a default mission. Let's say my Error.log tells me this.
[Mission file error]
error=Unable to init unit 9138
First you need to find the type_id= number corresponding to unit 9138 (or id=9138 )
[unit.0]
id=9138
type_id=3814name=%name_string.0%
allegiance=3
skill=3
aggression=2
payload=0
The type_id is 3814. Further down the mission file you should see something like this. (The Notepad Find feature is very useful when searching for these numbers.)
[unit_type.1]
type_id=3814
unit_family=1
name=
f4f4_wildcatThe name= entry is usually (not always) the exact folder name of the offending aircraft. If yours has any other name it will work fine in Free Flight & QC but not missions. This is one of the most common causes of those error messages in missions/campaigns using 3rd party aircraft. The first thing I would check is the folder name of the Br P40K. Make sure it matches the name= entry in the missions. (In your example this is BR_P-40K.) I suspect this will fix your problem. If not, check the title= name in Aircraft.cfg. A few 3rd party missions use this instead of the folder name.
I have less than 96 AC in my Aircraft folder.
The CFS2 "100 plane" limit will vary depending on the aircraft you have installed. If you have over 80 aircraft (including defaults) & get unexplained error messages I would try removing a few 3rd party aircraft.