I stand corrected, what's it like to fly the ERJ-140/145?

Autothrust Blue said:
Is RESET, ALTN not a part of the after start there?
Click to expand...
It is, but the FADEC isn't always on the "A" channel. Remember, the system switches fadec's for each start, and then the captain cycles the fadec's after the start as well. What I was saying is when a CPT switches all the FADEC's to read "A" no matter how many times they've cycled the fadec(s).
 
KHanson said:
It is, but the FADEC isn't always on the "A" channel. Remember, the system switches fadec's for each start, and then the captain cycles the fadec's after the start as well. What I was saying is when a CPT switches all the FADEC's to read "A" no matter how many times they've cycled the fadec(s).
Click to expand...
That's just silly. Two equivalent boxes.

Things related to engine control are "don't touch it more than you have to" items in my book, but I am weird.
 
Polar742 said:
Not sure, but we had the procedure from the first jet (mid 99).

IIRC, it had to do with clearing the RAM on the FADECS
Click to expand...

The procedure was developed by Embraer, Rolls Royce and ExpressJet (at the time, Continental Express) when they were experiencing an average of one uncommaded engine shutdown per week. It was determined that the FADECs were getting bogged down with miscellaneous, unneeded codes during each engine start. Like your computer when the hard drive gets full, it bogged down the FADECs causing them to eventually shutdown, which shuts down the engine. It was found that the COEX crews were just alternating the FADECs (per EMB procedures) after engine start. Going to RESET cleared the codes and things were fine after that. It was procedure that the FADECs were alternated in such a way that the A FADEC had control going from a HUB (Away) and the B FADEC had control going into a hub (Back). They switched on their own during each start, but that's how XJT did it.
 
ERfly said:
The procedure was developed by Embraer, Rolls Royce and ExpressJet (at the time, Continental Express) when they were experiencing an average of one uncommaded engine shutdown per week. It was determined that the FADECs were getting bogged down with miscellaneous, unneeded codes during each engine start. Like your computer when the hard drive gets full, it bogged down the FADECs causing them to eventually shutdown, which shuts down the engine. It was found that the COEX crews were just alternating the FADECs (per EMB procedures) after engine start. Going to RESET cleared the codes and things were fine after that. It was procedure that the FADECs were alternated in such a way that the A FADEC had control going from a HUB (Away) and the B FADEC had control going into a hub (Back). They switched on their own during each start, but that's how XJT did it.
Click to expand...

When I was doing IOE, I had one shut itself down, alternate the FADEC and relight before we realized what was going on. We felt the airplane start to yaw, then saw the N1 spooling back up through about 70%, both ignitors were on, and the FADEC had switched on its own. Best we could figure, the A box took a crap and shut the engine down, and the B box saw it happening, relit the engine and kept on chugging.

When we landed we alternated the FADEC back to the A box and...nothing happened, the engine kept running quite happily.

Gremlins.
 
You must log in or register to reply here.
Back
Top