The fuel introduction depends on the engine model. From the Boeing FCOM, Oct 17 2015, Rev 17 :

 

For the GE CF6-80 engines, put FUEL CONTROL switch to RUN when N2 is at 20% or (if 20% N2 is not possible), at maximum motoring and a minimum of 15% N2.

 

For PW 4000 series engine, put FUEL CONTROL switch to RUN at maximum motoring and a minimum of 15% N2

 

FF767 engines type are PW.

 

Note : Maximum motoring occurs when N2 acceleration is less than 1% in approximately 5 seconds.

 

I don't have any problems when starting the engines and putting fuel between 15-17% N2. I f I wait until 25% N2 or Max motoring, I have an EGT peak to 653°C (amber) during the start then back to normal parameters.

 

And according to Boeing, you can start either left or right engine first, but always one at a time.

Also, make sure that the packs are OFF, and the EEC are ON.

 

IMHO, I won't recommend to follow the tutorial/check list inside the sim, as there are a lot of mistakes in it.

I would recommend you to follow the FCOM in the Amplified Procedures section.

 

Stephane

Hi Stephane,

 

this is also what I would expect. Usually the EGT will get higher the lower the N2 at fuel-on. We used to make bets about the "peak EGT" during engine starts, and my captains cheated by guessing low and then waiting for the N2 to get really high before adding fuel.

 

If you add fuel at a too low N2, the airflow is not sufficient, and the EGT will get too high (hot start). If you see the EGT rise too rapidly or threatening to exceed the maximum starting limit, just move the startlever back to OFF - this cuts fuel immediately and you can try a second time after the engine has spooled down again enough for the starter to re-engage and the starter waiting time between starts has expired.

 

The only disadvantages of waiting for N2 to increase well above the minimum are the starter time limit and the actual time it takes to start the engine (time is money in airline flying!).

 

Jan

Thanks so much Stephane. That was what I originally meant when I said if you leave it too long it'll cause the engine to overheat. In this case, anywhere after 25% N2.

 

While testing this the other day, I decided to have some fun and takeoff while having the left engine in the yellow zone... Single engine fire & driftdown safely to an alt... :ph34r:

Great thread... I'm really keeping an eye on the FF 767 from now on...  I miss my LevelD 767 soooo much...

 

Again, in almost all of the videos I have been able to watch on youtube, of approaches flown on the FF767, using coupled or autoland, the aircraft is coming well off to the right or to the left of the rw centerline with the FD cue perfectly aligned ?

 

 

right or to the left of the rw centerline

 

Jose,

 

I have had it come in on either side.  Don't know if it is wind (wasn't paying attention to that) or what, but always well on the pavement...

 

John

Thx John,

 

but it should, even in te presence of x-wind, aligned and crabbing or sidesliping... AFAIK...

 

On autoland, the aircrtaft is brought in crab, and bellow 200' starts a sideslip, upwind down a bit, aligning with the rw centerline...

As someone said above, sometimes it can have many causes. From what I've experienced, for example, I have the FMEE airport's scenery and the Reunion Zone Photo scenery. I also have the latest navdata from Aerosoft or Navigraph (I have both of them but installed only once at a time), for XPX, for the GNS, for the 767 and all other add ons.

What I've noticed is if you tune the ILS 110.3 in the aircraft with a course of 135° and let the aircraft follow the ILS until the DA, you will land to the right of the runway in the scenery.

I have looked at the local map in XPX and noticed that the Localizer signal was a few tenth degree to the right of the scenery runway. I don't know if the signal is related to XPX navdata or coded in the scenery.

Anyway, a workaround to this is to edit the ILS course inside XPX, add/substract a few tenth degree or one or two degree until the Localizer signal is perfectly aligned with the runway in the scenery. Don't forget to save the change you made.

I don't know if I am clear in my explanations, but I think that a lot of ILS problems that people are reporting (aircraft not following the ILS perfectly or drifting to the left/right of the runway) is due to the difference between the FMS or XPX Navdata and the sceneries.

 

Stephane 

Thx John,

 

but it should, even in te presence of x-wind, aligned and crabbing or sidesliping... AFAIK...

 

On autoland, the aircrtaft is brought in crab, and bellow 200' starts a sideslip, upwind down a bit, aligning with the rw centerline...

I'll have to check on my next flight if this is the case. I have been catching myself left or right of the runway on many occasions but had brushed it off to inexperience on my part. I use real weather, so there is pretty much always some amount of wind component. The majority of my flights in the FF767 have been in the Caribbean, so lots of visual approaches and few ILS.

I know someone suggested it might be due to improper scenery alignement with the ILS Loc, but I have seen it in more than one video, at different airports...

 

Looking fwd for your tests..

 

Another aspect I never liked about their 777 was the autoland, or rather, the absence of it when even the mildest crosswinds were present. The aircraft always failed to come to a stop on the rw.

 

The 767 is certainly certified for up to at least 15 knot x-wind components in autoland, so, I would like to see this working as well.

 

The only airliners I owned  that made perfect autolands under even above limits x-winds were Peter's A380, and the QPAC Airbus.

Hello 

 

I was a Level-D junkie and flying in 2d Panel was beautiful. Now with FF 767-300 got me jumping all over the place, I recommended to all Level-D fans. Its a beautiful bird all around, go get it!!!!

 

David G

i also did an autoland with the ff 767 and it pulled me to the right of the center line at eham, i had thought it was the wind or i had done something wrong, i will test some more airports myself.

i also did an autoland with the ff 767 and it pulled me to the right of the center line at eham, i had thought it was the wind or i had done something wrong, i will test some more airports myself.

tHX

Just landed at TIST ILS 10 with a 6 knot headwind without problem. Granted, I was hoping for a little crosswind as headwinds are easy. I'll try something else soon.

Just landed at TIST ILS 10 with a 6 knot headwind without problem. Granted, I was hoping for a little crosswind as headwinds are easy. I'll try something else soon.

 

You know that you can change the wind in X-Plane, right?

 

Before you do the autoland, check the alignment of the localizer centerline on the "local map" in X-Plane. I would estimate 20% of all ILS approaches not perfectly aligned, some due to bad nav-data, but most of those because scenery artists didn´t place the runways accurately.

 

A plane doing autoland has nothing but the localizer signal to guide it laterally. So if that one isn´t running straight down the runway, the plane isn´t going to land on the centerline.

 

Jan

You know that you can change the wind in X-Plane, right?

 

Before you do the autoland, check the alignment of the localizer centerline on the "local map" in X-Plane. I would estimate 20% of all ILS approaches not perfectly aligned, some due to bad nav-data, but most of those because scenery artists didn´t place the runways accurately.

 

A plane doing autoland has nothing but the localizer signal to guide it laterally. So if that one isn´t running straight down the runway, the plane isn´t going to land on the centerline.

 

Jan

Hi Jan,

 

Sorry for the misunderstanding. This was not an autoland. I was flying a regular flight and wanted to see if the plane would line up correctly on an ILS signal, which it did in this case. We're trying to figure out if the plane is incorrectly lining us up either side of the runway on approach.

 

20% is a relatively high number and could explain why some videos are showing this misalignment (as José noted). Or, it could be my bad piloting skills and too much workload on approach, to get it right. :smile: Now, if MCE can send me a reliable First Officer to help out on the workflow, I'll be a happy Captain again.

 

Maybe I should be moving onto something a bit smaller like....I don't know...a 737 maybe? :wink:  Yes, I know, I'll be patient...lol