The Table Flights

This table offers a groundhandler view within the Flights module. It provides information on single flights instead of rotations.

Via the Edit panel the corresponding leg (either arrival or departure) of the rotation can be edited as well.

Following data fields are available for each flight:

  • Station:*

Station for which the corresponding flight is valid.

  • ROTID:

Internal ID of the rotation

  • ROTTYP:

Type of the rotation (Arrival, Departure, Rotation)

  • Ready:

Marks flight events of arrivals/departures as fully recorded for further commercial processing.

  • Event State:

State of the selected event (Calculated, Invoicing, Open or Service)

  • A/D:

Identification of the flight as Arrival (A) or Departure (D)

  • FLN:*

Flight number of an arriving/departing flight

  • Callsign:

Callsign of the arriving/departing flight. The value is generated at the time of creation of the flight and in the event of a flight number change. By default the value is derived from the flight number by replacing the IATA airline code with the ICAO airline code. It remains empty if the airline codes are not administered in the master data. The value can be manually overwritten.

  • ORG/DST:

Origin/destination airport for arrivals/departures (IATA code)

  • Prev./Next:

Previous (for arrivals) or next (for departures) station of the flight

  • Codeshare1-4:

For flights sharing a code with other flights, up to four "codeshares" can be entered in these fields

  • ST:

Scheduled time of arrival/departure

  • ET:

Estimated time of arrival/departure

  • AT:

Actual time of arrival/departure

  • BT:

On -block time of arrival/departure

  • CT:

Cancel time of arrival/departure

  • … Public (ST, ET, AT, BT, CT):

Scheduled/Estimated/Actual/On-block/Cancel time of an arrival/departure to be published (e.g. to a FIDS)

  • Slot Begin/End:

Timestamp of slot begin/end

  • Slot Begin/End Public:

Timestamp of slot begin/end to be published

  • PAX Total D/A/Transit:

Total number of passengers is calculated automatically and is displayed

  • Cargo D/A/Transit:

Cargo of arriving/departing/transit flight

  • Mail D/A/Transit:

Mail of arriving/departing/transit flight

  • Bags D/A/Transit:

Number of bags

  • Status:

Flight status of arrival/departure

  • A/C-Type:

Aircraft type of arrival/departure

  • Reg(*):

Registration of arriving/departing aircraft

  • Airline:

Airline ID of arriving/departing aircraft. The ID is initially derived from the aircraft owner in the table aircraft as defined in the Master Data Flight Information. It can afterwards be changed manually.

  • Cash Payer:

Checkbox to mark an arriving/departing flight as cash payer.

  • SVC:

Service type code of the arriving/departing flight. The codes can be administered in the Master Data FIS, table Service Type Code.

  • Handling:

Handling type for an arriving/departing flight. The handling types available here are defined in the table Handling Type in the master data module Fis.

  • Belt(*):

Belt for an arriving/departing flight. The belts available here are defined in the table Belts in the master data module General.

  • Gate:

Gate for an arriving/departing flight. The gates available here are defined in the table Gates in the master data module General.

  • Position:

Parking positions for an arriving/departing flight. The positions available here are defined in the table Parking positions in the master data module General.

  • Check-In From(*)/To(*):

Check-in (from/to) counter assigned to the flight

  • Runway:

Runway for an arriving/departing flight. The runways available here are defined in the table Runways in the master data module General.

  • Terminal:

Terminal for an arriving/departing flight. The terminals available here are defined in the table Terminals in the master data module General.

  • Flight Type:

International (I) or Domestic (D) depending on the previous/next station.

  • Quality Check Completed:

By activating this checkbox the registration of SLA data is completed. The registration of SLA data can be set back by unchecking this flag. The checkbox Achieved is only editable, if the checkbox Quality Check Completed is not set.

  • Closed:

Flag to indicate whether the quality check has been closed. If true, the quality check fields cannot be edited anymore.

  • Delay Conclusion:

Freely definable text to describe the delay conclusion

  • Delay Total:

Total of delay

  • Remark:

