Ok I have read and watched tutorials, I grasp and understand most of the FMC stuff, however I fail to plot my own routes as I am not entirely sure of what waypoints etc to use. Basically I have tried to plot the following route:

 

EGAA (Aldergrove), RWY25 To EGCC (Manchester) RWY05L

 

I wanted to go VIA (LISBO to MIRSI) or (DCT/Direct to RW05L) but there are discons with the LEGS page. Basically I need someone to give me a step by step very briefly from the RTE/DEP-ARR Pages to PERF INIT, as I understand everything before and after. Any help is greatly appreaciated as it will guide me towards plotting other routes including LSZH to LOWI (RWY08) :Hypnotized:

In order to clear the disco's, you have to us elect a waypoint. Let's say you have x|>disco|>y. You have to line select waypoint y, and then once it's in the scratchpad, you click on the line select key next to where it says disco. Finally, you press execute. As for a good guide on the steps to programming the fmc from start to finish, you can have a look at the tutorials included in the pmdg folder, under the start button in windows.

In order to clear the disco's, you have to us elect a waypoint. Let's say you have x|>disco|>y. You have to line select waypoint y, and then once it's in the scratchpad, you click on the line select key next to where it says disco. Finally, you press execute. As for a good guide on the steps to programming the fmc from start to finish, you can have a look at the tutorials included in the pmdg folder, under the start button in windows.

 

Not sure which guide is it in my pmdg folder? I have looked at a few off them and nothing explains step by step, there is a tutorial for flying from EGKK to EHAM, but thats kind of too much.

Don't be shy, forum rules require you to post your real name! Thanks.

 

This might get you going. Its very basic. It should work with 7,8 or 900. You need to read up on preflighting the FMC for flight though.

 

This does not follow any tutorial.

 

 

Push........RTE

Type .......EGAA in the scratch pad

Push LSK 1L ....... Moves EGAA to Origin airport

Type .......EGCC in the scratch pad

Push LSK 1R .....Moves EGCC to Dest (destination airport)

Type.........25 (RWY 25)

Push LSK 3L .....Moves 25 to active runway for takeoff

Push .........DEP/APP

Push LSK (Line Select Key on FMC) 1L …….. DEP (SID’s for EGAA)

Push LSK 1L ………LISBO (SID)

Push …...Activate

Push ….....Execute

Push ..............DEP/APP

Push LSK 2R……… EGCC ARR

Push Next page................... two times

Push LSK 1L …………MIRS1b (EGCC STAR)

Push LSK 5R……..ILS05L ( EGCC )

Push LSK 4R……MERCI (Transition to ILS App)

Push….Execute

Push LEGS

Push LSK 4L….LYNAS (to the scratch pad)

Push LSK 3L…. LYNAS is moved and end’s the route discontinuity

Push…….Execute

 

PERF INIT page

Cost Index ………….. 50

Reserves ………… 5.0 (5,000 US LBS)

Zero Fuel Weight ……. 115.0 (115,000 US LBS)

Fuel………..11.0 (11,000 US LBS)

GW WT/CRZ CG…… 126,000 US LBS (FMC will calculate by adding the ZFW and Fuel together)

Trip/CRZ Alt…………..Anything less than Trip

Push ……….Execute

Push ………..N1 Limit and continue

 

JOhn Floyd

Hi my real name is chris, I will sure give your brief steps a try in a minute or two, let you know how I fare.

Don't be shy, forum rules require you to post your real name! Thanks.

 

This might get you going. Its very basic. It should work with 7,8 or 900. You need to read up on preflighting the FMC for flight though.

 

This does not follow any tutorial.

 

 

Push........RTE

Type .......EGAA in the scratch pad

Push LSK 1L ....... Moves EGAA to Origin airport

Type .......EGCC in the scratch pad

Push LSK 1R .....Moves EGCC to Dest (destination airport)

Type.........25 (RWY 25)

Push LSK 3L .....Moves 25 to active runway for takeoff

Push .........DEP/APP

Push LSK (Line Select Key on FMC) 1L …….. DEP (SID’s for EGAA)

Push LSK 1L ………LISBO (SID)

Push …...Activate

Push ….....Execute

Push ..............DEP/APP

Push LSK 2R……… EGCC ARR

Push Next page................... two times

Push LSK 1L …………MIRS1b (EGCC STAR)

Push LSK 5R……..ILS05L ( EGCC )

