AIRAC Cycle

1

• AIRAC Cycle
• and
• impacts of large changes

2
AIRAC

• Aeronautical Information Regulation and Control
  (AIRAC) (ANNEX 15, Chapter 6)
• Information shall be distributed under the
  regulated system (AIRAC), i.e. basing
  establishment, withdrawal or significant changes
  upon a series of common effective dates at
  intervals of 28 days . The information shall
  not be changed further for at least another 28
  days after the effective date, unless it is of
  temporary nature and would not persist for the
  full period.

3
AIRAC

• Aeronautical Information Regulation and
• Control (AIRAC) (ANNEX 15, Chapter 6)

Recommended Practice Whenever major changes are
planned a publication date of at least 56 days
in advance of the effective date should be used.
In all instances, AIRAC information shall be
distributed at least 42 days in advance of the
effective date with the objective of reaching
recipients at least 28 days in advance of the
effective date.
4
Why do we need a regulated system?
5
Why do we need a regulated system?
6
Why is timeliness essential?

• What happens with AIP data after receipt by
  Database Suppliers and/or Airlines?

7
Effective date minus 20 days

• Database cut-off
• Any information received after cut-off will NOT
  be processed for the next AIRAC cycle

• Integrity and consistency checks

• Delivery of raw data to customers (Not FMS usable
  data)

8
Effective date minus 15 days

• Start of production of FMS data
• Compares and Packs

• For each airline individually
• OPS coverage
• packing software
• FMS manufacturer
• FMS software version
• FMS output
• Variation and calculation models
• Navigation algorithms
• Leg type changes
• Data selection

9
Operational Flight Program
U1.4 U1.5 U1.6
U5
U6.0 U6.1 U6.2
U7
U7.1
U7.2
U7.3
U7.4
U8.0 U8.1
U8.3 U8.4
U10.0 U10.2
Step Down Approaches
C
C
C
C
C
C
C
C
C
C
GS Intercept before FACF
C
C
C
C
C
C
C
C
C
C
Missed Approaches
C
C
C
C
C
C
C
FMS and GPS Approaches
C
C
C
C
C
C
C
NDB Approaches
C
C
C
C
Multiple Approaches same type / Rwy
C
RNP stored in Database
C
10
Effective date minus 15 days

• Determination of file size
• Handling of oversize problems
• Database sizes
• System capacities

• Large AIRAC cycles

11
Effective date minus 7 days

• FMS data shall be with the airline
• Company routes updates
• Aircraft rotation problems
• gtgt updates in time?
• Electronic transmission
• vs. regular mailing

12
Impact of

• Last minute postponements of AIRAC changes
• Information released with immediate effect
• Late publication of AIRAC information

gtgt Disharmony chart and database gtgt Disharmony
pilot and ATC
13
Possible Solutions

• Long-term vision
• Real-time updates at the gate or during the
  flight
• The whole industry needs to change standards and
  procedures
• Changes to todays databases required (which are
  only current once every 28 days)
• Medium-term vision / short-term solution
• electronic data transfers
• data loader onboard the aircraft
• disappearance of data overflow problems
• new aircraft
• new systems

14
(No Transcript)