Freely definable text comment

  • Modified By:

Name of the last user who changed the ARR/DEP data record. This entry is filled in automatically.

  • Last Changed:

Date and time when the ARR/DEP data record was changed last. This entry is filled in automatically.

  • Created By:

Name of the user who created the data

  • Create Time:

Time stamp of the data creation

  • ORD:

"Original 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 1st and an ORD marker of "-2" left its origin on Dec 30th.

The Table Flights -> Delays

This table is used to record delays of a rotation. The delays are administered in the module master data Fis, Delay-Codes.

To enter a delay make sure to have the correct flight selected in the table Flights, then move to the table Delays and create a new entry. Then enter the delay time and the delay reason code before you can save the entry.

  • FLN:

Flight number of the delayed flight

  • ST:

Scheduled time of the delayed flight

  • Source:

Information source of the delay

  • Delay Time:*

Time of delay in the format hhmm

  • Own Responsibility:

Mark if delay is to be considered as self-inflicted

  • Code:*

Code as administered in master data Fis, Delay-Codes

  • Subcode:

Additional detail code as administered in master data Fis, Delay-Codes -> Sub-Delay-Codes

  • Delay Reason:

Reason for delays administered in master data Fis, Delay-Codes

  • Chargeable:

Flag to be set if the delay can be billed

  • Caused By:

From this drop-down list the organisation unit (as defined in the module Rights), which is responsible for the delay, can be chosen.

  • Remark:

Freely definable text comment

  • Modified By:

Name of the last user who changed the ARR/DEP data record. This entry is filled in automatically.

  • Last Changed:

Date and time when the ARR/DEP data record was changed last. This entry is filled in automatically.

The Table Flights -> Quality Items

This table is used to assign quality items to a flight. To assign a quality item select the flight in table Flights, then switch to the table Quality Items, create a new record and enter data in accordance with the descriptions in the table further below.

  • SLA:

Reference number of the SLA to which the quality item refers

  • Quality Item:

Name of the quality item as defined in the master data table Contract -> Quality Items

  • Value:

Value of the quality item

  • Target:

Here, the actual nominal value for the service quality is recorded. This value is always based on the Unit defined in the corresponding data field.

  • Unit:

Lists the unit the quality item is accounted in (e.g. litre, hour, minute etc.) as defined in the master data table Contract -> Quality Items

  • Achieved:

Flag to indicate whether the target for a quality item has been achieved (yes) or not (no)

  • Remark:

Freely definable text comment

The Table Flights -> Incidents

This table shows the incidents assigned to a selected flight.

  • Source:

Information source of the incident message

  • Position:

Position assigned to flight

  • Text:

Text of the incident message

The Table Flights -> Messages

This table shows all IATA and AFTN messages related to this flight, if these optional interfaces are active.

  • Station:*

Shows the station for which the message record is valid

  • Type:

This field shows the message type (e.g. MVT, ASM, BFD).

  • Parser Errors:

Number of syntax errors (not allocation errors) which have been identified in the message parsing process. This field is marked in red if the number is larger than 0 and if the flag Ignore is not set.

  • Logic Errors:

Number of logic errors which have been identified. This field is marked in red if the number is larger than 0 and if the flag Ignore is not set.

  • Header:

Header part of the message

  • Message:

This field shows the actual message body part of the message. It can be edited if necessary.

  • Appendix:

Appendix to the message

  • Remark:

Freely definable text comment

  • Received:

Time stamp for the message

  • Modified By:

Name of the last user who changed the ARR/DEP data record. This entry is filled in automatically.

  • Last Changed:

Date and time when the ARR/DEP data record was changed last. This entry is filled in automatically.

  • manually created:

Flag that shows if the message has been created manually.

Often SSRs are recieved via email (not even in PSM format). Such free text infomation can be added to Daily Flight Plan → Flights: Messages, so they are visible in the MSR and can be considered for SSR-related service registration.

The messages received from the IATA Interface remain to be not editable in these tables, but the new entries are editable.