ID:

Airline_UC002

Title:

Airline changes aircraft for operational flight

Description:

Airline changes aircraft for an operational flight and sends an updated aircraft data (aircraft type, registration, tail) to airport.  

Primary Actor:

Airlines

Secondary Actor:

Airports

Preconditions:

Operational flight record already exists in AODB.

Postconditions:

Aircraft data is updated in flight record in AODB.

Trigger:

Any number of unplanned circumstances which requires a change in aircraft.

Goal in Context:

Airport operations is aware of aircraft change and adjust their activities accordingly.

Main Success Scenario/Flow:

1. Airline informs airport (or sometimes airport discusses with airline) of aircraft change for an operational flight.
2. Airport receives aircraft change updates for an operational flight.
3. Airport validates the new aircraft information.
4. Airport identifies the relevant operational flight in AODB.
5. Airport updates aircraft information in the operational flight record in AODB.

Extensions:

Subsequently, AODB is triggered to send an update to RMS for resource plan assessment.

Frequency of Use:

On demand. 

Status:

Owner:

Davey Zheng 

Priority:

Stakeholders and Benefits:

Airline, Airport

Benefit:   Apron safety, operational reliability and efficiency (i.e. reduction of tows) and maximizing gate utilization.

Comments, Modifications, Suggestions