This module displays an expanded list of individual flights which can be reviewed, and edited.

Each record includes data fields for all important flight data like flight number, scheduled times, weekdays and much more.

Upon opening the module, the Table mask is empty. Flight plan data is read from the database by clicking the button Search . Before you start a data search, you can define freely selectable filters in the Search panel in order to reduce the amount of data records displayed in the table.

Filtering is very important for two reasons:

1) Your search results will only include exactly what you are looking for, giving you a far better overview and

2) without filtering you will read hundreds or even thousands of data records, which might lead to a reduced system performance.

Key data unambiguously defining a flight record is marked with a red title in the Edit panel.

The expanded flightplan allows multi editing: Several data records may be edited at the same time. The editing has to be activated by clicking into a greyed out field.

Following data is recorded for each individual flight (please note that some details are displayed in the Search/Edit panel only):

Station:*	If you are logged-in under the holding, this field shows which station a flight is assigned to. Please note that data records cannot be created or edited if you are logged-in under the holding!
SEA:	Free-text marker to define the season a flight belongs to (e.g. WS08 for winter season 2008). This entry only serves informational purposes.
DATE:	Flight date, given in the format DDMM (day/month) without any separators. Note that the Search panel features to corresponding data fields – SD from and SD to – to allow defining a time span as search rule.
STAT:	Planning status of the flight. In the standard version of the application, following coordination states are available: * = Attention flag, flight has particularities or inconsistencies (e.g. date is outside the normal seasonal time limits); C=Flight has been cancelled (cancelled), but remains stored in the database; X=Flight is to be completely deleted and removed from the database (Attention: Assigning this status will completely delete a flight record!); #=Flight is in a planning state and details are still being discussed with a coordination center and might be changed; O=Flight has not been cleared by the responsible coordination institution.
*:	Automatically assigned attention flag which is activated whenever a flight data record shows a possible irregularity or particularity. Examples are: 1) An A-ST (Scheduled time according to airline) is recorded, 2) the coordination status is not "blank" 3) at least one chaining indicator is set etc.
ST:	Scheduled Time of Arrival/Departure – given in the format HHMM (hour/minute) without any separators
A/D:	Identification of the flight as Arrival (A) or Departure (D)
A/L:	ID code of the airline
FLN:	The flight number
CALLSIGN:	Flight's callsign
SVC:	Traffic type (charter, line, military etc.) is selected from this pull-down menu
ORD:	"Origin Date" is an indicator for the original plan date of a flight. As a flight planning date always refers to the date when the flight actually started, it happens that the arrival at its destination is a day or two later. In order to have an unambiguous reference between the start and actual date, this field can be used to enter a numerical value (0, -1, -2) for calculating the original date. Example: A flight with an arrival date of Jan 1^st and an ORD marker of "-2" left its origin on Dec 30^th.
ROT-FLN:	Arrival and departure of an individual aircraft can be linked to a so-called "rotation" in order to keep track of the aircraft's stay on the airport. This function is described in chapter Chaining of arrivals and departures. After a flight has been "chained" the flight number of the related arrival/departure is listed in this field.
ROUTING:	Only available in the Search panel. Filter flights according to their origins/destinations and stopovers (Via-flights). This is done by entering the international 3-letter code of the desired stopover airport. Multiple filters can be set by entering more than one code, separating each code with a blank.
OPR:	Operating company is selected (this might be a different company than the owner of the aircraft)
A/C:	Aircraft type in according to IATA code
GATE:	The gate
POSITION:	The position
BELT:	The belt
COUNTER from/to:	Check-in counter assigned to flight
TERMINAL:	The Terminal
SEAT:	Maximum seats available for the aircraft
MTOW:	Maximum take-off weight of the aircraft (in kg)
NAX:	Noise annex of the aircraft
N/S:	Number of night stops of the flight (1 means a single night stop etc.)
SCHENGEN:	Mark an airport as member of the Schengen Agreement (only relevant for European countries).
Intern./Domestic:	International/Domestic marker of the flight. Entering an "I" will denote an international, a "D" is entered for a domestic flight. Field will be available soon.
GA:	A marker for General Aviation flights. Activated checkbox: General Aviation Deactivated checkbox: Line/Charter
OD1-3:*	Up to three origins (for arrivals) or destinations (for departures) can be selected. If no stopovers are planned, only one origin or destination has to be selected. The pull-down menu lists all international airports according to their 3-letter codes. These fields are available in the Edit panel only. In the Search panel, the corresponding data can be filtered in the field ROUTING (see above).
OPS:	Handler Operations
PAS:	Handler Passengers
RMP:	Handler Ramp
CDSH1-4:	For flights sharing a code with other flights, up to four "codeshares"
REMARK 1-2:	Freely definable notes about the flight data record
Exported:	Checkbox to display the export status of a flight (i.e. for flights which have or have not yet been exported to the daily flight scheduling).
Modified By:	Name of the user who edited the flight record last
Last Changed:	Time and date when the data record has been changed last
History:	Major changes are logged automatically including time stamp

Functions in the expanded flight plan

There are two main functions in the expanded flight plan. First, individual flight records can be reviewed, edited or newly created. Please note that the modification of individual flights will usually have consequences for regular flight periods in the condensed view. The second function is the management of "chainings/rotations" between arrivals and departures of individual aircraft as described in the following chapter.

Chaining of arrivals and departures

In order to keep track of an individual aircraft's stay on the airport, Seasonal Flightplan offers a function for linking the arrival and departure of an aircraft. This process is called "chaining", while the resulting linkage between arrival and departure is called "rotation". The available functions allow you to create, delete or exchange chainings.

The following function buttons are available to edit chainings in the module Seasonal Flightplan:

Unchain the Selected Rotation: Clicking this button will delete the chaining (link between arrival and departure) of the currently selected flight. If multiple flights are selected, all their chainings will be removed.

Chaining: After you have selected an arriving and a departing flight from the table, you can use this button for chaining both flights to a rotation.

Interchange chaining: After selecting two flights which are already chained with different flights, clicking this button will swap the corresponding chainings between the selected flights.

For chained flights, the flight number of their corresponding arrival/departure is listed in the field ROT-FLNR.

For eliminating a chaining, it is only necessary to mark one of the chained flights. This is done by clicking the function button Delete chaining . After that, both the formerly linked arrival and the departure will be split and displayed without a ROT-FLNR (note that the successful splitting has been commented in the message in the lower left corner of the Table mask).

After marking both flights (multiple records can be marked by keeping the Ctrl-key pressed and then clicking on them), the button Chaining is highlighted and can be used to create a rotation between the two flights (note that the successful chaining has been commented in the message in the lower left corner of the Table mask).

It is also possible to interchange (swap) chainings of flights, which are each linked to a different partner. This is done by marking two chained flights and then clicking the button Interchange chaining .