02-01-2006, 09:39 PM
Yes I know this may sound like I haven't read the FAQ, but today I attempted my first flight with the Level D 767 and I had an engine failure on climb
out. I had NO WORD from the first officer and so I didn't declare an emergency. I thought that Level D's own emergency emulator must have caused the
failure therefore.
BUT when I landed, I was penalised for not declaring an emergency, and FSP said it had caused it! I didn't know that! As a result I really am asking
you Dan please if could make it allowed for people to declare an emergency in any situation that goes wrong, even if it is not caused by FSP. Me
thinking that the engine failure was caused by the level D software and not FSP caused me to be penalised for NOT declaring an emergency, but since I
had no knowing which software did cause it, it's just not fair to add that confusion.
I really would like to see it made possible to declare an emergency in any situation the pilot considers to be an ermergency. Nobody is going to
willingly declare a false emergency anyway, something must go wrong somehow for someone to declare an emergency.
The fact is, an engine failure caused by FSP or NOT, is still an emergency, and worthy of declaring one. I thought I couldn't in this case because I
thought the failure was not caused by FSP, but it WAS, without me knowing, do you see the confusion it can cause?
I am not attacking your program at all here Dan so don't take this the wrong way, but in most of these cases I don't know which software is causing
the emergency; the FO didn't say so, and I just end up getting penalised either way.
out. I had NO WORD from the first officer and so I didn't declare an emergency. I thought that Level D's own emergency emulator must have caused the
failure therefore.
BUT when I landed, I was penalised for not declaring an emergency, and FSP said it had caused it! I didn't know that! As a result I really am asking
you Dan please if could make it allowed for people to declare an emergency in any situation that goes wrong, even if it is not caused by FSP. Me
thinking that the engine failure was caused by the level D software and not FSP caused me to be penalised for NOT declaring an emergency, but since I
had no knowing which software did cause it, it's just not fair to add that confusion.
I really would like to see it made possible to declare an emergency in any situation the pilot considers to be an ermergency. Nobody is going to
willingly declare a false emergency anyway, something must go wrong somehow for someone to declare an emergency.
The fact is, an engine failure caused by FSP or NOT, is still an emergency, and worthy of declaring one. I thought I couldn't in this case because I
thought the failure was not caused by FSP, but it WAS, without me knowing, do you see the confusion it can cause?
I am not attacking your program at all here Dan so don't take this the wrong way, but in most of these cases I don't know which software is causing
the emergency; the FO didn't say so, and I just end up getting penalised either way.