Optimising take-off & landing procedures

Airport Obstacle Database (AODB) provides accurate, current runway and obstacle information. Engine Fail Procedures (EFP) are configured by performance specialists and included as part of the offer.

Available payload at takeoff is directly influenced by the obstacles included in the AODB, which are based on the EFP track.

AODB is compatible with a variety of external performance applications, but also includes integration into Flysmart+ and more recently Mission+ PERFO Electronic Flight Bag solutions.

AODB users have the option to receive the service on a daily basis, per AIRAC cycle, or both.

aircraft taking off

Authored on

A330 in flight at Toluca & La Paz

Key features

  • AODB contains 3,000 airports worldwide.

  • Standard and non-standard EFPs are available. Whilst standard EFPs are favourable, non-standard EFPs are sometimes required with turns below 1,500ft.

  • We aim to make standard EFPs more simple to operate, with a straight climb applicable for all aircraft types, with a reduced obstacle accountability area.

Safe routing during a pivotal moment

State sources, including Aeronautical Information Publication amendments, supplements and NOTAMs are analysed to obtain the latest runway and obstacle data. Both permanent and temporary data changes are included in the AODB.

EFP creation uses AODB data to provide a safe, executable route for take-off and hold patterns. Splays are applied, extending outwards from the runway, to identify obstacles which must be included in performance calculations, complying with both regulatory and company requirements.

EFPs are provided for all usable runways. The AODB is aircraft agnostic, hence the EFPs are designed geometrically without being optimised for any one individual aircraft type. 

  • Talk with an expert to learn about our solutions.

Discover our Aeronautical Data Solutions