1. The support of analysis tools to flight inspection activities
International Flight Inspection Symposium
Oklahoma City, OK USA June 2008
The support of analysis tools to flight inspection activities
M. D. Mannino A. Nobiletti IDS Ingegneria Dei Sistemi S.p.A.

2. The support of analysis tools to flight inspection activities
IFIS 2008, OKC

3. The support of analysis tools to flight inspection activities
Contents
1. Introduction
2. New design challenges from RNAV navigation
3. The IDS approach to the problem
4. Conclusions and Recommendations
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

4. The support of analysis tools to flight inspection activities
Introduction
ICAO
PAN-OPS
FAA
AIP
Ann. 10
ARINC
424
JAA
RTCA
YYY
XXX
zzz
’50s
’80s
Today
Eurocontrol
Until today instrument flight navigation procedures rely upon to fixed ground Navaids, but this cannot be assumed any more. Recent RNAV safety cases highlighted risks and hazards associated with poor data quality Today’s data integrity performance is far from that specified by ICAO. Area Navigation and the potential to apply GNSS together depend ENTIRELY upon data quality.
Interoperability and collaboration is a key to the future AIS , Flight inspection and MIL ORG all this is reliant on data of the required content, quality & timeliness to reach “The right digital info, right place, right time”
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

5. classical use of the ground based radio-navigation aids
Introduction (cont.)
Low flexibility
Not only good news, but also …
Restrictions
Constraints
The advent of area navigation gave a wider degree of freedom to the designers, but introduced new challenges related to:
the possible use by the aircraft Flight Management Systems (FMS) of different sets of ground based radio-navigation aids with respect to the ones identified by the designer
the use of sources of navigation signal not spatially fixed (i.e. GPS satellites).
These new features have dramatically increased the complexity of the IFP design work.
… new challenges and increased complexity
classical use of the ground based radio-navigation aids
Area Navigation
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

6. Industry/Criteria Requirement
Today’s safe Nav procedures rely upon their reference to fixed ground Navaids
This cannot be assumed in future applications
Recent RNAV safety cases highlighted risks and hazards associated with poor data quality
Today’s data integrity performance is far from that specified by ICAO.
ICAO requirements not met
No differences filed.
Area Navigation and the potential to apply GNSS together depend ENTIRELY upon data quality.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

7. The support of analysis tools to flight inspection activities
Challenges
Interoperability and collaboration is a key to the future ANS ORG
Is reliant on
with data of the required content, quality & timeliness
The right digital info, right place, right time
AIS is introducing ISO , but for most it is process only
What is required is the fixing of the process of “origination to publication”,
The co-operation of all actors in the data processing chain is fundamental and IDS actually have a proven solution to this requirement
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

8. The support of analysis tools to flight inspection activities
RNAV REQUIREMENTS
ICAO state in the “Flight procedure design Manual” (released in Q3 2008) that the procedure design process consists of different steps:
Requirements and data collection
Design and first ICAO rules checks
Pre-Validation
Flight check
Publication
Eurocontrol stated in the “Guidance Material for the Validation of RNAV Procedures” the main steps to be performed in validating RNAV procedures
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

9. The ICAO proposed flow for the Procedure Design Quality
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

10. The Eurocontrol proposed flow for the Procedure Design Quality
Organization
Activity
Comment
ICAO rules in the design
Minimum distance between waypoints
MCA (Minimum Crossing Altitude) on WP, gradients, etc
ARINC 424 checks on the coded procedure
P&T Sequence, legs attributes, etc
Flyability checks
Max weight, max bank angle, etc
Temperature and cross/head Wind effects
Signal in space check (coverage, multiple DME/DME analyses, satellite visibility, etc)
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

11. Eurocontrol Guidance Workflow
Design procedure.
Close co-operation with Navaid Service Provider and Users
Collect
Collate data concerning Navaids infrastructure, obstacles and aerodrome
Supplied by approved surveyor/airport/government department.
Collate and check data to be issued to flight inspection organization.
Procedure design Office
Procedure Owner
Navaids Engineer Office
Procedure Design
/AIS Unit
Analyze
Administration
Validation
EAD Slot mgmt
Conduct independent
review of design and
check flyability if design
is non-standard.
May be done by a third party.
Analyse flight inspection
report. Recheck
flyability if necessary
Mainly for navaid coverage but may also address bstacle
assessment and flyability.
Activities
Flight
Flight inspection
Conduct Flight
Inspection
See ICAO Doc 8071
Review
Obtain approval for publication
Publish procedure and
monitor operational
application
Procedure Design & Navaids Engineer
Validate
Procedure Design Office/ Owner/ AIS/ ATC /Regulator
Design
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

