FlyNET/FSA induced failures - REPORT THEM HERE

Check here to keep abreast of FSAirlines updates.

Moderators: Guru's, The Ministry

Re: FlyNET/FSA induced failures - REPORT THEM HERE

Postby simondix » Wed Oct 14, 2009 7:39 pm

Cheers for that.
Simon

Image
simondix
VC10
VC10
 
Posts: 563
Joined: Fri Aug 10, 2007 8:54 am
Location: Redditch, Worcestershire, UK

Re: FlyNET/FSA induced failures - REPORT THEM HERE

Postby RAF_Quantum » Fri Oct 16, 2009 10:33 am

Hi,

In circumstances like this, resetting/aborting the sim first will re-instate your fuel to that at start of flight so if the client is still running it will show this message as the sim is attempting to alter the fuel state. Best course of action is to pause the sim, shutdown the client, reset flight and start again. Simon if you have sim messages turned on in the client options then you will know for sure if it is client induced or pilot/aircraft induced engine failures, I don't think the client gives a double engine failure. Konny turned off the annoying climb/cruise/descend messages a long tim ago so it is no imposition having them turned on again. You should only see taxi/take-off/landed/on blocks for a normal flight.

Regards

John
Image
User avatar
RAF_Quantum
The Gurus
 
Posts: 2884
Joined: Sun Jul 04, 2004 11:36 pm
Location: NE Lincolnshire UK

Re: FlyNET/FSA induced failures - REPORT THEM HERE

Postby NigelC » Sun Jan 24, 2010 2:43 pm

No 1 Engine fire en-route Thessaloniki to Birmingham (just reached cruise at FL310), had the FSA banner message.

Diverted to Podgorica (LYPG) in Serbia. G-AZMF

N
Image
NigelC
Victor
Victor
 
Posts: 227
Joined: Tue Oct 02, 2007 11:20 am
Location: Hednesford, Staffordshire, UK

Re: FlyNET/FSA induced failures - REPORT THEM HERE

Postby stegs » Thu Aug 19, 2010 9:42 pm

Had No.3 engine on Viscount G-AZNC shut down on IOM to Teesside flight. I restarted it and had no further trouble. As I could see nothing wrong
with the aircraft I'm assuming it was a Flynet thing although as I have never had a Flynet induced failure before I'm not sure how you
can tell. The flight report states everything was OK.
How do you know when you've had a Flynet induced failure?

Steve

EDIT :
Not Flynet. I've just flown the Viscount and No. 3 engine just shuts down when it reaches the cruising altitude I've got set
in FSNavigator. I'll investigate further
Image
stegs
Lightning
Lightning
 
Posts: 279
Joined: Fri Nov 10, 2006 11:33 pm
Location: Darlington UK

Re: FlyNET/FSA induced failures - REPORT THEM HERE

Postby DaveB » Fri Aug 20, 2010 9:35 am

Hi Steve :hello:

If FSA caused the engine failure, you'd not be able to restart it mate.. it remains dead until the flight has ended and the client has been shutdown. However, when you rebook the same aircraft, the faulty engine is automatically fixed so you can continue on your way. To the best of my limited memory, even though you may experience a failure.. the failure isn't reported by FSA on the Pirep. The only visual warning you get, besides the engine instruments, is a green/red text line at the top of the screen (like the taxi/takeoff/landed notification).
Again, if memory serves me right, I've only ever had engine failures on the outers.. usually No.4 on both the Viscount and Vanguard but it's been a long time since I had one and could be mistaken. The last failures I remember having under FSA both occured at touchdown and were both engine fires!! Not had one at any other point in FSA whereas under FlyNET.. they happened when they happened. Last one I had was funny.. FSA reported a main gear failure (again at touch down) and I was in a Rapide! :lol:

ATB

DaveB B)smk
ImageImage
I'm learnin' to fly.... but I aint got wings!!
User avatar
DaveB
The Ministry
 
Posts: 21680
Joined: Thu Jun 17, 2004 8:46 pm
Location: Reading, Berkshire, UK

Previous

Return to FSAirlines info

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest