Flacon 50EX - Problems

[EHM-2029 Sotiris]

Hello All,

just wanted to raise an issue with the falcon 50EX and just want to ask around and see if it's only my problem.
After landing after a 6 hours flight from Dubai to Athens, I was so tense not to fail it (being online etc.) that I ended I ended up actually bringing the plane to a complete stop on the runway.
All well until this point.
Yet, when I wanted to manouevre and vacate the runway, upon giving some thrust the tires started smoking like mad and soon after the plane crashed while straight, level and stationary.
(P.S. although obvious, no parking brakes were engaged)

Has anyone had the same issue?

Also on Falcon, while its published cruise speed is 280kts or 0.85 at high altitutes it would struggle to exceed 0.75 even at full power.
And finally, on the autothrottle: while it performs admirably on low speeds and is excellent at keeping the correct low speed during approach, in cruise or climb, it reduces power and if left unchecked, it brings a stall.
(again, obvious as it may have be; the autothrottle was engaged first and then set to the desired speed).

It is only me?

[EHM-1001 Robert]

Hi Sotiris,

unfortunately the Falcon50 seems to not be compatible with FS2004, even though, the designers stated: it is. This issue will be fixed soon (EuroBusiness is next in the renewal process).

I cant say anything to the brake problem. Is not it possible they overheated, and the smoke came ? Then the whole airplane burnt down probably :s

[EHM-1465 Dominic]

Sotiris,

Just a thought but what AFCAD2 file are using for Athens (if any)? And do you have any addon terrain mesh?

I think that quite a few crashes are caused by invisible buildings, uneven terrain and other scenery conflicts that often originate from the AFCAD2 file (if you're not familiar with these, it's the file that tells FS9 where the runways, taxiways, ILS etc all are) or otherwise from scenery mesh that has things at different elevations from the airport scenery.

[EHM-2029 Sotiris]

Dominic,

I think you maybe right as I have indeed installed a whole series of meshes and add-on sceneries for Greece.
I will try the Falcon also on a standard area, because also prior to the smoking of the tires I experience several bumps that I hadn't until that point. (i.e. all the runway length until the full stop was smooth but after restart of taxiing smoke came from all over, the airframe shook and I got my crash!!)

[EHM-1001 Robert]

The AFCAD file can change the runway surface, but it does not contain invisible objects, only the airport layout, you can trust in them

[EHM-1465 Dominic]

I'm afraid I have to disagree Robert

Unfortunately AFCADs can cause problems and are responsible for lots of posts in Flightsim forums ! A lot of the time it is because an addon scenery will contain a new AFCAD file (airport layout) with a non-standard name or in a non-standard location.

So you may end up with two layouts for the same airport... Only one will be visible (whichever has highest priority in your scenery settings) but the other can cause a crash because it's still there with its taxiway signs, windsocks etc which are invisible to you but not to FS... So when you taxi into them without realising they are there, FS registers a crash!

The best way to avoid this is to make sure all your AFCAD2 files are in the correct place - the 'Addon scenery/scenery' folder and that they all follow the standard naming convention of 'AF2_EGLL' (as an example for Heathrow) - the only letters in the name should be AF2_ then the ICAO code for that airport. This way you cannot have two files for one airport.

Sometimes the AFCAD designer doesn't exclude or flatten the default airport they are improving so this also leaves invisible objects beneath the new layout for you to crash into!

So while the top AFCAD doesn't include invisible objects, it's what is hidden below you have to worry about...

[EHM-1001 Robert]

Okay that is true...I thought we should not have to mention this 1 AFCAD: good, more AFCAD: bad !