12. New design challenges from RNAV navigation
GNSS related topics (from ICAO, 2007, Manual on Testing Radionavigation Aids doc. 8071, volume II, Testing of Satellite-based Radionavigation Systems, chapter 1):
GNSS analysis
geodetic survey
GNSS monitoring
Record keeping
availability of prediction SW
GPS selective availability
When dealing with GNSS navigation the IFP designer and the flight checking teams shall be aware that their attention shall be focused on identification of possible sources of degradation of the quality of the GNSS signal. This goal shall be achieved by means of ([4], chapter 1):
GNSS analysis
geodetic survey
GNSS monitoring
Record keeping
availability of prediction SW
GPS selective availability
These means that the availability of computer aided tools connected to a reference ATS database where all the stored data has been collected by means of a professional site survey will enable the designers to achieve their tasks in a safe, robust and traceable manner.
In these latest years a lot of work has been executed on the field of site surveys and the way in which the terrain and the obstacles information shall be collected, processed and stored (see [8]). The work related to this item is focused on the identification of a conceptual model to the representation of the information related to the aerodrome and to the surrounding environment.
Another very important task is related to the prediction of possible failures of the GNSS signals due to bad satellite geometries, terrain masking, multipath and or interferences.
As stated in [5], the availability of a prediction tools which make use of GPS almanacs is very important both in the pre-flight phase and in the design phase of and IFP.
During the design of an instrument flight procedure it’d very interesting to have tools which enable the analysis of the satellite performance to failures due both to satellite expected or unexpected failures, and to the effect of ground based sources of radio interference.
If an IFP designer were able to assess constraints related to the intrinsic GNSS geometries limitations (i.e. few satellites in view) and to the additional constraints coming from the operational environment (i.e. terrain masking and sources of interference), the following work phases bring to the IFP publication (ie. design quality check, IFP fight checking) will have many benefits in terms of:
reduced time to publication
optimization of man power
increased work quality.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

13. New design challenges from RNAV navigation PANS-OPS
DME/DME related topics (from ICAO, PANS OPS-Doc 8168, “Procedures for Air Navigation Services - Aircraft Operations”, Volume II Construction of Visual and Instrument Flight Procedures, vol. 2, part III, sec. I, ch. 3 ): it’s “not possible to know which DME facilities the airborne system will use for a position update, a check should be made to ensure the appropriate DME coverage is available throughout the proposed route …”.
In practical terms this means that the designer should look for the worst geometry of the DME couples and check the obstacles clearances against that case. But how many cases shall be investigated in order to look for the worst case ([7]) ?
Let’s assume that N DMEs with the required coverage and geometry are available, then the number of possible DME couples to be used for DME/DME navigation can be computed as:
In practical terms when 5 DMEs (N in the above formula) are in radio coverage and are compliant to the 30°/150° angle criterion the designer shall inspect up to 10 couples in order to look for the worst case. A very time consuming task !
When the aircraft is flying at low altitudes the terrain masking is becoming an important factor, and the complexity of this problem is increased due to a not straightforward way to account for terrain masking.
N=5
NDMEcouples=10
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

14. New design challenges from RNAV navigation – PBN -
DME/DME related topics (from ICAO, NAVIGATION INFRASTRUCTURE ASSESSMENT IN SUPPORT OF PBN): “Appropriate tools should be used to assess navigation infrastructure. While the assessment could be conducted using manual analysis and flight inspection, the use of a software tool is recommended in order to make the assessment more efficient.
The software tool should be tailored to allow evaluating the infrastructure in light of the requirements imposed by a specific navigation specification, such as RNAV-1.
In general, RNAV assessment tools should include a 3D terrain model with sufficient resolution and accuracy to allow predicting the line of sight visibility of navaids along a procedure service volume, including an analysis of their respective subtended angles and a variety of other geometric constraints.”
When the aircraft is flying at low altitudes the terrain masking is becoming an important factor, and the complexity of this problem is increased due to a not straightforward way to account for terrain masking.
In complex environments where the DME density is high like in the core Europe, the need to use SW tools has been recognized by some years by Eurocontrol ([7]).
ICAO in its document on the navigation infrastructure assessment in support of PBN ([9]) says that “Appropriate tools should be used to assess navigation infrastructure. While the assessment could be conducted using manual analysis and flight inspection, the use of a software tool is recommended in order to make the assessment more efficient. The software tool should be tailored to allow evaluating the infrastructure in light of the requirements imposed by a specific navigation specification, such as RNAV-1. Such a tool could, but does not have to be integrated with procedure design tools. In general, RNAV assessment tools should include a 3D terrain model with sufficient resolution and accuracy to allow predicting the line of sight visibility of navaids along a procedure service volume, including an analysis of their respective subtended angles and a variety of other geometric constraints.”
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