Push LSK 4R……MERCI (Transition to ILS App)

Push….Execute

Push LEGS

Push LSK 4L….LYNAS (to the scratch pad)

Push LSK 3L…. LYNAS is moved and end’s the route discontinuity

Push…….Execute

 

PERF INIT page

Cost Index ………….. 50

Reserves ………… 5.0 (5,000 US LBS)

Zero Fuel Weight ……. 115.0 (115,000 US LBS)

Fuel………..11.0 (11,000 US LBS)

GW WT/CRZ CG…… 126,000 US LBS (FMC will calculate by adding the ZFW and Fuel together)

Trip/CRZ Alt…………..Anything less than Trip

Push ……….Execute

Push ………..N1 Limit and continue

 

JOhn Floyd

 

Thanks, I followed this step by step guide and, there is a gap that needs bridging from "MIRSI" to IOM10-4" on page 2 of the LEGS page, basically need the last waypoint sector so its a complete route. thanks for help so far.

 

EDIT: The IOM10-4 waypoint couldnt be selected for some reason but I used the CI05L waypoint and this works fine, it leads onto the runway approach, but would have liked a little more room for the approach. Any other help is appreciated.

A complete route doesn't mean a complete (unbroken) magenta line from departure to destination.

Very rarely will you have a route that doesn't have some break in the line. Don't be a slave to the magenta line (or any of the automation). Understand what the automation is trying to tell you.

 

Those last waypoints seem to be waypoints onto an approach. An air traffic controller would vector you off of your route, onto the approach, so you'd leave the comfy magenta line, and get vectored (via HDG SEL) onto the next segment of the line (which is probably an ILS, but may be another type of navaid, where you'd use VOR/LOC or APP, instead of LNAV).

Thanks, I followed this step by step guide and, there is a gap that needs bridging from "MIRSI" to IOM10-4" on page 2 of the LEGS page, basically need the last waypoint sector so its a complete route. thanks for help so far.

 

You still need to sign your post.

 

The gap from MIRSI to IOM10-4 is a VECTOR leg as it shows on the LEGS page. This particular STAR just does it that way. Actually, there is no route discontinuity on the LEGS page. The gap can only be seen on the ND. In the real world, ATC will begin giving radar vectors to the ILS05 final approach course.

 

 

All this information is in the manuals and tutorials.......

Thanks guys I know there is just so much to learn in the manuals, dont know where to begin really. I guess I was after a unbroken magenta line but now know that I need to make contact with ATC for approach to final.

The manuals are a lot, but one's called Introduction. That's generally a good place to start .

The manuals are a lot, but one's called Introduction. That's generally a good place to start .

 

I will give that a read, although I think I may have already, if thats the one with the test EGKK to EHAM flight. Will read again if so. I hope to learn alot here, so thanks its already been helpful to me.

You still need to sign your post.

 

The gap from MIRSI to IOM10-4 is a VECTOR leg as it shows on the LEGS page. This particular STAR just does it that way. In the real world, ATC will begin giving radar vectors to the ILS05 final approach course.

 

All this information is in the manuals an tutorials.......

 

Real dumb question, but why leave a gap then continue. Why wouldn't it just end at MIRSI if the norm is to be vectored from there?

Real dumb question, but why leave a gap then continue. Why wouldn't it just end at MIRSI if the norm is to be vectored from there?

 

I think you’re asking, why do you need to load the ILS05 approach into the LEGS page. Standard procedure in the NG is to fly in the EFIS control panel Map mode and load an available approach procedure into the FMC LEGS page so that it is displayed on the ND (Navigation Display or "moving map"). You will hardly ever have an instance where the flight crew uses only raw data (EFIS control panel APP) to fly the approach in a NG.

I think you’re asking, why do you need to load the ILS05 approach into the LEGS page. Standard procedure in the NG is to fly in the EFIS control panel Map mode and load an available approach procedure into the FMC LEGS page so that it is displayed on the ND (Navigation Display or "moving map"). You will hardly ever have an instance where the flight crew uses only raw data (EFIS control panel APP) to fly the approach in a NG.

 

Thank you John.

A complete route doesn't mean a complete (unbroken) magenta line from departure to destination.

Very rarely will you have a route that doesn't have some break in the line.

 

Actually, in Europe, most of the time it is unbroken... I fly around the Continent mostly and, apart from Munich maybe, have yet to find an airport where I would not be able to have an unbroken line down to landing.