Is it possible to detect that a 2004 aircraft is 'broken'?

[skydriver]

Peter:

I wondered if it is possible to detect that a 2004 aircraft is 'broken' rather than crashed?

I refer to those landings where FS has decided to break several functions of the plane - the engine, etc. but does not actually report a 'crash'. The plane is going nowhere, but there is no crash.

Can this state be detected in FSUIPC?

Thanks

SkyDriver

[Pete Dowson]

I wondered if it is possible to detect that a 2004 aircraft is 'broken' rather than crashed?

I refer to those landings where FS has decided to break several functions of the plane - the engine, etc. but does not actually report a 'crash'. The plane is going nowhere, but there is no crash.

Can this state be detected in FSUIPC?

See if any of the assorted failure flags are being set: search for "Fail" in the programmer's guide Table. There's a batch at 0B64, but they seem to be all panel instrument problems except for the Engine, Another at 3BD6 is similar. Certainly an engine failure should be detectable.

The main failure which can easily occur on a hard landing, but doesn't seem to have an indication anywhere, is where the nose wheel strut or even complete gear system collapses. The only indication of that I know of is that the aircraft is flat on the concrete and the gears don't work. I think you can also damage the gear trying to lower it at too high a speed, but again I don't know any indication I can read -- all you find is that the gear system is inoperable when you try to use it.

As for body part damage like a broken wing, I would think this all comes under "crash"?

Regards,

Pete

[skydriver]

Pete:

Will investigate the registers in your docs as sugested.

It would seem reasonable to say that if the engine fails within a *very* short time after touching down (say less than 1 second) - it was due to a bad landing.

It's FS's way of saying "You broke it even if you didn't crash it..."

Thanks for all the information!

SkyDriver