15. New design challenges from RNAV navigation (cont.)
Procedure validation related topics: ICAO, JAA, and Eurocontrol recognize that the Flyability check is part of the quality process related to an IFP design and publication:
Aircraft maneuvering in context of safe operating practices for the category of aircraft
Cockpit workload
Charting aspects
Navigation database aspects
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

16. New design challenges from RNAV navigation – Annex 15
Data integrity related topics: ICAO in Annex 15 requires the “Contracting States shall ensure that integrity of aeronautical data is maintained throughout the data process from survey/origin to the distribution to the next intended user. Aeronautical data integrity requirements shall be based upon the potential risk resulting from the corruption of data and upon the use to which the data item is put”
The following classification and data integrity levels apply:
routine: 1x10-3
essential: 1x10-5
critical: 1x10-8
In order to demonstrate that the above stated level of data integrity has been achieved and maintained throughout the complete data process, the old style hands and paper dissemination of the AIS data has reached its end.
What the future is preparing for us is a set of tools which enable to store, import and export data in electronic format, whit most of the data protected by cyclic redundancy checks (CRC) and other means in order to guarantee the data integrity.
A relevant work is executed by the international community on the field of data acquisition and to its dissemination. The following items are of main concerns:
Survey of airport terminal areas (terrain and obstacles);
Development of a systems (named eTOD) able to manage terrain and obstacles according to ICAO ANNEX 15 and EUROCAE requirements;
Capability of interfacing with the flight procedures and airspace management system;
ICAO A & B Obstacle Charts Production;
Full adoption of ICAO data Quality standards;
Use of high technology sensors and processes.
The cutting edge of the activities in this field is related to the development (see [8]) for guidance material, which should assist States, inter-alia, in the definition of:
the responsibilities and roles of the different bodies involved in the implementation process;
the quality of data collection techniques;
the Methods for the validation and verification of eTOD;
the data model(s) to be used;
the Mechanisms for the storage and exchange of eTOD; and
the cost recovery mechanism to be used
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

17. New design challenges from RNAV navigation (FAA .52)
Instrument Flight Inspection data management related topics: (from FAA Order “Aeronautical Data Management” ): the data must accurately reflect the references to be used in the performance of inspecting the systems supporting the National Airspace System (NAS). These data will be the references for certifying the quality of signal-in-space, and the instrument flight procedures
The availability of
data used by the Automated Flight Inspection Systems (AFIS) which has been validated by AIS teams
tools for the Flight Inspection Report Processing (see [10])
tools the distribution of data collected during the flight inspection mission
are recognized as tools which are improving the proficiency of the flight inspection teams.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

18. The IDS approach to the problem
IDS has been involved by many years in the provision of system and services with qualified personnel
IDS relies on advanced graphics and databases, integrating multiple data sources such as maps, photos, property records, survey and engineering data, inspections reports, traffic safety prescriptions, congestion statistics, documents, aeronautical charts.
IDS solutions help the air transport industry to manage strategically and efficiently this information.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

19. OSED (Operational Scenario and Environment Definition)
OSED - Methodology
Scenario Definition for Procedure Drafting
Aerodrome, Terrain, Obstacle
Defining IFP Design Constraints due to environment.
OSED (Operational Scenario and Environment Definition)
Geospatial Data, ATS Geography, Operational Data, Airport Constraints, Meteo
Defining IFP Design Constraints due to Airborne Usability of Signals in Air (ICAO Annex 10)
EMACS: Ground Based Navaids
EMACS TAMIA: potential EM interferences
EMACS ASUV: Signal Usability for GNSS and DME
FPDAM: drafting IFP for ground based and satellite based infrastructure
ENCODER: IFP ARINC 424 encoding (path terminations and WP types)
VESAS: PBN/RNAV/RNP performance prediction
Pre-validation Phase
Pre-Flyability Validation
AACS: Advanced Aircraft Cockpit Simulator
Pre-flyability checks
Pilots familiarization with new procedures
FLIPP: Flight Inspection Planning and Post Processing
Planning Mission
Data Acquisition
Combined with VESAS comparison between prediction and measurements
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

