{//% unless portal.user.is_agent %} Tickets
Login Submit a Ticket News {//% endunless %}

Creating a Flight Schedule

This section describes the processes of creating and maintaining schedules and adhoc schedules in the N-OC system.



To be able to create schedules in the system, there are certain prerequisites that must first be defined:


  • Data
  • Companies
  • Prefixes
  • Suffixes
  • Seasons
  • Aircraft Types
  • Versions
  • Configurations
  • Service Type Codes
  • Stations and Terminals
  • Default BLH (Distance)
  • Turnaround Times
  • IATA Rules
  • Company Rules
  • Messages and Receivers


For more information, please contact your administrator.


To open a New Schedule window, right mouse click in the Gantt on the aircraft registration row until this window appears: 


Note: Where you click on the Gantt will determine the proposed STD shown in the schedule window. (You will see this later on).



New Schedule icon

Ad-Hoc Schedule icon

Aircraft Reference Activity icon

Turnaround (Ground Times) icon

Maintenance Schedule icon

Timetable Detailed Rule Check icon


Creating a New Schedule

Select New ‘Sche’  

Click here to see a schematic display of the new scheduled flight.



The Schedule Header


Creating and maintaining schedules are presented in logical steps. There are two steps in the wizard: 1. Edit step 2. Message step. The wizard header displays the current step in the process (in red), and the next step (in grey). 


The Flight Identifier Panel


 The user enters the Airline code, Flight Number and Suffix in the Flight Identifier Panel. Completion of all fields is mandatory.   


Note: ‘Project’ and ‘Call Sign’ are optional fields.

Example for a ‘Project’:    


 The Calendar Panel

The user enters period information for the schedule in the Calendar Panel. 


Valid From: The start time for the schedule (which defaults to where the user pointed at with the mouse pointer in the Gantt).

Valid To: Set the end date.

Time: STD / ETD/

Frequency: Days of the week when the schedule operates.

Weekrate: If the created flight schedule operates weekly or bi-weekly.

Time Mode (only UTC available for the moment).

 The Route Panel

Single leg:

The user defines the routing in the Route Panel. The route must have a minimum of two stations, and can be up to a maximum of nine stations. 

Note: only active stations are shown in the drop-down list. 


If the user wants to activate a station that is not currently available from the dropdown, they select the  button. The user is then presented with a window like the one shown below.


The search option includes any of the following: Airport name, IATA code, or ICAO code. 

The  button makes the airport station available in the system.


Click on   to create multi-leg flights (i.e. fork flights) and select additional station(s). (Example: ARN > LHR > CDG).

The  above the 3rd station is for deletion.

 The Note / Action Panel

The action panel has 2 functions:  notes and new flight schedule creation.

1.     Note:  


The ‘Note’ is activated by clicking on the arrow on the left side of the panel.


The note can be stored either as an ‘SI’ (Supplementary Information) - it will only be part of the system, or as a Schedule Note (a predefined note type). Schedule Note is stored in the system. 


There are 2 buttons to copy an SI Note to a Schedule note and vice versa. The scheduled note will optionally be shown on the leg puck on the bottom left side (not implemented yet).

Remark: A ‘Notetype’ must be defined.


2.               Create the ‘legs’ of the new flight schedule.  




Here the user can create a new flight for any given season.


Insert the following information:

Airline Designator

Flight Number

Suffix (Optional)

Project (Optional)

Call sign (Optional)

Valid From

Valid To


Week Rate

Date Mode - UTCl







The Leg Panel


Select the  button – a new schedule editor row is displayed at the bottom of the window. Enter the required Schedule information: about the route, departure and arrival times, equipment, version, configuration, and STC.


The route and schedule times have already been created. The system uses the default BLH (Block Hours) for the specific aircraft type, period, weekday. The values are set in the ‘Distance’ tab in the station window. The default version and configuration for the leg is set as well. 

Creating a return schedule

To create a return routing click on . The system creates the outbound routing but in reverse (return leg based on the original city-pair with the ‘next’ flight number which can be modified), bringing it back to the starting point. This function also uses default BLH, and default turn around times, as pre-defined in the system.


Note: A minimum of selecting a Service Type Code ‘STC’ is mandatory.

Note the 4 subdivisions at the top when clicking one of these icons 

The user can change the following: terminal information, times, equipment and service type codes (STC). These four icons are shown on the right side of the window and store extra information for the leg. 

 Set the onward reference, aircraft owner and codeshare - see also Onward Flights concept

 (Flight Data as shown above):

Service:   Enter ‘Meal codes’

Crew:    Set Cockpit and Cabin Crew

PAX:  The user may edit passenger booking related information.



Note:  These are not fully implemented yet.


The function to add traffic restriction on a segment is now added. There is currently no validation if traffic restrictions are not to be combined according to SSIM manual or to add multiple traffic restrictions of the same code. This will be implemented later.


In the service tab in additional dialog in the schedule dialogs (New Schedule, New AdHoc, Edit Schedule and Create AdHoc from Schedule, there is now a possibility to add a traffic restriction code to a segment. This will be part of a NEW scheduled SSM and ASM message and the ADM message (if only changing this part of a schedule).


The SSIM file export also shows this on the Schedule row, (in  position 150) plus the number of points the segment points to. The SSIM file import will also parse Traffic Restrictions




Two Step Process


The process of creating, editing, deleting etc in N-OC usually follows two common steps:



1. The Step Panel

By clicking on Next in the step panel, the user proceeds to the next step - the ‘Message’ Page.


2. The Message Page - Processing Messaging/Reports/Eventflow tasks and saving. 

Here all relevant messages defined in the system will be automatically generated for the newly created flight. 


Below is an example: 

The user has entered the information and clicks on 

The Messages, Reports and Eventflow related to the new schedule are displayed. 

These are sent out and processed when the user clicks on Save. 


Note: Click on the magnifying glass to view and update the message/report/eventflow information before sending. 


You may enlarge the various messages by clicking on the ‘plus’ sign  where the message can be revised / updated if necessary.



The user can also set a date / time trigger:



Click on  to save your scheduled flight. The new schedule is then displayed in the Gantt as legs / pucks.




Adding Notes to the Schedule


There are two types of notes that may be added when creating a new schedule:

SI - Supplementary Information - these are added to the bottom of the standard IATA messages

Standard Note - See Editors > Company > Note Types





Creating an Ad-Hoc Schedule - see the reference article!

The Rule Check Panel



From the Rule Check Panel, the user can check and ensure that the newly created schedule complies with predefined rules (already set up in the N-OC Rule engine).

The status lamp (grey circle) displays different ‘traffic-light’ colors depending on the result of the rule check.  After a check is made, a tree-view shows which rules, calculators, or accumulators were used in the rule check. Any violations are also included.

Note: See ‘Check’ article for specific details.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.