JQ Problem

[Craig Lindsay]

I flew out of yssy on wed morning.It was the first flight of the morning up to cooly on JQ400 .Every one was on board and the pilot announced there was a problem with something in the cockpit and they had an engineer looking at it.I was just curious about what the problem was.It took about 20 minutes to fix.

[Daniel M]

from what my sources tell me, the flux capacitor was running low on jiggawatts and needed a full reboot, hence the 20 minute timeframe.

Further to what Daniel has said, occasionally the jiggawatt generator in the screens need's to be emptied out as well. It accumulates liquid in it sometimes that's needed to run the screen's and can be trapped. Resetting them does the trick.

We had problems like this over in Europe on the A320's for one of my past employers.

Cheers

Chris

[Adam P.]

Can confirm it was the Jiggawatt Generator.

[Stephen Brown]

The problem was probably something in the cockpit

[Gabriel S.]

20 minutes? Sounds about right. Note the correct spelling, "gigawatt generator".

[Philip Argy]

I think they were just having trouble bridging the credibility gap ...

[David Ramsay]

Note the correct spelling, "gigawatt generator".

That was actually the problem, it had spelt itself incorrectly and they needed a 20 minute spell to fix it.

[Kelvin R]

Is that because the A320 FMC runs Windows? Hence why the reboot takes so long? If only they moved to a Mac OS the reboot would take half the time

[chrisb]

Originally Posted by Kelvin R

Is that because the A320 FMC runs Windows? Hence why the reboot takes so long? If only they moved to a Mac OS the reboot would take half the time

Yes, but once the FMC was on MacOS, you'd no longer be able to program in a flight route - It would tell you the best way to get to the destination and if you don't like it then too bad!