Dev:LH Core Admin-Flight plan

The Flight Plan application allows administrators to define and manage planned flight operations for a specific time period.

A flight plan represents a structured collection of scheduled flight courses operated by a designated carrier within a defined validity period.

This module ensures:

•Clear definition of operational periods

•Accurate planning of offered routes

•Alignment between carriers, aircraft types, and schedules

•Consistency in operational and regulatory handling

The Flight Plan module enables administrators to:

•Define operational flight plans per carrier

•Structure complex routing scenarios

•Manage repetition logic

•Assign aircraft types

•Configure codeshares

•Maintain validity periods

It acts as the operational backbone for:

•Capacity management

•Service availability logic

•Regulatory checks

•Segment-based service restrictions

•Craft-based limitations

Flight Plan Overview Page

Purpose

The overview page provides a searchable and sortable list of all configured flight plans.

Table Structure

The table contains the following sortable columns:

Column Description

Flight Plan Code Unique identifier for the flight plan (e.g., FRA/ARN 2025/2026)

Name User-defined name of the flight plan

Carrier Designated operating carrier

Valid From Start date of the flight plan

Valid Through End date of the flight plan

Sorting

All columns are sortable via header arrows.

Available Actions

➕ Add New (Top-left button)

Creates a new flight plan.

✏️ Edit (Row Action)

Opens the selected flight plan in edit mode.

🗑 Delete (Row Action)

Deletes the flight plan.

•System should display a confirmation popup before deletion.

•Deletion is blocked if dependencies exist (e.g., linked cases or configurations).

🔍 Search (Top-right)

Search field filters flight plans by:

•Code

•Name

•Carrier

Flight Plan Details Page

The Details page consists of:

1.Base Data Section

2.Offered Courses (Segments) Section

2.1 Base Data Section

This section defines general information about the flight plan.

Fields


Field	Description	Required
Operating Carrier	Dropdown selection of carriers defined in Carrier Administration	Yes
Flight Plan Name	Dictionary input (multi-language supported; at least one language required)	Yes
Flight Plan Code	Unique identifier for the flight plan	Yes
Valid From	Start date of plan validity	Yes
Valid Through	End date of plan validity	Yes

Validation Rules

•Valid From must be ≤ Valid Through

•Valid Through must be ≥ Valid From

•All required fields must be filled before saving

Offered Courses Section

Note: Although labeled as “Offered segments” in some areas, this section actually defines courses.

🔎 Course vs Segment (Important Concept)

A Course = A complete journey from boarding to final disembarkation.

A Segment = A part of a course between two airports.

Example:

New York → Paris → London

•If passenger stays on the same aircraft in Paris → 1 course, 2 segments

•If aircraft changes in Paris → 2 separate courses

3.1 Offered Courses Table

The table includes:

Column Sortable

Departure ✅

Destination ✅

Repetition Type ✅

Default Aircraft Type ❌ (can contain multiple values)

Codeshares ❌ (can contain multiple values)

Available Actions

•➕ Add New (Top-right)

•✏️ Edit Course

•🗑 Delete Course (with confirmation popup)

•🔍 Search

Course Configuration

When adding/editing a course, the following sections appear:

4.1 Segment Definition

Segments (At least one required)

Each segment must:

•Have a departure airport

•Have a destination airport

•Ensure logical routing:

•The departure airport of a segment must match the arrival airport of the previous segment

Segment Fields

•From (required)

•To (required)

•Intercontinental / Continental indicator

•Regulatory zone information (if applicable)

4.2 Codeshares

Codeshare configuration allows assigning additional carrier flight numbers.

Functionality

•Select carrier from dropdown

•Enter codeshare flight number

•System combines carrier code + entered value

•Multiple codeshares allowed

•Can be added via ➕ icon

4.3 Schedule Section

Defines when and how often the course operates.

Repetition Type Options

•Single occurrence (exact date)

•Daily

•Weekly

•(Optional extension: Monthly / Yearly if needed)

Schedule Inputs


Field	Required	Description
Date	Required if Single occurence	Exact date of operation
Departure time	Yes	Based on local time of departure airport
Flight Duration	Yes	In HH:MM format
Default Craft type	Yes	Dropdown from Craft Types administration

Arrival time may be calculated from departure + duration, or entered directly depending on system configuration.

Daily Schedule Element

When repetition type is “Daily”:

•Departure time (required)

•Flight duration (required)

•Default craft type (required)

Weekly Schedule Element

When repetition type is “Weekly”:

•Select operating days (e.g., MON, TUE, WED)

•Departure time

•Flight duration

•Default craft type

Aircraft Assignment

The default aircraft type must:

•Be selected from the Craft Types administration

•Be valid within the carrier context

•Support operational limitations

Validation & Business Rules

•At least one segment required per course

•Segments must form a continuous routing

•Date validation must prevent logical conflicts

•Default aircraft must exist in craft types administration

•Codeshares must reference valid carriers

•Cannot save incomplete mandatory data

User Experience Principles

The module ensures:

•Clear operational planning visibility

•Transparent validity periods

•Consistent routing logic

•Structured scheduling flexibility

•Clean separation between:

•Plan level

•Course level

•Segment level

•Schedule level