20. The support of analysis tools to flight inspection activities
An operational workflow from monitoring ,design and analysis, to pre-validation checks
FPDAM
Procedure - SSA DATA Already CODED
FPDAM
Flight Procedures Design
Airspace Management
VESAS
Mission Planning
EMACS
Virtual Flight Inspection
IAS
DATA Maintenance
and Publishing
AeroDB
VESAS
Virtual Flight
Flight Simulation
Area of benefits
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

21. Airport Survey, Terrain & Obstacle Data Management (eTOD)
Terrain 3D Modelling (WGS84 reference datum)
GIS based geodetic calculations and projections
Geo referencing Obstacles and Relief
Airport layout
Aerodrome ICAO type A & B Chart
Terrain & Obstacle Database Management e-TOD.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

22. The support of analysis tools to flight inspection activities
IDS Measurement Laboratory Services Site Survey and Monitoring of GNSS Signals
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

23. Measurement Laboratory Services GNSS Monitoring Station for Airports
Dual Frequency GPS antenna
GPS Receivers /splitters
Reference Oscillator
Spectrum Analyzer to monitor Interferences
Control PC
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

24. The support of analysis tools to flight inspection activities
Measurement Laboratory Instrumentation for setting up GNSS monitoring stations
IDS Signal simulator of L band signal as received from a simulated GNSS satellite constellation
GPS Receiver
GNSS signal Simulator
Antenna
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

25. Procedure Design - FPDAM
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

26. The support of analysis tools to flight inspection activities
Procedure Coding
In order to build the flight profile and trajectory, the first element to be set is the Aircraft model;
Encoder window opens (see Fig. 4‑13) and the current flight procedure can be saved (Save session) in the chosen path, together with the initial condition file necessary to build the flight profile.
Editing Flight Procedure
By clicking Tools→Edit Flight Procedure→Editor the Waypoint Editor Window opens (see Fig. 4‑14).
If a flight procedure was previously loaded (or created), this is visualized (orange crosses) in the 3D main window and it can be, if necessary, modified. In order to modify a waypoint, it must be selected through the combo in the window; in the 3D view the its colour changes from orange to violet; after the selection is done is position can be changed or directly writing longitudine, latitude and height in the corresponding fields of the window, or by clicking with left mouse button on the desired point, whose coordinates are then written in the window; the other fields can be changed directly through the GUI. The new waypoint is then saved in the flight procedure file by clicking Set WayPoint.
Loading flight procedure
An existing flight procedure can be retrieved from:
FPDAM DB, by clicking Tools→Load Flight Procedure→Encoder;
local DB, by clicking Tools→Load Flight Procedure→Local;
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

27. ASUV:Area/Airborne Signal Usability Verification DME/DME
Radio Coverage characterization:
As previously described ASUV requires as input parameter:
The terrain within the analysis domanin;
The set of DME ground stations (with the related data such as frequency, Tx Power, antenna Model, …) to be analyzed: this set is know as “configuration”
The next step si to execute a characterization analysis: this is an analysis focused on the evaluation of the Line of sight within the maximum operative range of the ground station.
The output of thsi analysis is a matrix showing the minum altitude at which an aircraft should fllight in order to be in line-of-sight to the ground station.
This analysis is to be executed for all the ground stations belonging to the configuration uner analysis.
If someone has previously executed a characterization analysis on one or more ground stations belonging to , the ASUV tool will not execute anymore this analysis and will reuse the existing one.
In such a manner the ASUV system will reduce the computation time as long as it is used to execute the analys on the existing network of ground stations.
In a following phase the user will select an analysis domain on which the xxxx
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

28. ASUV:Area/Airborne Signal Usability Verification
DME/DME Performance analysis:
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

29. Ground Augmentation System Siting
GASS:
Ground Augmentation System Siting
Worst Case Interference Margin
VDL Radio coverage and Interference Margin Analysis
In Band Interference Margin
Out Band Interference Margin
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

30. ASUV:Area/Airborne Signal Usability Verification
GNSS Performance analysis:
Critical zones analysis:
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

31. GASS: Ground Augmentation System Siting
Multipath analysis:
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

32. Wide area multilateration
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

