Charly04 5 Posted December 17, 2019 Share Posted December 17, 2019 On my flight from BOS to MUC the MCDU displays a "H" at the beginning of the coordinates. Should'nt there be a "N" in front? Best regards Charly Please login to display this image. Please login to display this image. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted December 17, 2019 Deputy Sheriffs Share Posted December 17, 2019 Yes, there should. Did you load the flight plan from .flp file? If so, could you please post that file here so we can have a look. Thanks Link to comment Share on other sites More sharing options...
ln-asm 1 Posted December 21, 2019 Share Posted December 21, 2019 No, not necessarily. Depends on the coordinates entered, as you have half degree coordinates as well, which you have used here. 55N020W = 5520N (ARINC 424) 5530N02000W = H5520 http://code7700.com/arinc_424_shorthand.htm Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted December 27, 2019 Deputy Sheriffs Share Posted December 27, 2019 Interesting, even I learn something new everyday from the product I develop. Thanks for the answer In-asm. Link to comment Share on other sites More sharing options...
Deputy Sheriffs The Dude 6537 Posted December 27, 2019 Deputy Sheriffs Share Posted December 27, 2019 Be careful with half truths. The RW Thales does not use an 'H', atleast not when using Lido navdata. Link to comment Share on other sites More sharing options...
ln-asm 1 Posted December 28, 2019 Share Posted December 28, 2019 17 hours ago, Frank Docter said: Be careful with half truths. The RW Thales does not use an 'H', atleast not when using Lido navdata. Sorry, looks like you might be right after reading some NAT bulletins etc. The link I posted seems to be based on a data provider who has changed from the ARINC 424 format but not mentioning that at all. It looks like the default ARINC 424 is actually N5530 for half degree coordinates, but because of so many pilot errors they are strongly dis-encouraging everyone from using this format and instead change to something else, e.g H5530, which at least Navigraph's source has done already. Aerosoft I cannot speak for, as I don't use NavDataPro myself Please login to display this image. (NAT OPS Bulletin 2008_003) Checking e.g AIP Iceland ENR 1.3.1.2, you'll see: Due to the unresolved potential for FMC insertion errors: Aircraft navigation data shall NOT contain waypoints in the Reykjavik Control Area in the ARINC424 paragraph 7.2.5 format of "Nxxxx". If an aircraft operator or flight planning service has an operational need to populate data bases with half-degree waypoints in the Reykjavik Control Area, they are advised to use the alternate format "Hxxxx". So it looks like the default is actually N#### after all, but that some data providers have already changed this to e.g H#### Hopefully I got it right this time @Frank Docter Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted December 28, 2019 Deputy Sheriffs Share Posted December 28, 2019 Interesting you mentioned Navigraph using the H format. I just checked simbrief and they use it as well. So this "issue" is caused through the way SimBrief generates a route file for the Airbus with this H#### naming system. Our airbus reads the waypoint name and it's coordinates and names the waypoint with the name on the file. Here is attached a route file from Simbrief that uses the H#### naming system. KBOSEDDM01.flp Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.