Jump to content

EGLL LAM3A ILS 27R


Airbus339

Recommended Posts

Well, LAM3A is always the same ... coming from Frankfurt, Munich or Tokio.

However this is the flight plan

LTFE AKBUK N128 IMR UN128 PEREN UN133 EVIVI L863 OKANA UL863 RAVAK UY505 BEO UM749 TONDO UL610 BATTY UL608 LOGAN EGLL

Link to comment
Share on other sites

hi,

have maked a alternate and short route from EGGW (Luton) to EGLL ...

EGGW CLN7C LAM3A LAM EGLL

post-77582-0-59940900-1371483726_thumb.j

you can see ... if have used the STAR 'LAM3A' and the transition 'LAM' for the rwy 27R.

I cannot see any problem with this route ... see PIC

post-77582-0-60974100-1371483796_thumb.j

I will fly this route too

cu Juergen

Link to comment
Share on other sites

hi,

that's right ... maybe I made ​​a mistake when I select the TRANS in the MCDU1.

The aircraft actually flew as it shows the blue line (see pic) ... i will repeat this flight

post-77582-0-58392400-1371488273_thumb.j

cu Juergen

Link to comment
Share on other sites

hello,
I have since made ​​the flight again ... but there are two important events

1. could not find the transition LAM (ILS27R) ... then I have simply inserted the relevant WP's in the MCDU1.
The WP's are: LAM11 BNN15 BNN19 IRR10 and IRR75

post-77582-0-51898000-1371511598_thumb.j


2. from the WP 'LAM11' the airplane flew then to a another WP ... but with the same name 'BNN15' (see PIC)

post-77582-0-55214500-1371511646_thumb.j post-77582-0-00798300-1371511678_thumb.j

cu Juergen

Link to comment
Share on other sites

Looks like you're too high for that approach and the FMGS is calculating orbits to lose altitude.

TAGAS is way outside the London area (way outside ...). So it's just like Joshua stated already in his post #2: "Under Investigation."

BTW, the same approach with NavDataPro looks pretty similar to the OP's approach with NaviGraph.

Link to comment
Share on other sites

  • 1 month later...

Perhaps an AIRAC issue (using Navigraph AIRAC 1308) but it looks a lot different on my flight with the 321 today. I've attached a screenshot. The flightplan is OJAI TALMI J10S BGN UH1 PURLA UH1B SUVAS UL53 KAROL UL995 RDS UL609 MES UG18 GIKAS UN133 EVIVI L863 OKANA DCT TONDO UL610 BATTY UL608 LOGAN. Arrival is LAM3A, EGLL 27L via LAM.

post-71384-0-90625700-1376218191_thumb.p

Link to comment
Share on other sites

Perhaps an AIRAC issue (using Navigraph AIRAC 1308) but it looks a lot different on my flight with the 321 today. I've attached a screenshot. The flightplan is OJAI TALMI J10S BGN UH1 PURLA UH1B SUVAS UL53 KAROL UL995 RDS UL609 MES UG18 GIKAS UN133 EVIVI L863 OKANA DCT TONDO UL610 BATTY UL608 LOGAN. Arrival is LAM3A, EGLL 27L via LAM.

Hi,

Perhaps I should have stated it more clearly, It is solved in one of our internal test build, no problems there. In other words, in the next update, you should not see the same problem.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use