33. Pre Flyability check with different evaluation view(simulation)
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

34. Procedure Virtual Flying (cockpit Simulator)
The support of analysis tools to flight inspection activities
IFIS 2008, OKC

35. Real time monitoring of RNAV GNSS approaches
Landing Monitor
Real time monitoring of RNAV GNSS approaches
Functionalities
Flight tracks real time monitoring based on ADS-B data
2-D, 3-D protection areas display
ATS data management
RNP Tunnel-incident detection alarm
Reception and decoding of ADS-B 1090 ES report (according to EUROCONTROL, ASTERIX 021 ) and system track (according to EUROCONTROL, ASTERIX 062 )
Automatic flight data display (ICAO Target Address, Target ID, Vertical rate, geometric altitude, ground speed,……) 1
The support of analysis tools to flight inspection activities

36. System Architecture and Landing Monitor
ADS-B Station
1090 MHz ES
GBAS Reference and Monitoring station
GNSS VDB
CWP
Position Landing Monitor
Position
ARO/MET
GNSS
PSR/SSR Radar
FDP
Flight
plan data
radar
data
Gateway
GPS & GEO
Tracking & Data Fusion
GNSS VDB
Transponder 1090 ES
On-Board segment
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

37. Safety/Quality procedures
Currently we are tuning ourapplications to fully comply with the workflow that integrates quality and safety procedures according to Eurocontrol SAfety Regulation Requirements (ESARRs) and Safety Assessment Methodology (SAM) following the ICAO PBN manual
RNAV Approach operation: Pre-operative phase
Obstacle notification and survey
Maintenance of new obstacles & airspace changes database
Obstacle assessment
Procedure design (initial & change)
Code the procedure
Procedure validation (might include flight check)
Safety Procedures
Promulgation of procedure (new or changed), linked to AIRAC cycle
Quality Procedures
Flight crew training to LPV approach
Operational evaluation of the new procedure
Produce maps&charts, distribute them to aircrews before start of AIRAC cycle
Code current navigation database before start of AIRAC cycle
Load NAV database
ATCO training to LPV approach
Avionics equipment meeting AMC20-XX fitted
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

38. The IDS approach to the problem (cont.)
eTOD
Survey Data
Obstacle & Aerodrome Charts
Terrain Database
Obstacle Database & Surveyed ATS Data
Survey
Data
Manager
Planning
Obstacle
Encoders
Reference Aero Data for Projects
Aero Projects Database
Interface to ATC
(Radar Maps)
Virtual Flight Inspection
Flight Procedures
Airspace & Routes
Interface to Fast Time Simulation
Navaids Maintenance
WEB
PLX
PLX
WEB
Data Originators
PLX
Electronic Data
Data
Administration
&
Maintenance
AIS
Database & Document Repository
AIP/eAIP
Amds
Chart
Updates
Op. Systems
EAD
Ext. Users
PLX
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

39. The IDS application framework
Flight Plans
Operat. ATS info
Ground Based C/N/S Systems E.M. Analysis
Radar Tracks
CWPs Radar Maps
RNAV DME/DME Systems E.M. Analysis
Interf. to ATC
(Radar Maps&Tracks)
Interface to Fast Time Simulation
Satellite Based Nav. Systems E.M. Analysis
(Virtual) Flight Inspection
Cockpit Simulator
Aero Projects Database
Flight Inspection Planning & Post-Processing
Encoderss
Flight Procedures
Airspace & Routes
NAVAIDS MAINTENANCE DB
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

40. Conclusions and Recommendations
The increasing use of RNAV routes and approaches/departures increase the challenges of flight inspection teams and cost connected activities
The international rules from ICAO, Eurocontrol, JAA and FAA are asking for increased level of integrity in aeronautical data due to the fact that aircraft flying strongly rely in the data loaded in the navigation DataBase.
This paper has given a short overview of those requirements and has given some snapshots of the solution developed by IDS to meet the though requirements which are asked from the regulators to the air navigation service providers.
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

41. ACKNOWLEDGMENTS
The authors wish to acknowledge ENAV (Italy’s Air Navigation Service Provider) for its support in the AIRNAS system development
And JCAB for the contribution on the DME/DME requirement
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities

42. Thanks for your attention!
Let’s improve your performance with our solutions
QUESTIONS, COMMENTS, SUGGESTIONS, …
The support of analysis tools to flight inspection activities
IFIS 2008, OKC
The support of analysis tools to flight inspection activities