I am trying to fathom the LOWI runway 8 RNAV approach with the 738 (PMDG). Simbrief gave me the EDDN to LOWI plan below. Prior to descent I selected the RNAV Y approach with a transition at ELMEM. However, each time I try the approach, the plane turns in midway from RTT to ELMEM  towards WI813 and starts a very steep descent to landing. Is this the correct procedure as I want to start descent from 13000ft at ELMEM? Sorry, new to heavies. Would appreciate any help or pointers on vids/tutorials on this type of approach.

 

 

 

 

 

 

 

Edited March 18, 20251 yr by snaparaz

I'm no expert, but the current simbrief flightplan has you arriving well east of LOWI, I clicked on the simbrief "Suggested routes - Show all", to see if there was a route that went to the west side, and this route seemed to fit the bill, 

BOLS1C BOLSI Y167 AKANU XEBIX XEBI1B

XEB1B takes you on a track of 148 degrees to ELMEM, which enables you to start the approach directly. If ATC insisted you went to RTT east of the field, routing RTT to ELMEM direct (effectively the RTT1B STAR), would have you over ELMEM, but you'd need to do a course reversal in the ELMEM hold to be pointing the right way for the approach.

Just my best guess?

 

Thanks for that! I tried a few times with the eastern arrival, but even with a 180 at ELMEM, the approach is deadly. Thanks for the tip. The XEBI1B works fine.

Yep 180 at ELMEM is way too high, final descent starts 4 miles after ELMEM from 13,000 ft, just change the altitude constraint in the FMC from FL130A (FL130 or above) to 13000ft. Use an altitude rather than FL for terrain separation.  In my FMC using the PMDG 737 700, it showed 280/FL130A (280kts FL130 or above at ELMEM), I changed it to 250/13000, this means the VNAV will recalculate the descent profile to cross ELMEM at 250kts, and 13,000, much better set up for the 08Y approach.

 

08 LOWI visual approach was in pmdg tutorial for FSX. Very interesting and chalenging. There you had to be at FL130 at RTT, already slow, flaps extended and follow the visual app chart.