omega95 wrote in Wed Jul 24, 2013 4:11 am:EDIT - Yeah, I'm looking at a 7233-4 form and see there's a LOT more than what applies to flight simulation.
It sure has more information than what's needed, yep. It seems that item 19 actually is not always transmitted even in real life (until needed). Most if the information in items 10 and 18 are just excess weight for our purposes and intents.
omega95 wrote:Btw, because you're working on this, is this going to be done for FlightGear? Maybe use a canvas form and broadcast the data on the mpserver?
For now I am only wrapping my head around it and trying to write it down in a way that would make it easier to read in on than going through the real documentation. The base I am building the wiki page on is bits and pieces of ICAO Doc 4444 - Procedures for Air Navigation Services - Air Traffic Management (PANS-ATM) which contains a lot of information on other things.
In other words, no I'm not currently working at getting this into FlightGear. Only document things now that maybe (hopefully?) can be used later on.
At some point in the future, as I have mentioned before (
here and
here), I would love to see a central non-mandatory flight plan repository open for all to file to and to look into (not only traffic controllers), both for the original flight plan and current flight status, and that the traffic controllers can update while a flight is en route, preferably with a few levels of complexity when filing the flight plan, say for example these three levels:
- Callsign, type of flight and aircraft, origin and time, destination and time, flight level and cruise speed;
- same as 1. but also with route; and
- full blown flight plan, maybe excluding item 19
As for adding a flight plan form as a Canvas form, some wizards would be needed to help filling in a full blown ICAO flight plan form (that is actually how Eurocontrol does it, see
their folder on filing a flight plan, and they can hardly be alone). I believe item 10 and 18 are the trickiest ones,
but most of the time the aircraft type will give pretty much all of the required information (except some information in item 18). The availability of FGCOM and other voice communication could be added as a remark in item 18.
Sorry for the long post, but I could not help myself.