+ *
+ * This is traffic manager version II. The major difference from version
+ * I is that the Flight Schedules are decoupled from the AIAircraft
+ * entities. This allows for a much greater flexibility in setting up
+ * Irregular schedules. Traffic Manager II also makes no longer use of .xml
+ * based configuration files.
+ *
+ * Here is a step plan to achieve the goal of creating Traffic Manager II
+ *
+ * 1) Read aircraft data from a simple text file, like the one provided by
+ * Gabor Toth
+ * 2) Create a new database structure of SchedFlights. This new database
+ * should not be part of the Schedule class, but of TrafficManager itself
+ * 3) Each aircraft should have a list of possible Flights it can operate
+ * (i.e. airline and AC type match).
+ * 4) Aircraft processing proceeds as current. During initialization, we seek
+ * the most urgent flight that needs to be operated
+ * 5) Modify the getNextLeg function so that the next flight is loaded smoothly.
+