Hello, I know this is not a too recent post, but anyway i'll post here one of the things to try out in case that it is 100% certai n that there is a Feelthere Gauge causing a CTD... (It can also be a bad format texture, in this case find "dxt3fixer" or "dxtfixer" and let it run on the Feelthere folder w here the suspected texture/repaint is, but if you feel this might be a Feelthere Gauge CTD, please continue reading:) Have a look in: ...\Flight Simulator 9\FeelThere\Airbus\FMGC and then into the folder of the Airbus you where rece ntly flying. (A320 / A330 or A340) Every one of these folders contains a "fmgc.cfg" file that basically holds all the MCDU/FMC info, and normally, aft er a flight, it gets "empty" automatically. (not completely though, as your about to find out...) If this "fmgc.cfg" file is around 7-8 kilobyte (and not like around 400/500 bytes only as this should be) than this "emptying process" went corrupt at shutting down the Airbus after a flight. This can also occur in midflight, taxiing or even taking off... what matters is that the information in the start-up of th e Aircraft, and thus also the MCDU/FMC, corrupts with what is inside the "fmgc.cfg" file. What is the solution as to fight this issue? (I take no responsiblities, this worked for me, it MIGHT work for you...) To reset this information! First make sure that your FS2004/FS9 is closed and not running in Windows Task Manag er, as this could give File Access errors. Now follow very precisely everything i write down below: Open the culprit "fmgc.cfg" file with Notepad, (rightclick, Open with...) delete any text or info written inside this fil e, and insert following info: (This is my personal info from my FS9, but at least it gets you to open and fly the Wilco Airbus again, after you can modify this via the FMC/MCDU and by going into the Wilco Airbus Configurator and planning a new flight from sc ratch) For the Airbus A320 "fmgc.cfg" file: [MCDU] CoRte= FlightNumber=IBE9000 [FMGC] FlightPhase=1 FMSFlightPhase=1 IRSAlignment=0 DeltaLat=0.000000 DeltaLon=0.000000 ZFWCG=25.00 ReductionAltitude=3498 ReductionAltitudeGenerated=1 AccelerationAltitude=3498 AccelerationAltitudeGenerated=1 TransitionAltitude=18000 TransitionAltitudeGenerated=1 [Flight Plan] AIRAC-Cycle=1404 NumberOfWaypoints=0 NextWaypoint=0 DepartureIndex=0 ArrivalIndex=0 For the Airbus A330 "fmgc.cfg" file: [MCDU] CoRte= FlightNumber=TAM8012 [FMGC] FlightPhase=10 FMSFlightPhase=8 IRSAlignment=0 DeltaLat=0.000000 DeltaLon=0.000000 ZFWCG=25.00 ReductionAltitude=1528 ReductionAltitudeGenerated=1 AccelerationAltitude=1528 AccelerationAltitudeGenerated=1 TransitionAltitude=18000 TransitionAltitudeGenerated=1 [Flight Plan] AIRAC-Cycle=1404 NumberOfWaypoints=0 NextWaypoint=0 DepartureIndex=0 ArrivalIndex=0 For the Airbus A340 "fmgc.cfg" file: [MCDU] CoRte= FlightNumber=AFR3510 [FMGC] FlightPhase=10 FMSFlightPhase=8 IRSAlignment=0 DeltaLat=0.000000 DeltaLon=0.000000 ZFWCG=25.00 ReductionAltitude=1892 ReductionAltitudeGenerated=1 AccelerationAltitude=1892 AccelerationAltitudeGenerated=1 TransitionAltitude=18000 TransitionAltitudeGenerated=1 [Flight Plan] AIRAC-Cycle=1404 NumberOfWaypoints=0 NextWaypoint=0 DepartureIndex=0 ArrivalIndex=0 You'll see that once you save this file again as a "fmgc.cfg" file, the size will be around the mentioned 400/500 bytes only, and you can safely close the folders, once everything is edited. Now open up again your FS2004/FS9 and try it out... It should work as good as possible! Just like before... As i know, this has been one of the most famous CTD from the Wilco Airbus family, and not even after the Evolutio n version this was solved. Note, this is a DIY Workaround, not an official fix. This type of CTD occured to me a cou ple of times, and i always keep a backup of the "Flight Simulator 9\FeelThere\Airbus\FMGC" folder, so in case this happens, i can copy over the faulty "fmgc.cfg" file. Enjoy your flights, and please do let know of this was usefull to anyone out there... Sure i'm not the only one with tr ouble with Wilco Airbus.... :P Greetings, Diego.