July 31, 201213 yr Also remember that for 20 Euro, you can buy enough credits for an entire year's worth of navdata. This means you can download for any aircraft, all year. This is what I do and is most economical, IMO. Adam Hill
July 31, 201213 yr Ryan, I was flying last night and noticed the improvements. How feasible is it to incorporate next-gen approaches, such as the GPS ones that Alaska Airlines has been testing. Thanks! LUIS LINARES Processor: Intel Core i9 6700K 9900K (5.0 GHz Turbo) Eight Core; CPU Cooling: NXXT Kraken X62 280mm CPU Liquid Cooler; System Memory: 64GB Corsair DDR4 SDRAM @ 3200 MHz, RGB; Graphics Processor: 11GB Nvidia GeForce RTX 2080 Ti, GDDR6, Primary Drive: 2TB Samsung 850 Pro Solid State Drive (SSD)
July 31, 201213 yr Ryan, I was flying last night and noticed the improvements. How feasible is it to incorporate next-gen approaches, such as the GPS ones that Alaska Airlines has been testing. Thanks! I'm guessing the main problem with those would be getting Alaska to give you the required data, not the actual programming itself. John-Alan Pascoe
July 31, 201213 yr Southwest. Oh Ryan, where have you been thundering around to now? I've been on 6 Southwest flights and 5 American flights this month. We really outta get some close seats and talk 777. :P Nathan Cupps, VZAB Instructor
August 2, 201213 yr Doesn't it beg the question as to why the aircraft use the raw data? Must be something navdata does that's pretty good for the aircraft makers. Never seen any raw data or what the navdata output looks like so I can't say. I know this is a bit late, but I just wanted to clarify: I believe the "raw data" is already parsed to ARINC-424 standard, and this standard is used by every aircraft manufacturer. Thus no need to parse it for specific aircraft. Company procedures may need to be implemented, but that all still falls under the ARINC-424 specification for communication with the flight computers. Hope that answers that. Frank Grivel Intel i5-2500K CPU, 8GB DDR3-1600 RAM (9-9-9-23), 1TB HDD, Nvidia 560Ti GTX, 700W PSU
August 3, 201213 yr Hey fellas, I don't think this is too much off topic... can anyone explan to me, why, when I get the latest updated navigraph data that the SIDS and STARS don't always read exactly the same as in the CDU? eg a STAR maybe BISET1D but when choosing the STAR in the CDU it may read BISEN1D or NISET1D these are not real STARS just an example...I'm fairly new to SIDS and STARS and so this is something that confuses my small mind! Help as always, appreciated, cheers guys. Well I don't know about the examples you've given here, but what I have seen is that the name displayed in the CDU is shorter, presumably due to a limitation in the number of characters that can be displayed in that position. John-Alan Pascoe
August 3, 201213 yr Ya, ASA is testing nextgen approaches into SEA (works for all approaches except those from the east) and JBU is testing them at JFK. Eric
August 23, 201213 yr Author Commercial Member No further changes yet. Ryan MaziarzFor fastest support, please submit a ticket at http://support.precisionmanuals.com
August 23, 201213 yr Doubt Ryan can answer that. No way he can know which DP/STAR's have changed throughout the world. Eric
August 24, 201213 yr I heard that with 1209 some European destinations have major changes (ESSA), and that alphanumeric routes can now be used (such as in Africa, B23F, instead of B23)? Frank Grivel Intel i5-2500K CPU, 8GB DDR3-1600 RAM (9-9-9-23), 1TB HDD, Nvidia 560Ti GTX, 700W PSU
August 24, 201213 yr ESSA had a major change indeed. For more info look here: http://forum.vatsim-scandinavia.org/index.php?/topic/829-swedish-airspace-changes-from-23-august/ Marc
Create an account or sign in to comment