April 28, 201313 yr Hi, I'm working on an RNAV approach for rwy 21 in LLET. The approach is like this: 7000ft @SAMAR, 3000ft @KITOR, 900ft @MIYAH and then visual for the runway. I wrote this in the LLET.txt (PMDG\SIDSTAR): APPROACHES APPROACH RNAV21 FIX SAMAR 7000FIX KITOR 3000 FIX MIYAH 900 RNW 21 ENDAPPROACHES In the FIXES section, I wrote: FIXES FIX GODAR LATLON N 29 30.35 E 34 55.86666 FIX HILIT LATLON N 29 28.48333 E 34 54.16666 FIX KITOR LATLON N 29 43.38333 E 34 59.9 FIX LOT LATLON N 29 36.485 E 34 58.56833 FIX RODED LATLON N 29 34.48333 E 34 56.83333 FIX RW03 LATLON N 29 33.29082 E 34 57.39516 FIX SAMAR LATLON N 29 49.33332 E 35 1.06668 FIX SHAKI LATLON N 29 31.66666 E 34 54.38333 FIX YAMAD LATLON N 29 31.43333 E 34 56.38333 FIX MIYAH LATLON N 29 29.60888 E 34 34.98444 ENDFIXES And still, when I add the approach, it shows the waypoint MIYAH 20 nm away, somewhere near Taba, Egypt: The waypoint MIYAH is located, acording to the chart, at: 29°36’32 ” N 034 °59’04 ” E Which is translated to "N 29 29.60888 E 34 34.98444", as in the FIXES section. Any help would be very appreciated! Regards, Liam Liam K
April 28, 201313 yr liamkosh, on 28 Apr 2013 - 11:41 PM, said: The waypoint MIYAH is located, acording to the chart, at: 29°36’32 ” N 034 °59’04 ” E Which is translated to "N 29 29.60888 E 34 34.98444", as in the FIXES section. Any help would be very appreciated! It's not translated correctly obviously. correct way to do this: you practically need to transfer from 60 units for one minute (seconds) to 100000 units for one minute (decimal minute). So just take this proportion: 32:60=x:100000 so x=(3200000)/60 x=53333 So correct answer would be 29°36’32 ” N equals 29°36.53333'N Same for longitude: 4:60=x:100000 X=400000/60 x=6666 So 034°59’04 ” E equals 034°59.06666' E At the end, just make a quick check to make sure calculated number makes sense: 32" is a little over half of minute, and that perfectly match 53333 which is a little over half when you compare with 100000. Btw, when you are converting from low sense to high sense (seconds to decimal minutes), it's ridiculous to go with 10000 units per minute precision. That's just like to try to resize photo from 400x400pix to 20000x20000pix - no quality gain at all. As with decimal system you cannot use base of 60, you can choose between 10, 100, 1000 and so on; base 10 is lower quality (precision) than base 60 so It's perfectly reasonable to go with 100 units per minute. [color=#a9a9a9][size=1][size=4][img]http://forum.avsim.net/public/style_images/flags/rs.png[/img][/size] Lj. Prodanovic[/size][/color]
April 28, 201313 yr Author It's not translated correctly obviously. correct way to do this: you practically need to transfer from 60 units for one minute (seconds) to 100000 units for one minute (decimal minute). So just take this proportion: 32:60=x:100000 so x=(3200000)/60 x=53333 So correct answer would be 29°36’32 ” N equals 29°36.53333'N Same for longitude: 4:60=x:100000 X=400000/60 x=6666 So 034°59’04 ” E equals 034°59.06666' E At the end, just make a quick check to make sure calculated number makes sense: 32" is a little over half of minute, and that perfectly match 53333 which is a little over half when you compare with 100000. Btw, when you are converting from low sense to high sense (seconds to decimal minutes), it's ridiculous to go with 10000 units per minute precision. That's just like to try to resize photo from 400x400pix to 20000x20000pix - no quality gain at all. It's perfectly reasonable to go with 100 units per minute. Oh you're right lol. Thank you very much! Liam K
Create an account or sign in to comment