September 7, 201213 yr Dear all, I experienced some problems while descending into KSJC via the ROBIE3 arrival, I programmed the FMS to cross a specific waypoint on the arrival at 8000, LNAV and VNAV were engaged. The aircraft crossed this specific waypoint at a way higher altitude and a message showed up in the FMS "DESCENT PATH UNACHEIVABLE" so I ended up being too high to intercept the Localizer runway 30L, what could be causing the problem, need your help and advice please. Andrew Ayad
September 7, 201213 yr Try again with some screen shots of your progress, and there will be plenty of suggestions. Matt Cee
September 7, 201213 yr What weather did you use? Did you enter the expected winds in the FMC? Regards Johan Grauers
September 8, 201213 yr Was there a route discontinuity in the star? Vladimir Levkov / Владимир Левков Two miles of road can take you two miles.Two miles of runway can take you anywhere in the world
September 8, 201213 yr How accurately did you follow the STAR? Cheers, Richard Intel Core i7-7700K @ 4.2 GHz, 16 GB memory, 1 TB SSD, GTX 1080 Ti, 28" 4K display Win10-64, P3Dv5, PMDG 748 & 777, Milviz KA350i, ASP3D, vPilot, Navigraph, PFPX, ChasePlane, Orbx
September 8, 201213 yr Author There wasn't a route discountinuity in the STAR, I am using Active Sky 2012 and I did not enter the expected winds along my route. Andrew Ayad
September 8, 201213 yr Then you may have had a significant tailwind during descent, something the FMC would not calculate for (since you told it there would be no winds). This can put you off little at a time and if you do nothing to correct will eventually make the descent path unachivable. Regards Johan Grauers
Create an account or sign in to comment