Please refer to the attached ILS approach for 25L at EBBR.

 

When I selected this and it loaded the farthest waypoint from the runway that loaded was "D5 BUB".  I am using Navigraph AIRAC Cycle 1303 and I know that the MD11 FMS is only loading what is included in the AIRAC 1303 25L ILS approach.

 

I know how to add standard waypoints into the flight plan, but how do you add something like D8.9 IBL or D8.1 BUB or D13.9 IBL?

 

Regards,

 

Rod Storer

You go to your last way point ( or any waypoint ) select the Left  Key  then  on the other page you need to put the name example Flora is D112.05 and put it in the { next waypoint } and activate it  , every thing els after Flora will be calculated by the FMC  all the ILS/DME will be there you dont need to do any thing

 

hop this helps you can always direct it by this method if you choose so But be aware to erase the next waypoint after you entered the new one other wise the Aircraft will go back to Original PLN after reaching the new way point

Oh ya several reasons One it could be that you are close enough to the D5 and thats all you see,,   2 sometimes if there are very close to each other you will not see all of them

 

I will not worry about this very much as long as the Aircraft is doing what it supose to do

 

but this method is useful for a Miss approch and you want to go to a specific waypoint or ATC asks you to go direct to a waypoint

I know how to add "FLO" (Flora) as a waypoint.

 

I am asking how do you add something like "D8.1 BUD" and "D13.9 IBL" as a waypoint since "D8.1 BUD" and "D13.9 IBL" are shown on the ILS approach for 25L, but are not included in the 1303 AIRAC information for this approach!

 

I am asking how do you add something like "D8.1 BUD" and "D13.9 IBL" as a waypoint since "D8.1 BUD" and "D13.9 IBL" are shown on the ILS approach for 25L, but are not included in the 1303 AIRAC information for this approach!

 

They "are."

 

Those are DME points.  You just glance at your DME information, seen here at the top left of the PFD, right under the FMA:

Thanks for the response Kyle, but the PFD picture you posted is not from the MD11, it looks like it is the 737.

 

Also my question is how do you add (insert) something like "D13.9 IBL" into the flight plan because when the FMS loads the ILS approach for 25L "D8.1 BUD" and "D13.9 IBL" are not included as waypoints in the flight plan displayed on the FLT PLN page on the FMS in the MD11.

Thanks for the response Kyle, but the PFD picture you posted is not from the MD11, it looks like it is the 737.

 

Also my question is how do you add (insert) something like "D13.9 IBL" into the flight plan because when the FMS loads the ILS approach for 25L "D8.1 BUD" and "D13.9 IBL" are not included as waypoints in the flight plan displayed on the FLT PLN page on the FMS in the MD11.

 

It appears you're right that I used the wrong picture, but the concept is the same.  You get the DME information from the displays, not from the navdata.  Navdata is for named waypoints, and occasionally pseudo-waypoints.  Those DME reference markers aren't really waypoints at all, so they're not going to come up.

 

To answer your question, though, I believe that with the MD-11 you'd have to create a new waypoint on the REF page using Lat/Lon.

Why would you need these waypoints for ILS anyway?

 

I know how to add standard waypoints into the flight plan, but how do you add something like D8.9 IBL or D8.1 BUB or D13.9 IBL?

Rod,

 

easy, you need to add a PDB Waypoint (Place/Bearing/Distance), check the FMS manual on page FMS.100.3 .

 

So in this case you would enter for example BUB/250/8.1 to enter the FAF. Then add the 3000ft altitude restriction via a normal VERT REV.

 

Cheers,

Markus

Why would you need these waypoints for ILS anyway?

Very good Question  if the Aircraft is doing every thing els Right , and i know it does because mine does

 

But i think he was Looking for the answer that  MBURKHARD  Gave           witch is super

Why would you need these waypoints for ILS anyway?

 

Because the first waypoint when you select this approach that is actually entered is D5BUB and I want to start my straight in approach farther out than 5.5 nm.

 

Rod,

 

easy, you need to add a PDB Waypoint (Place/Bearing/Distance), check the FMS manual on page FMS.100.3 .

 

So in this case you would enter for example BUB/250/8.1 to enter the FAF. Then add the 3000ft altitude restriction via a normal VERT REV.

 

Cheers,

Markus

 

Thanks Markus, that is the answer that I was looking for!

I am Happy you got your answer ,, and it is also interesting for me too , i will give it a shot and see how this works out

 

But just heads up this will not work online with ATC they will not let you descend  that farther out  to the Altitude you want

 

But with no ATC sure this will not be a problem

 

Happy Landings update if you can on how well did it work

Just an Option what you are looking for is a Product call     EFB   this will give you exactly what you are looking for and exactly where you are ,,   above or at the G/S

 

I highly recommend this Product but it is Payware

 

good luck

 

Then add the 3000ft altitude restriction via a normal VERT REV.

 

I don't see any difference betweeen entering a speed and altitude restriction on either the ACT F-PLN page or VERT REV page. Is there any difference?

 

Thank you

Michael Cubine

This is also a result of different naming conventions between the navdata providers. Navigraph uses Jeppesen and Aerosoft uses Lido.

Here is the way it looks in NavdataPro:


APPROACH ILS25L FIX IBL58 AT 2000 FIX OBNB AT 1410 SPEED 160 RNW 25L TRK 250 UNTIL 700 HDG 119 INTERCEPT RADIAL 085 TO FIX FLO FIX FLO AT 4500
TRANSITION ANT FIX ANT SPEED 220 FIX OVERFLY BUN FIX IBL11 AT OR ABOVE 2000
TRANSITION FLO FIX FLO SPEED 220 FIX FLO81 FIX IBL14 AT OR ABOVE 3000 FIX IBL89 AT OR ABOVE 3000
TRANSITION KERKY FIX KERKY SPEED 220 FIX OVERFLY BUN FIX IBL11 AT OR ABOVE 2000

The difference here is, that the waypoints use the DME ident + distance as identifier.

Jeppesen on the other hand is using a naming convention based on their function. CI25l means "Final Approach Course Fix ILS 25L".

For pilots the DME Distance convention may be the better one, as it enhances the situational awarenes regarding the geographical position of that waypoint.

For database editors the naming convention based on function may be better, because you can connect them to their database role and easily use it on multiple approaches without having to figure out the dme distance name every time you want to use the same waypoint on a different approach.

Here as example ILS25L with FLO transition.

Jeppesen:

D070P = D13.9 IBL

D070K = D8.9 IBL

CI25L = D5.8 IBL

OM25L = D3 IBL


Lido:

IBL14

IBL89

IBL58

OBNB (OB NDB)


In the end, there is no need to add any waypoints, as all of them are there already. You may just forgot to select the FLO transiton.


Jan-Paul

But just heads up this will not work online with ATC they will not let you descend  that farther out  to the Altitude you want

Why should this not work with online ATC? My answer is conforming to the published approach, ATC will always let you fly that.

 

Markus

Because the first waypoint when you select this approach that is actually entered is D5BUB and I want to start my straight in approach farther out than 5.5 nm.

 

 

Thanks Markus, that is the answer that I was looking for!

Because he is saying he wants to start his descend Farther out then what is his FMC  giving him

 

Isnt this what he wants to do ??

 

any way this is what i understood