wagnerw wrote in Fri May 10, 2013 8:44 pm:How does it work in real live? Flightplan filed under Callsign and Flightnumber => Contact identifies itself => ATC tells Contact Squawk code and assigns it to flightplan?
In real life the aircraft type is required information in the flight plan. In the flightplan it is represented using ICAO DOC 8643 - Aircraft Type Designators, and if one is not available for the aircraft type (e.g. if it is a prototype or a rare aircraft) it will be written as "ZZZZ" in the aircraft type field and instead added in field 18 (other information) after a preceding "TYP/" tag.
wagnerw wrote:Do we really want to force everybody to file a flightplan, before he can fly at your airports? Or do we alternatively accept anything flightplan like be it per chat or voice. In the later more beginner friendly way, we could keep it more simple...
I would personally prefer if there at some point in the future will be a central flightplan database (accessible to anyone), and that filing a flightplan would not be mandatory unless required by e.g. a virtual airline or flight club (i.e. not required for any geographical area), and that they could be done in a simple way as in some places today (i.e. departure time, arrival time, route, cruise speed and cruise altitude) and as a full flight plan for the few who would wish to do that (would probably only be done by virtual airlines and a handful of others, and will require a "wizard" to help filling the form).
F-JJTH wrote in Sat May 11, 2013 11:15 am:In this screenshot I transmit sqwak -9999 from one aircraft (which is totally impossible in real world... so not realistic) and the other aircraft receive -9998 (which is certainly a bug) Also the first aircraft is transmitting sqwak -9999 even if the transponder is OFF or SBY... I need to talk with James about all of this.
Eum, the squak code for all the "legacy" modes (1, 2, 3A and 3C) are octal numbers (0-7). (See for example Aviation transponder interrogation modes at Wikipedia)