![](media/image1.jpeg){width="3.9569444444444444in" height="1.68125in"}

APMS 3.0 Flight Analyst Guide

August 25, 2004

Revision: 0.5.1

# 

##  

Contents

1\. Introduction [4](#introduction)

1.1. APMS Overview [4](#apms-overview)

1.1.1. Flight Data Importation [4](#flight-data-importation)

1.1.2. Flight Data Analysis [4](#flight-data-analysis)

1.2. Document Scope [5](#document-scope)

1.3. Document Styles [6](#document-styles)

2\. Getting Started [7](#getting-started)

2.1. Start Application [7](#start-application)

2.2. Log In [7](#log-in)

2.3. Select Tool [8](#select-tool)

3\. Morning Report [9](#morning-report)

3.1. Overview [9](#overview)

3.2. Details [10](#details)

3.2.1. Select Analysis Report [10](#select-analysis-report)

3.2.2. View Analysis Summary [12](#view-analysis-summary)

3.2.3. View Flight List [13](#view-flight-list)

3.2.4. View Parameter Traces [14](#view-parameter-traces)

3.2.5. Other Options [15](#other-options)

3.2.6. Validate Atypicality [15](#validate-atypicality)

4\. Data Exploration [16](#data-exploration)

4.1. Overview [16](#overview-1)

4.2. Details [16](#details-1)

4.2.1. Select Flights [16](#select-flights)

4.2.2. Quantify Routine Events [19](#quantify-routine-events)

4.2.3. View Events [20](#view-events)

4.2.4. Load FFD into Viewer [21](#load-ffd-into-viewer)

4.2.5. View Parameter Values Grid [22](#view-parameter-values-grid)

4.2.6. View Flight in GRADE [24](#view-flight-in-grade)

5\. Viewer [25](#viewer)

5.1. Overview [25](#overview-2)

5.2. Details [25](#details-2)

5.2.1. Open FFD File [25](#open-ffd-file)

5.2.2. Add Parameters [27](#add-parameters)

5.2.3. Change Parameter Set [29](#change-parameter-set)

5.2.4. Add Routine Event Markers [30](#add-routine-event-markers)

5.2.5. Position Cursor Marker [31](#position-cursor-marker)

5.2.6. Set Timeline [33](#set-timeline)

5.2.7. Other Options [36](#other-options-1)

6\. Search Pattern (Simple Mode) [37](#search-pattern-simple-mode)

6.1. Overview [37](#overview-3)

6.2. Details [37](#details-3)

6.2.1. Create New Pattern [37](#create-new-pattern)

6.2.2. Create New Module [40](#create-new-module)

6.2.3. Run New Pattern Query [50](#run-new-pattern-query)

6.2.4. Open Existing Pattern Query [53](#open-existing-pattern-query)

6.2.5. Interpret Pattern Results [54](#interpret-pattern-results)

7\. Event Charts [56](#event-charts)

7.1. Overview [56](#overview-4)

7.2. Details [57](#details-4)

7.2.1. Create Page Group [57](#create-page-group)

7.2.2. Add Page to Page Group [59](#add-page-to-page-group)

7.2.3. Add Chart to Page [61](#add-chart-to-page)

7.2.4. Create Query [63](#create-query)

7.2.5. Run Report [68](#run-report)

7.2.6. View Charts [71](#view-charts)

8\. Flight Validation [73](#flight-validation)

8.1. Overview [73](#overview-5)

8.2. Details [74](#details-5)

8.2.1. Select Fleet [74](#select-fleet)

8.2.2. View Flight List [75](#view-flight-list-1)

8.2.3. Filter Flight List [76](#filter-flight-list)

8.2.4. Select Flight [77](#select-flight)

8.2.5. View Special Events & Routine Events
[78](#view-special-events-routine-events)

8.2.6. View Analysis List & Analysis Details
[79](#view-analysis-list-analysis-details)

8.2.7. Validate Selection [80](#validate-selection)

9\. Reports [83](#reports)

9.1. Overview [83](#overview-6)

9.2. Set-up Details [84](#set-up-details)

9.2.1. Log In [84](#log-in-1)

9.2.2. Create User Category [85](#create-user-category)

9.3. Performance Report Details [87](#performance-report-details)

9.3.1. Create New Template [87](#create-new-template)

9.3.2. Create New Report [90](#create-new-report)

9.3.3. View Report [91](#view-report)

9.4. Special Event Report Details [94](#special-event-report-details)

9.4.1. Create New Template [94](#create-new-template-1)

9.4.2. Create New Report [97](#create-new-report-1)

9.4.3. View Report [99](#view-report-1)

10\. Glossary [102](#glossary)

# Introduction

## APMS Overview

The Aviation Performance Measuring System (APMS) is a method---embodied
in software---that uses mathematical algorithms and related procedures
to analyze digital flight data extracted from aircraft flight data
recorders.

APMS consists of an integrated set of tools used to perform two primary
functions:

-   Flight Data Importation

-   Flight Data Analysis

These functions are described below.

### Flight Data Importation

Air carriers store digital flight data on a variety of media including
optical disks and electronic memory devices. These data are regularly
downloaded and processed with the use of commercial flight data
processing software. This commercial software converts the data from
their native storage units into standard engineering units. It also
identifies *exceedance* events in the data and generates standard
reports and statistics characterizing the data. The results of this
processing activity are stored in online data stores of varying formats.
All of this activity by commercial flight data processing software
occurs prior to data importation by APMS.

On a regular basis, APMS data importation tools are used to access the
online data stores created by the commercial flight data processing
software. These tools locate new flight data and perform various
filtering, structuring, signature extraction, compression, and storage
processes.

APMS data importation tools include the *Loader*, *Parameter Editor*,
*Phase Editor*, and *Fleet Editor*.

### Flight Data Analysis

APMS includes tools that permit flight analysis to be performed by both
computers and humans, since both are necessary to produce meaningful
results. The following paragraphs describe how this is accomplished.

#### Computerized Analysis

The computerized analysis process is performed by the *Analysis Engine*.
This tool examines the imported data to determine typical flight
patterns and also identifies flights that do not conform well to any
typical pattern. The Analysis Engine does this by using statistical,
rather than operational, criteria. It ranks atypical flights in order of
their degree of deviation from the norm. The system finds the specific
flight phases that are atypical and identifies the flight parameters
that contributed to the unusual performance. Since the Analysis Engine
accomplishes these various functions without any prior human
specification of normal or operationally interesting flights, it can
reveal unexpected events or trends that could compromise the safety of
flight operations.

#### Human-Guided Analysis

Atypical flights identified by the Analysis Engine are brought to the
attention of airline safety analysts, who use other APMS tools to
determine whether these flights are of operational interest. The
*Morning Report* tool is a key component in the human-guided analysis of
flight data. This tool displays the output of the Analysis Engine.
Because words can often convey more meaning than raw statistics to air
carrier analysts, the Morning Report provides textual descriptions of
the atypical flights identified by the Analysis Engine. The Morning
Report also displays graphical representations of the Analysis Engine's
findings in the form of *parameter traces* and *parameter clouds*. The
latter depict the range of variation commonly observed in the flight
data. This graphical visualization provides a frame of reference against
which parameter traces from atypical flights can be displayed and
visually assessed by human analysts.

In addition to Morning Report, human-guided analysis tools include
*Viewer, Data Exploration*, *Search Pattern*, *Events Charts*, and
*Reports*. Aviation safety analysts use the *Flight Validation* tool to
record their findings.

## Document Scope

Figure 1.1. APMS Main Toolbar

![](media/image2.png){width="6.843055555555556in"
height="1.0208333333333333in"}

This document is written for aviation safety analysts who use APMS to
analyze digital flight data. It contains descriptions of the
human-guided flight analysis tools available in APMS 3.0. Each of these
tools except the Viewer is directly accessible from the **APMS Main
Toolbar** (see Figure 1.1). The Viewer is accessible from within most of
the other tools.

The following flight analysis tools are described in detail:

-   Morning Report

-   Data Exploration

-   Viewer

-   Search Pattern

-   Event Charts

-   Flight Validation

-   Reports

Figure 1.2. Utilities Toolbar

![](media/image3.png){width="6.842361111111111in"
height="0.9138888888888889in"}

The **Utilities Toolbar** (see Figure 1.2) provides access to several
tools that are used primarily by systems administrators to configure
APMS for data importation and to set up user permissions. The
**Utilities Toolbar** also provides access to the Analysis Engine that
is used to perform computer-driven flight analysis. For a description of
the tools in the **Utilities Toolbar**, see the APMS 3.0 System
Administrator's Guide.

## Document Styles

-   **Bold** text is used throughout this document to identify user
    interface features such as windows, buttons, and fields.

-   *Italicized* text is used throughout this document to identify
    APMS-specific terms defined in the Glossary (see Section 10).

# Getting Started

## Start Application

Figure 2.3. APMS Shortcut Icon

![](media/image4.png){width="0.65625in" height="0.8541666666666666in"}

Before using any of the APMS flight analysis tools, flight analysts must
start the application and log in. To begin, click the **APMS Shortcut**
icon (see Figure 2.3) on the computer desktop.

## Log In

Figure 2.4. APMS Login Window

![](media/image5.png){width="4.416666666666667in"
height="2.6458333333333335in"}

To log in, perform the following steps:

-   Select the appropriate user name in the **User** drop-down list.

-   Enter the password in the **Password** text box.

-   Click **Login**.

## Select Tool

Figure 2.5. APMS Main Toolbar

![](media/image2.png){width="6.843055555555556in"
height="1.0208333333333333in"}

In the **APMS Main Toolbar** (see Figure 2.5), click the icon of any
available flight analysis tool.

# Morning Report

## Overview

The Morning Report tool provides textual descriptions and graphical
representations of data imported from *analysis reports*, which are
generated by an APMS utility called the *Analysis Engine*. To understand
the Morning Report tool, it is important to learn more about these
analysis reports.

The Analysis Engine produces analysis reports by comparing data from
newly imported flights with data from earlier, or baseline, flights.
However, only the new flights are listed in the analysis report. New and
existing flights from the same fleet (and, if applicable, from the same
originating or destination airport) are grouped by *phase* to form a
1,000-flight *aggregation*. The computerized analysis determines typical
flight patterns for the aggregation and also identifies phases in the
new flights that do not conform well to any typical pattern. The
Analysis Engine then ranks the atypical flights and phases in order of
their degree of deviation from the norm. The system also identifies the
flight *parameters* that contributed to the unusual performance.

The Morning Report tool allows analysts to view and investigate these
*atypicalities*---flights or phases of flights containing parameter
values that deviate from the group norm. Each atypical flight or flight
phase is ranked from 1 (lowest degree of deviation) to 3 (highest). When
a rank applies to a single flight phase (such as Takeoff or Landing), it
is called a *phase atypicality* rank. When a rank applies to an entire
flight (all combined phases), it is called a *global atypicality* rank.

It's important to note that *Level 3 atypicalities* in the Morning
Report do not necessarily point to safety or quality problems in the
flights or phases in which they appear. Instead, atypicalities should be
considered as starting points for further investigation of potential
problems. Analysts must gather additional flight information (with the
help of other tools in the APMS suite) to validate or invalidate
atypicalities in the Morning Report. For example, an analyst might
invalidate or exempt atypicalities resulting from bad data sensors or
weather-related flight adjustments.

## Details

### Select Analysis Report

Figure 3.6. Start Morning Report Window

![](media/image6.png){width="6.846527777777778in"
height="1.2493055555555554in"}

The **Start Morning Report** window (see Figure 3.6) provides access to
the list of analysis reports.

To view the list of available reports, select **Morning Report\>Choose
Morning Report** in the menu.

Figure 3.7. Morning Report Selector Window

![](media/image7.png){width="5.416666666666667in"
height="4.989583333333333in"}

The **Morning Report Selector** window (see Figure 3.7) contains a list
of the available analysis reports. Note that the list includes the date
that each report was generated by the Analysis Engine tool.

To view a specific report, select it and click **View Morning Report**.

### View Analysis Summary

Figure 3.8. Morning Report Summary Window

![](media/image8.png){width="6.840277777777778in"
height="4.134722222222222in"}

The **Morning Report Summary** window (see Figure 3.8) summarizes the
global and phase atypicalities contained in the report. In this example,
note that there are three Level 3 global atypicalities and four Level 3
phase atypicalities. Also note that Morning Report atypicality levels
can be identified by the following colors:

-   Red---Level 3 (most atypical)

-   Yellow---Level 2

-   Aqua---Level 1 (least atypical)

To view more details about the atypical flights and flight phases in the
report, click **Go to Flight List**.

### View Flight List

Figure 3.9. Morning Report Flight List Window

![](media/image9.png){width="6.840277777777778in"
height="2.8854166666666665in"}

![](media/image10.png){width="0.20833333333333334in"
height="0.19791666666666666in"}The **Morning Report Flight List** window
(see Figure 3.9) lists the flights and phases with atypicalities. The
**Flight** column contains a flight's unique *FFD (Full Flight Data)* or
*SFFD (Scrubbed Full Flight Data)* number. This is the number that the
APMS system uses to track different flights. This window also lists the
processing date, phase, airport origin, airport destination, validation
status, and significant parameters of every flight. Note that a flight's
global atypicality rank appears in the **Level** column and the phase
atypicality rank appears in the **Phase** column. Flights that contain
more than one phase atypicality are preceded with a symbol. To view
other atypical phases in the flight, simply click in any column of the
line.

To view the parameter traces of an atypical phase, select the
appropriate line and then click **Explore Flight**.

**Note:** Atypicalities are computed by phase with other flights in an
*aggregation*, a group of new and existing flights (typically totaling
1,000) used by the Analysis Engine to produce an analysis report.
Low-elevation flight phases (Taxi-out, Takeoff, Low Speed Climb, Low
Speed Descent, Final Approach, Landing, and Taxi-in) are aggregated by
phase, fleet, and airport. High-elevation flight phases (High Speed
Climb, Cruise, and High Speed Descent) are aggregated by phase and fleet
only.

### View Parameter Traces

Figure 3.10. Morning Report Atypicality Analysis Window

![](media/image11.png){width="6.840277777777778in"
height="5.194444444444445in"}

The **Morning Report Atypicality Analysis** window (see Figure 3.10),
displays a flight's parameter trace relative to the combined parameter
traces of other flights in the aggregation. In the example above, the
black line represents the flight's data trace for the selected
parameter. The shaded area , or *parameter cloud*, represents the
combined parameter traces of other flights in the aggregation. When the
cursor is positioned inside the parameter cloud, an information box will
identify the percentage of flights that contributed to that data region.
Click **Typical** to view the combined traces of the most typical
flights (representing 80 percent of the total). Click\
**All** to view the combined traces of all flights in the aggregation.

The **Rationale List** box identifies the most significant
characteristic for every parameter that contributed to the flight's
phase atypicality ranking.

### Other Options

Figure 3.11. Morning Report Atypicality Analysis Window (Partial View)

![](media/image12.png){width="6.841666666666667in"
height="1.7395833333333333in"}

The analyst can obtain additional flight information by clicking one of
the following:

-   The **Flight Info** button links to a table containing the flight's
    numerical parameter values.

-   The **APMS Viewer** button allows the analyst to view all
    significant parameter traces on a single graph.

### Validate Atypicality

Figure 3.12. Morning Report Atypicality Analysis Window (Partial View)

![](media/image13.png){width="6.842361111111111in"
height="1.7354166666666666in"}

The analyst can validate an atypicality by clicking one of the
following:

-   The **Flight Validation** button launches the Flight Validation tool
    (described in Section 7.1 of this document). This tool allows the
    analyst to view and *validate* all phase atypicalities for the
    flight. It also allows the analyst to view and validate any *special
    events* (also known as exceedances) that may have occurred during
    the flight.

-   The **Quick Validation** button allows the analyst to bypass the
    Flight Validation tool to validate an atypicality quickly.

# Data Exploration

## Overview

The Data Exploration tool allows analysts to conduct in-depth research
on a flight. This tool puts several other tools and utilities within
easy reach, including the Viewer, Parameter Editor, and Loader.

## Details

### Select Flights

Figure 4.13. Data Exploration Window (Partial View)

![](media/image14.png){width="6.845833333333333in"
height="1.2291666666666667in"}

To select a group of flights in a fleet, select **Edit\>Select Flights**
in the menu of the **Data Exploration** window (see Figure 4.13).

**Note:** To select only a single flight by its FFD or SFFD
identification number, select **File\>Open FFD** and navigate to the
appropriate file.

Figure 4.14. Select Flights Window

![](media/image15.png){width="3.0in" height="4.976388888888889in"}

In the **Select Flights** window (see Figure 4.14), perform the
following steps:

-   Select the appropriate fleet in the **Fleet** list box.

-   Select the beginning month and year of the query in the **Begin
    Date** drop-down lists.

-   Select the ending month and year of the query in the **End Date**
    drop-down lists.

-   Select the appropriate tail number(s) in the **Available Tail
    Numbers** list.

**Note:** To select multiple tail numbers, hold down the CTRL key and
click the desired items. To quickly select a contiguous block of tail
numbers, hold down the SHIFT key and click the first and last items in
the block.

-   Select flight origin(s) in the **Origin** list box.

**Note:** To select multiple origins, hold down the CTRL key and click
the desired items.

-   Select flight destination(s) in the **Destination** list box.

**Note:** To select multiple destinations, hold down the CTRL key and
click the desired items.

-   To include only those flights that departed one of the selected
    origin airports and also arrived at one of the selected destination
    airports during a single flight, check the **Flight Origin and
    Destination Airports Must Match Selection** box.

**Note:** If this box is not checked, origin and destination will be
uncoupled. In other words, the query will include all flights leaving
the origin airport(s), regardless of destination. It also will include
all flights arriving at the destination airport(s), regardless of
origin.

-   When finished, click **OK**.

Figure 4.15. Data Exploration Window

![](media/image16.png){width="6.841666666666667in"
height="2.4270833333333335in"}

The **Data Exploration** window (see Figure 4.15) displays summary
information about all of the flights that match the flight selection
criteria.

The Data Exploration tool now provides many analysis options for
conducting additional research. Before choosing an analysis option,
first select a single flight.

### Quantify Routine Events

Figure 4.16. Data Exploration Window

![](media/image17.png){width="6.846527777777778in"
height="2.411111111111111in"}

To quantify the *routine events* for a specific flight, select
**Edit\>Validate Data** in the menu of the **Data Exploration** window
(see Figure 4.16).

Figure 4.17. Data Exploration Window

![](media/image18.png){width="6.844444444444444in"
height="2.201388888888889in"}

In the **Data Exploration** window (see Figure 4.17), notice that the
**Problem Description**\
column now appears. This column lists the number of routine events
identified in the flight. Bad or missing data will result in flights
with fewer identified routine events.

### View Events

Figure 4.18. Data Exploration Window

![](media/image19.png){width="6.844444444444444in"
height="2.201388888888889in"}

To view a list of all routine events and *special events* associated
with a flight, select **Events\>All Events** in the menu of the **Data
Exploration** window (see Figure 4.18).

Figure 4.19. Flight Information Window

![](media/image20.png){width="4.872222222222222in"
height="3.814583333333333in"}

The **Flight Information** window (see Figure 4.19) provides summary
information, *phases*, special events, routine events, and weather
associated with the flight. The analyst also can use this window to
access the *Viewer* or to obtain flight information from other FFDs or
SFFDs.

### Load FFD into Viewer

Figure 4.20. Data Exploration Window

![](media/image21.png){width="6.84375in" height="2.204861111111111in"}

To load a flight in the Viewer, select **Viewer\>Load FFD into Viewer**
in the menu of the **Data Exploration** window (see Figure 4.20).

Figure 4.21. Viewer Window

![](media/image22.png){width="6.846527777777778in"
height="4.670138888888889in"}

The **Viewer** window (see Figure 4.21) now displays a graphical
representation of parameter values recorded during the selected flight.
For a complete description of the Viewer, see Section 5.

### View Parameter Values Grid

Figure 4.22. Data Exploration Window

![](media/image23.png){width="6.844444444444444in"
height="2.201388888888889in"}

To view a table containing the flight's parameter values, select
**Grid\>Go to Grid** in the menu of the **Data Exploration** window (see
Figure 4.22).

Figure 4.23. Flight Data Table

![](media/image24.png){width="6.108333333333333in"
height="5.134027777777778in"}

The **Flight Data Table** (see Figure 4.23) lists the value or values
for every parameter in a given parameter set. To change the parameter
set, simply make a new selection in the parameter set drop-down list ,
and then click **Go**.

### View Flight in GRADE

Figure 4.24. Data Exploration Window

![](media/image25.png){width="6.84375in" height="2.204861111111111in"}

To view a flight in the Graphical Airspace Design Environment (GRADE),
select **Grade\>Go to Grade** in the menu of the **Data Exploration**
window (see Figure 4.24). GRADE, developed by ATAC Corp., is a PC-based,
four-dimensional computer tool for displaying, analyzing, designing, and
evaluating air traffic operations.

# Viewer

## Overview

The Viewer is a powerful tool that allows analysts to study the
interactions between significant parameters for any flight at any given
time during the flight. The Viewer can be accessed only from other APMS
tools, including Morning Report, Data Exploration, and Flight
Validation.

The Viewer produces a graphical representation of multiple parameter
values in a single window. These parameter traces share a common
timeline. The Viewer can display parameter traces for any parameter
recorded in a flight's *FFD (Full Flight Data)* or *SFFD (Scrubbed Full
Flight Data)* file. The Viewer also can display a flight's *routine
events* (regular flight occurrences such as Gear Up Takeoff and Flaps
Down Approach).

Analysts use the Viewer as an analytical tool to help validate or
invalidate *atypicalities* displayed in the Morning Report tool.

## Details

### Open FFD File

Figure 5.25. Viewer Window (Partial View)

![](media/image26.png){width="6.846527777777778in"
height="1.4805555555555556in"}

As mentioned above, the Viewer can be accessed only from other APMS
tools. When initially opened, the **Viewer** window displays the FFD or
SFFD file that has been selected by the active tool.

Once the **Viewer** window has been opened, it can be used to open
directly any other available FFD or SFFD file. To open an FFD or SFFD
file in the **Viewer** window, select **File\>Open FFD File** in the
menu and then navigate to the directory containing the appropriate file.

Figure 5.26. Viewer Window

![](media/image27.png){width="6.846527777777778in"
height="4.670138888888889in"}

The **Viewer** window (see Figure 5.26) now displays a graphical
representation of parameter values recorded during the selected flight.
Notice that the window contains the following items:

-   A parameter box on the left-hand side that contains a color-coded
    list of the charted flight parameters and their numerical parameter
    values at the position of the cursor.

-   A large graph area containing separate, color-coded traces of each
    flight parameter, displayed horizontally.

-   Routine event markers that vertically intersect the parameter traces
    at various intervals.

-   A combined events locator & timeline scroll bar at the bottom of the
    window.

### Add Parameters

Figure 5.27. Viewer Window (Partial View)

![](media/image28.png){width="3.5in" height="2.9791666666666665in"}

Analysts can easily add new parameters to the graph area. To begin,
simply right-click inside the parameter box and select **Add
Parameter**.

Figure 5.28. Select New Parameters Window

![](media/image29.png){width="3.75in" height="5.15625in"}

In the **Select New Parameters** window (see Figure 5.28), select a
parameter in the **Generic Name** list , and then click **OK**.

**Note:** To select multiple parameters, hold down the CTRL key and
click the desired items. To quickly select a contiguous block of
parameters, hold down the SHIFT key and click the first and last items
in the block.

### Change Parameter Set

Figure 5.29. Viewer Window (Partial View)

![](media/image30.png){width="6.8493055555555555in"
height="1.4493055555555556in"}

Analysts can easily change the active parameter set. Simply select any
available set in the parameter set drop-down list.

### Add Routine Event Markers

Figure 5.30. Viewer Window (Partial View)

![](media/image31.png){width="2.7416666666666667in" height="6.08125in"}

Analysts also can add routine event markers to the graph area. Simply
click the left panel of the events locator bar to display a list of all
routine events (see Figure 5.30). The checked items indicate routine
events with active markers. Click items in the list to add new routine
event markers.

### Position Cursor Marker

Figure 5.31. Viewer Window (Partial View)

![](media/image32.png){width="6.845138888888889in"
height="1.4069444444444446in"}

Analysts can click anywhere inside the graph area to produce a moveable
cursor marker. The **Time at Cursor from Liftoff** and **Time at Cursor
to Touchdown** display boxes at the top of the Viewer window (see Figure
5.31) indicate the position of the cursor marker relative to the time of
liftoff and touchdown. The **In View** display box indicates the number
of hours and minutes of flight data currently visible in the graph area.
In the example above, the display boxes indicate that the cursor marker
is at the liftoff position---exactly 4 hours, 5 minutes, and 8 seconds
from touchdown---and that the entire flight is being displayed in the
graph area.

Figure 5.32. Viewer Window

![](media/image33.png){width="6.846527777777778in"
height="4.670138888888889in"}

To reposition the cursor, click and hold while dragging it to a new
position. In Figure 5.32, note that the cursor marker is now positioned
40 minutes from touchdown and near to the End Cruise (CruE) routine
event marker. Also note that numerical values in the parameter list box
have changed for all parameters to reflect their values at this new
cursor position.

Figure 5.33. Viewer Window (Partial View)

![](media/image34.png){width="2.71875in" height="5.454166666666667in"}

To position the cursor over a routine event marker, simply click the
appropriate event flag in the events locator at the bottom of the
window. In Figure 5.33, note that the cursor marker now is positioned
directly over the End Cruise (CruE) routine event marker and that the
cursor marker now is displayed as a white line.

### Set Timeline

Figure 5.34. Viewer Window (Partial View)

![](media/image35.png){width="6.847222222222222in"
height="0.8756944444444444in"}

Analysts can zoom in on a portion of the flight by using the timeline
scroll bar at the bottom of the window (see Figure 5.34). For example,
to zoom in on the End Cruise portion of the flight, click and hold on
the left scroll handle, and then drag the scroll handle to the right.
Note that the time in the **Time from Liftoff to Left Scroll Handle**
display box changes to reflect the new position of the left scroll
handle.

Figure 5.35. Viewer Window

![](media/image36.png){width="6.846527777777778in"
height="4.670138888888889in"}

In Figure 5.35, note that the **In View** display box now indicates that
only 34 minutes and 20 seconds of flight data are visible in the graph
area. Also note that this same amount of time (34 minutes and 20
seconds) is represented by the space between the left scroll handle and
the right scroll handle.

Figure 5.36. Viewer Window

![](media/image37.png){width="6.846527777777778in"
height="4.670138888888889in"}

Analysts can preselect a time slice for viewing data. This is done by
manipulating the distance between the scroll handles. In Figure 5.36,
note that the **In View** display box reveals that the distance between
the left scroll handle and the right scroll handle represents exactly 5
minutes. Now that the time slice has been set, analysts can use the
following two methods to view data:

-   Sliding: Click and hold on the space between the scroll handles,
    then drag the scroll bar to the appropriate event or location.

-   Event centering: Click on the appropriate event flag in the events
    locator at the bottom of the window to center on that event.

### Other Options

Figure 5.37. Viewer Window (Partial View)

![](media/image38.png){width="6.845138888888889in"
height="1.4770833333333333in"}

Other options available in the Viewer include the following:

-   **PowerPoint** : Click this button to automatically load the current
    Viewer window into a PowerPoint presentation.

-   **Reset View** : Click this button to reset the Viewer window to the
    default settings.

-   **Show Grid** : Click this button to generate a flight data table
    containing all of the parameter values for the flight.

-   **Grade\>View Flight in Grade** : Select this menu option to launch
    the Graphical Airspace Design Environment (GRADE). GRADE, developed
    by ATAC Corp., is a PC-based, four-dimensional computer tool for
    displaying, analyzing, designing, and evaluating air traffic
    operations.

# Search Pattern (Simple Mode)

## Overview

The Search Pattern tool is used to search *FFD* or *SFFD* files for
*patterns* in flight data. By identifying patterns associated with
specific adverse events in a flight, analysts can better understand the
causes of these events and, in turn, take actions to prevent them from
occurring in the future.

Each pattern consists of one or more *modules*, or user-defined flight
events. Each module is composed of at least one *parameter condition*,
an equation that includes a specific flight parameter, an operator, and
a numeric value (such as N1_Eng_1 ≤ 45). Each parameter condition in the
module must be applied to an *event frame*, a selected period of time in
a flight.

For example, to locate all flights that landed with an unstable
approach, an analyst might want to create a pattern that contains one or
more modules for flap position vs. airspeed, one module for high speed
at landing, one module for low power on approach, and another module for
excessive glide slope. Each module would be a piece of the pattern that
defines an unstable approach. In this example, the module for high speed
at landing would identify excessive airspeed parameters (the parameter
conditions) from the start of the final approach phase until touchdown
(the event frame).

When an analyst runs a pattern, the Search Pattern tool queries the
database and returns a list of flights that match any of the modules in
the pattern. Analysts then can conduct additional research on the
characteristics of matching flights or refine the pattern definition for
future queries. Analysts also can make use of other APMS tools for
further analysis.

## Details

### Create New Pattern

Figure 6.38. Search Pattern Window (Partial View)

![](media/image39.png){width="5.13125in" height="1.6305555555555555in"}

To begin a new pattern, select **File\>Pattern Management\>Simple** in
the menu of the **Search Pattern** window (see Figure 6.38).

**Note:** The Search Pattern tool includes a simple mode and an advanced
mode. This document describes only the simple mode.

Figure 6.39. Pattern Wizard Window

![](media/image40.png){width="6.84375in" height="3.442361111111111in"}

The **Pattern Wizard** window (see Figure 6.39) lists all previously
created patterns in the **Available Patterns** drop-down list. The
**Available Modules** list box lists all previously created modules. It
also lists routine events (when the **Include Routine Events** checkbox
is selected).

**Note:** A pattern consists of one or more modules. A module is a
user-defined flight event composed of one or more parameter conditions
(such as N1_Eng_1_corr ≤ 45), applied to a specific time frame (such as
Ten Minutes before Touchdown).

Figure 6.40. Pattern Wizard Window (Partial View)

![](media/image41.png){width="5.894444444444445in"
height="1.3645833333333333in"}

To create a pattern, select **New\>Pattern** in the menu of the
**Pattern Wizard Window** (see Figure 6.40).

Figure 6.41. Editor Window

![](media/image42.png){width="4.479166666666667in" height="1.46875in"}

In the **Editor** window (see Figure 6.41), enter a name for the new
pattern in the text field , and then click **OK**.

Figure 6.42. Pattern Wizard Window

![](media/image43.png){width="6.84375in" height="3.442361111111111in"}

In the **Pattern Wizard** window (see Figure 6.42), select the new
pattern in the **Available Patterns** drop-down list . Note that the new
pattern is only an empty shell at this stage, as evidenced by the empty
**Pattern Details** list box. In other words, the new pattern does not
yet contain any pattern-defining modules.

#### Add Existing Modules to New Pattern

Figure 6.43. Pattern Wizard Window

![](media/image44.png){width="6.84375in" height="3.452777777777778in"}

To add existing modules to a new pattern, simply drag and drop items
from the **Available Modules** list box to the **Pattern Details** list
box in the **Pattern Wizard** window (see Figure 6.43).

To view the details (parameter conditions and event frame) associated
with a particular module, simply click on an item in the **Available
Modules** list box. The details will appear in the **Module
Description** list box.

### Create New Module

Figure 6.44. Pattern Wizard Window (Partial View)

![](media/image45.png){width="5.925in" height="1.34375in"}

To create a new module, select **New\>Module** in the menu of the
**Pattern Wizard** window (see Figure 6.44).

Figure 6.45. Define New Module (Description) Window

![](media/image46.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

In the **Define New Module (Description)** window (see Figure 6.45),
perform the following steps:

-   Type a name for the module in the **Name** field.

-   Type an abbreviation for the module in the **Abbreviation** field.

-   Specify the risk level in the **Risk Index** field.

**Note:** The Risk Index is an analyst-assigned risk level for each
module in a pattern. This numerical value allows analysts to weight the
relative degree of risk from the combined parameter conditions included
in the module. A larger number indicates a greater risk. The Risk Index
is used to compute the RIN for every flight that matches a pattern.
Currently, there is no default Risk Index value range in APMS.

-   When finished, click the **\>\>** button or the **When to Look**
    tab.

Figure 6.46. Define New Module (When To Look) Window

![](media/image47.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

In the **Define New Module (When to Look)** window (see Figure 6.46),
perform the following steps:

-   Click a radio button for one of the following event frame
    categories:

    -   **Defined Phases:** Contains only APMS-defined phases (such as
        Cruise).

    -   **Defined Event Frames:** Contains all previously used event
        frames, including custom time periods created in the advanced
        mode of Search Pattern.

    -   **User Defined:** Contains routine event markers (such as Taxi
        Out)

**Note:** An event frame is a selected moment or span of time in a
flight. An event frame can be an APMS-defined phase (such as Cruise), a
user-defined time period based on routine event markers (such as Taxi
Out to Liftoff), or a custom time period created in the advanced mode of
Search Pattern (such as 1500 ft AFE Approach to Touchdown). The amount
of time represented by an event frame can be as short as a single second
(such as Center of Flight) or as long as the entire flight.

-   Select the appropriate event frame in the active drop-down list. If
    using the **User Defined** category, select a routine event in each
    of the two drop-down lists.

-   When finished, click the **\>\>** button or the **What to Look For**
    tab.

Figure 6.47. Define New Module (What To Look For) Window

![](media/image48.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

In the **Define New Module (What to Look For)** window (see Figure
6.47), click **Add\
Condition**.

#### Add Existing Condition to New Module

Figure 6.48. Available Conditions Window

![](media/image49.png){width="4.666666666666667in"
height="3.8229166666666665in"}

The **Available Conditions** window (see Figure 6.48), provides a list
of all previously created parameter conditions. To add an existing
condition to the module, simply click a condition in the\
list , and then click **OK**.

Figure 6.49. Define New Module (What To Look For) Window

![](media/image50.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

Notice that the added condition now appears in the **Define New Module
(What to Look For)** window (see Figure 6.49).

#### Create New Condition

Figure 6.50. Define New Module (What To Look For) Window

![](media/image50.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

To create a new condition, click **Add Condition** in the **Define New
Module (What to Look For)** window (see Figure 6.50).

Figure 6.51. Available Conditions Window

![](media/image51.png){width="4.666666666666667in" height="3.8125in"}

Position the cursor inside the **Available Conditions** window (see
Figure 6.51), right-click, and then select **New**.

**Note:** Once a condition has been created, it cannot be deleted in the
simple mode of Search Pattern. To delete a condition, use the advanced
mode.

Figure 6.52 Create New Condition Window

![](media/image52.png){width="4.729166666666667in"
height="1.5520833333333333in"}

In the **Create New Condition** window (see Figure 6.52), perform the
following steps:

-   Select a parameter from the drop-down list.

**Note:** *Derived parameters* are not available in the simple mode of
Search Pattern. To create a new condition based on derived parameters,
use the advanced mode.

-   Select an operator from the drop-down list.

-   Type a value into the text field.

-   Click **OK**.

#### Add Second Condition to New Module

Figure 6.53. Available Conditions Window

![](media/image53.png){width="4.666666666666667in"
height="3.8229166666666665in"}

When adding a second condition to a module, the analyst is required to
join them by setting the condition logic. To add a second condition to
the module, select the condition in the list and click **OK** in the
**Available Conditions** window (see Figure 6.53).

Figure 6.54. Set Condition Logic Window

![](media/image54.png){width="4.5625in" height="1.8854166666666667in"}

The **Set Condition Logic** window (see Figure 6.54) appears only when a
second condition has been added. Even though multiple conditions can be
added to a module, the module logic is selected only one time. Click
**AND** to require that all of the module conditions exist in order to
generate a query match. Click **OR** to require that only one of the
module conditions exist in order to generate a query match.

#### Save New Module

Figure 6.55. Define New Module (What To Look For) Window

![](media/image55.png){width="4.7965277777777775in"
height="4.4215277777777775in"}

Selected conditions and logic will appear in the display area of the
**Define New Module (What to Look For)** window (see Figure 6.55). When
all conditions have been added, click\
**Done**.

Figure 6.56. Pattern Wizard Window

![](media/image56.png){width="6.84375in" height="3.442361111111111in"}

In the **Pattern Wizard** window (see Figure 6.56), the new module now
appears in the **Available Modules** list box. The module now can be
added to a pattern, as described previously in Section 6.2.1, Create New
Pattern.

**Note:** Once a module has been created, it cannot be edited in the
simple mode of Search Pattern. To edit a module, use the advanced mode
of Search Pattern.

### Run New Pattern Query

Figure 6.57. Search Pattern Window (Partial View)

![](media/image57.png){width="6.226388888888889in" height="1.6875in"}

Analysts can query the APMS database to find flights that match a
pattern. To run a new pattern query, click **Run Pattern** in the
**Search Pattern** window (see Figure 6.57).

Figure 6.58. Run Search Pattern Window

![](media/image58.png){width="4.910416666666666in"
height="5.198611111111111in"}

In the **Run Search Pattern** window (see Figure 6.58), perform the
following steps:

-   Select the appropriate fleet in the **Fleets** list box.

-   Select the beginning month and year of the query in the **Begin
    Date** drop-down lists.

-   Select the ending month and year of the query in the **End Date**
    drop-down lists.

-   Select the appropriate tail number(s) in the **Available Tail
    Numbers** list.

**Note:** To select multiple tail numbers, hold down the CTRL key and
click the desired items. To quickly select a contiguous block of tail
numbers, hold down the SHIFT key and click the first and last items in
the block.

-   Select flight origin(s) in the **Origin** list box.

**Note:** To select multiple origins, hold down the CTRL key and click
the desired items.

-   Select flight destination(s) in the **Destination** list box.

**Note:** To select multiple destinations, hold down the CTRL key and
click the desired items.

-   By default, searches will locate only flight tail numbers that
    departed the selected origin airport(s) and arrived at the selected
    destination airport(s) during a single flight. To search for all
    tail numbers leaving the origin airport(s) regardless of
    destination(s), and all tail numbers arriving at the destination
    airport(s) regardless of origin airport(s), uncheck the **Flights
    Origin and Destination** checkbox.

-   Select the appropriate pattern in the pattern list box.

-   Click **Go**.

Figure 6.59. Search Pattern Progress Window

![](media/image59.png){width="3.5833333333333335in"
height="3.3229166666666665in"}

The **Search Pattern Progress** window (see Figure 6.59) tracks the
query progress and identifies the flights matching the properties of the
selected pattern.

The query results will appear when processing is complete. See Section
6.2.5, Interpret Pattern Results, to learn more about interpreting the
results.

### Open Existing Pattern Query

Figure 6.60. Search Pattern Window (Partial View)

![](media/image57.png){width="6.395138888888889in" height="1.6875in"}

In addition to running new pattern queries, the analyst also can access
the results of prior pattern queries. To open an existing query, click
**Pattern Results** in the **Search Pattern** window (see Figure 6.60).

Figure 6.61. Run Patterns Window

![](media/image60.png){width="3.6458333333333335in"
height="3.8020833333333335in"}

In the **Run Patterns** window (see Figure 6.61), select a pattern query
, and then click\
**View**. The query results will appear immediately. See Section 6.2.5,
Interpret Pattern Results, to learn more about interpreting the results.

### Interpret Pattern Results

The **Search Pattern** window (see Figure 6.62) allows analysts to view
a complete list of FFDs or SFFDs that match at least one module in the
pattern. This window contains two tabbed pages: **Pattern Results** and
**Individual Results**. These options are described below.

#### Pattern Results

Figure 6.62. Search Pattern Window (Pattern Results Table)

![](media/image61.png){width="6.839583333333334in" height="1.59375in"}

Analysts use the **Pattern Results** table (see Figure 6.62) to
determine the flights they wish to examine in more detail. The **Pattern
Results** table contains a row for every matching flight. Each row
begins with the **Flight** column, which contains the flight's unique
FFD or SFFD number. The table also contains a separate column for every
module associated with the applicable pattern. The numbers in these
columns represent the time, in seconds, at which the module occurred
during the flight. The **RIN** column contains an APMS-computed number
that is displayed for every flight that matches a pattern. The *RIN* is
the sum of the risk indices for the modules that occurred during a
flight. A larger RIN indicates a greater risk. The RIN allows analysts
to quickly sort the results based on the severity of the modules that
occurred during a flight.

#### Individual Results

Figure 6.63. Search Pattern Window (Individual Results Tab)

![](media/image62.png){width="6.839583333333334in" height="1.7875in"}

The **Individual Results** table, (see Figure 6.63) summarizes each
module that occurred in a specific flight. In addition to the
information available in the **Pattern Results** table, the **Individual
Results** table contains a **Duration** column. This column lists the
duration, in seconds, of a given module.

To obtain additional information about a flight, right-click on the
appropriate record, then select **Flight Information**.

Figure 6.64. Flight Information Window

![](media/image63.png){width="4.872222222222222in"
height="3.814583333333333in"}

The **Flight Information** window (see Figure 6.64) provides summary
information, *phases*, *special events*, *routine events*, and weather
associated with the flight. The analyst also can use this window to
access the *Viewer* or to obtain flight information from other FFDs or
SFFDs. If research indicates that the events associated with a flight
contain bad data, the analyst can use the **Set Bad Data** drop-down
list in the **Summary** tab to mark the data as good or bad. The analyst
can set data markers for a single flight or for all flights associated
with an aircraft tail number.

**Note:** Flights that have been flagged with a bad data marker will not
be used as baseline flights for computing atypicality. In other words,
the Analysis Engine will not include these flights in an *aggregation*
used to determine typical flight patterns.

# Event Charts

## Overview

The Event Charts tool displays report pages containing routine event
charts for a selected group of flights. Each event chart is associated
with one *parameter* and uses *routine events* to plot the parameter
distributions. The charts contained on a report page allow an analyst to
evaluate and compare parameter distributions at selected routine events
within a group of flights.

Before generating and viewing report pages, the flight analyst must
first create and define the following entities:

-   **Page Group:** Category-specific container for pages. Parent
    directory in tree structure. Created in the Page Manager box.

-   **Page:** Category-specific container for charts. Defines the
    routine events, page title, and page layout for all associated
    charts. Sub-level directory of *page group* parent. Created and
    defined in the Page Manager box.

-   **Chart:** Defines the parameter, chart style, chart title, and axis
    limits for a single chart. Sub-level directory of *page* parent.
    Created and defined in the Page Manager box.

-   **Query Folder:** Category-specific container for queries. Parent
    directory in tree structure. Created in the Queries box.

-   **Query:** Defines the query name, fleet(s), begin date, end date,
    tail number(s), origin airport(s), and destination airport(s) for a
    single query. Sub-level directory of *query folder* parent. Created
    and defined in the Queries box.

## Details

### Create Page Group

Figure 7.65. Event Charting Window

![](media/image64.png){width="6.842361111111111in"
height="3.477777777777778in"}

To create a page group, click the **Page Manager** tab in the **Event
Charting** window (see Figure 7.65).

Figure 7.66. Event Charting Window

![](media/image65.png){width="6.848611111111111in"
height="3.3319444444444444in"}

In the **Event Charting** window (see Figure 7.66), perform the
following steps:

-   Position the cursor inside the white area of the **Page Manager**
    box.

-   Right-click the mouse.

-   Click **Add Group** in the menu box.

Figure 7.67. Page Group Name Window

![](media/image66.png){width="3.9791666666666665in"
height="1.3958333333333333in"}

In the **Page Group Name** window (see Figure 7.67), enter a name for
the new page group in the text field , and then click **OK**.

### Add Page to Page Group

Figure 7.68. Event Charting Window

![](media/image67.png){width="6.848611111111111in"
height="3.3319444444444444in"}

To add a page to a page group, click the **Page Manager** tab in the
**Event Charting** window (see Figure 7.68), and then perform the
following steps:

-   In the **Page Manager** box, click the page group that will contain
    the new page.

-   Right-click the mouse.

-   Click **Add Page** in the menu box.

Figure 7.69. Page Properties Window

![](media/image68.png){width="4.8125in" height="3.5in"}

In the **Page Properties** window (see Figure 7.69), perform the
following steps:

-   Enter a name for the new page in the **Page Name** text field.

-   Click on a pertinent routine event in the **Routine Events** list.

-   Click the **\>** button.

-   Select additional routine events in the **Routine Events** list, as
    necessary.

-   When finished, click **OK**.

### Add Chart to Page

Figure 7.70. Event Charting Window

![](media/image69.png){width="6.848611111111111in"
height="3.3319444444444444in"}

To add a chart to a page, click the **Page Manager** tab in the **Event
Charting** window (see Figure 7.70), and then perform the following
steps:

-   In the **Page Manager** box, click the page that will contain the
    new chart.

-   Right-click the mouse.

-   Click **Add Chart** in the menu box.

Figure 7.71. Chart Properties Window

![](media/image70.png){width="4.111111111111111in"
height="5.226388888888889in"}

In the **Chart Properties** window (see Figure 7.71), perform the
following steps:

-   Enter a name for the new chart in the **Chart Title** text field.

-   Enter a display name for the new chart in the **Display Title** text
    field.

-   Select a chart type (spline or histogram) in the **Chart Type**
    drop-down list.

-   Select the appropriate parameter in the **Parameter Name** drop-down
    list.

-   Enter the appropriate values in the **Min Bin Value**, **Max Bin
    Value**, and **Bin Width**\
    fields.

**Note:** When charting a parameter that is unfamiliar, simply make a
rough estimate when first entering minimum and maximum bin values. If
necessary, come back and adjust the values after viewing the chart.

-   Click **Re-calculate Axis Labels**.

-   To allow the creation of extra bins to collect flights with values
    less than the Min Bin Value and greater than the Max Bin Value,
    click the **Can Underflow** and **Can Overflow**\
    boxes.

**Note:** When the **Can Underflow** and **Can Overflow** boxes are
*not* checked, flights with values less than the Min Bin Value and
greater than the Max Bin Value are placed in the nearest available bins.

-   When finished, click **Save**.

### Create Query

Figure 7.72. Event Charting Window

![](media/image71.png){width="6.842361111111111in"
height="3.477777777777778in"}

To create a query, click the **Queries** tab in the **Event Charting**
window (see Figure 7.72).

Figure 7.73. Event Charting Window

![](media/image72.png){width="6.842361111111111in"
height="3.477777777777778in"}

In the **Event Charting** window (see Figure 7.73), perform the
following steps:

-   Position the cursor inside the white area of the **Queries** box.

-   Right-click the mouse.

-   Select **Add Folder\>Root Folder** in the menu box.

Figure 7.74. Event Charting Window

![](media/image73.png){width="6.842361111111111in"
height="3.477777777777778in"}

In the **Event Charting** window (see Figure 7.74), perform the
following steps:

-   Click the newly created folder in the **Queries** box.

**Note:** The query folder can be given a new name at any time. To do
this, simply double-click on the folder title and enter an appropriate
name.

-   Right-click the mouse.

-   Select **Add Query** in the menu box.

Figure 7.75. Flight Query Data Selection Window

![](media/image74.png){width="4.0in" height="5.766666666666667in"}

In the **Flight Query Data Selection** window (see Figure 7.75), perform
the following steps:

-   Enter a name for the new query in the **Query Name** text field.

-   Select the appropriate fleet in the **Fleet** list.

-   Select the appropriate starting month and year in the **Begin Date**
    drop-down lists.

**Note:** By default, this date will reflect the earliest month for
which there is data for the selected fleet.

-   Select the appropriate ending month and year in the **End Date**
    drop-down lists.

**Note:** By default, this date will reflect the latest month for which
there is data for the selected fleet.

-   Select the appropriate tail number(s) in the **Available Tail
    Numbers** list.

**Note:** To select multiple tail numbers, hold down the CTRL key and
click the desired items. To quickly select a contiguous block of tail
numbers, hold down the SHIFT key and click the first and last items in
the block. To quickly select all tail numbers, click the **Select All
Tail Numbers** box.

-   Select the appropriate origin airport(s) in the **Origin** list.

**Note:** To select multiple origin airports, hold down the CTRL key and
click the desired items. To quickly select all airports, click the
**Select All** box.

-   Select the appropriate destination airport(s) in the **Destination**
    list.

**Note:** To select multiple destination airports, hold down the CTRL
key and click the desired items. To quickly select all airports, click
the **Select All** box.

-   To include only those flights that departed one of the selected
    origin airports and also arrived at one of the selected destination
    airports during a single flight, check the **Flight Origin and
    Destination Airports Must Match Selection** box.

**Note:** If this box is not checked, origin and destination will be
uncoupled. In other words, the query will include all flights leaving
the origin airport(s), regardless of destination. It also will include
all flights arriving at the destination airport(s), regardless of
origin.

-   When finished, click **OK**.

### Run Report

Figure 7.76. Event Charting Window

![](media/image64.png){width="6.842361111111111in"
height="3.477777777777778in"}

To run a report and view charts, click the **Page Manager** tab in the
**Event Charting** window (see Figure 7.76).

Figure 7.77. Event Charting Window

![](media/image75.png){width="6.842361111111111in"
height="3.477777777777778in"}

In the **Event Charting** window (see Figure 7.77), perform the
following steps:

-   Click the thumbnail icon in the **Page Manager** box.

**Note:** The thumbnail icon should now be pointing down to indicate
that the **Page Manager** box is locked on the page.

-   Click the **Queries** tab.

-   Click the thumbnail icon in the **Queries** box.

Figure 7.78. Event Charting Window

![](media/image76.png){width="6.847916666666666in"
height="2.9131944444444446in"}

In the **Event Charting** window (see Figure 7.78), perform the
following steps:

-   In the **Queries** box, check the tick box beside the folders (to
    include all queries in the folders) or individual queries to be
    included in the report.

-   In the **Page Manager** box, click the appropriate page group (to
    include all existing charts for every page in the group), page (to
    include all existing charts for that page), or individual chart to
    be displayed.

-   Click the thumbnail icon in the **Queries** box to dock the box.

-   Click the thumbnail icon in the **Page Manager** box to dock the
    box.

**Note:** Docking the **Queries** and **Page Manager** boxes leaves more
room to render the charts.

-   Click **Run Report**.

### View Charts

Figure 7.79. Event Charting Window

![](media/image77.png){width="6.843055555555556in"
height="5.554861111111111in"}

In the **Event Charting** window (see Figure 7.79), choose any of the
following options:

-   To export chart(s), select **File\>Export\>PowerPoint** or
    **File\>Export\>Excel** in the\
    menu.

-   To zoom in on a single chart, right-click inside the chart and then
    select **Zoom Chart**.

**Note:** This feature operates as a toggle. To return to the default
view, simply click **Zoom Chart** again.

-   To produce separate charts for each routine event, right-click
    inside the chart and then select **Split Chart** in the menu box.

-   To produce a list of all flights occupying a specific data point,
    right-click on the data point and then select **Chart Data\>Flights
    in Data Exploration** in the menu box.

-   To produce a table that contains the total number of flights in each
    bin for every routine event, right-click inside the chart and then
    select **Chart Data\>Raw Data Counts** in the menu\
    box.

-   To produce and download an image file of a chart, click on the
    appropriate chart and then select **Save Chart Image to File ...**
    in the menu box.

-   To quickly edit the properties of a chart, click on the appropriate
    chart and then select **Edit Chart** in the menu box.

# Flight Validation

## Overview

The Flight Validation tool allows a flight analyst to view all *special
events*, *routine events*, and *atypicalities* associated with a flight
and to *validate* or *invalidate* the record based on additional
research. The analyst can filter the results to view only records with
specific characteristics. After researching an event or atypicality, the
analyst can produce a validation form and select the appropriate
validation status.

## Details

### Select Fleet

Figure 8.80. Flight Validation Window

![](media/image78.png){width="6.839583333333334in"
height="5.207638888888889in"}

The flight analyst first must select a fleet in the **Flight
Validation** window (see Figure 8.80). To do this, select a fleet in the
**Fleet** drop-down list , and then click **Refresh Flight List**.

### View Flight List

Figure 8.81. Flight Validation Window

![](media/image79.png){width="6.838888888888889in"
height="5.206944444444445in"}

Once a fleet is selected, the **Flight List** box is populated with
summary flight information in the **Flight Validation** window (see
Figure 8.81). To search for a specific flight that is not visible, click
**Page Down**.

### Filter Flight List

Figure 8.82 Flight Validation Window (Partial View)

![](media/image80.png){width="6.838888888888889in"
height="1.7993055555555555in"}

Analysts can filter the flight list to display only those records that
match specific categories. By marking the check boxes next to
**Actions**, **Levels**, and **Status**, in the **Flight Validation**
window (see Figure 8.82), the drop-down lists are enabled (see Figure
8.83).

Figure 8.83 Filters (Modified View)

![](media/image81.png){width="6.847222222222222in"
height="2.058333333333333in"}

The **Actions** list allows the analyst to restrict the view to only
records coded with a particular action item (such as Investigation or
Maintenance). The options in this list correspond with the actions
options available in the **Validation** window (see Figure 8.90). (The
**Validation** window is described in greater detail in Section 8.2.7,
Validate Selection.)

The **Levels** list allows the analyst to restrict the view to only
records that contain special events and atypicalities at or above the
selected level. For example, to restrict the view to only mid-severity
Level 2 items and high-severity Level 3 items, select **2**.

**Note:** Level 0 items are low-priority special events identified by
SAGEM Avionics, a company that preprocesses digital flight data.

The **Status** list allows the analyst to restrict the view to only
records coded with a particular validation status (such as Confirmed or
Pending). The status options in this list also correspond with the
validation status options available in the **Validation** window (see
Figure 8.90). (The **Validation** window is described in greater detail
in Section 8.2.7, Validate Selection.)

### Select Flight

Figure 8.84. Flight Validation Window

![](media/image82.png){width="6.838888888888889in"
height="5.206944444444445in"}

In the **Flight Validation** window (see Figure 8.84), click on a flight
to select it in the **Flight List** box. After a flight has been
selected, all associated special events will appear in the **Special
Events** table , and all associated atypicalities will appear in the
**Analysis List\
** table. These tables are described below.

### View Special Events & Routine Events

Figure 8.85. Special Events Table (Flight Validation Window)

![](media/image83.png){width="6.845138888888889in" height="2.225in"}

The **Special Events** table (see Figure 8.85) displays event status,
event description, event level, event time in flight, flight *phase*,
and event duration for every special event associated with the flight.

To view the flight's routine events, click the **Routine Events** tab.

Figure 8.86. Routine Events Table (Flight Validation Window)

![](media/image84.png){width="6.846527777777778in"
height="2.2159722222222222in"}

The **Routine Events** table (see Figure 8.86) displays the event time
for the flight's routine events. This allows an analyst to reference
special events to the time of routine events in a flight.

### View Analysis List & Analysis Details

Figure 8.87. Analysis List Table (Flight Validation Window)

![](media/image85.png){width="6.832638888888889in"
height="2.3229166666666665in"}

The **Analysis List** tab (see Figure 8.87) displays the *global
atypicality* level, atypicality analysis status, analysis date, and
event level for every *phase atypicality* associated with the flight.

To view the details associated with an atypicality, select the
appropriate record , and then click the **Analysis Details** tab.

Figure 8.88. Analysis Details Table (Flight Validation Window)

![](media/image86.png){width="6.853472222222222in"
height="2.3020833333333335in"}

The **Analysis Details** table (see Figure 8.88) displays parameter
names and rationale descriptions for every atypicality associated with
the flight.

### Validate Selection

Figure 8.89. Flight Validation Window

![](media/image87.png){width="6.838888888888889in"
height="5.206944444444445in"}

Analysts can use the Viewer tool to perform additional research on
special events and atypicalities. To open the Viewer from the **Flight
Validation** window (see Figure 8.89), simply select a flight in the
**Flight List** box, then click **Send to** **Viewer**.

Once the analyst has sufficiently researched a flight, it's time to
assign the proper validation status to every special event and
atypicality. To do this, simply double-click the special event or
atypicality item in the appropriate table , or select the special event
or atypicality and click the corresponding **Validate Event** or
**Validate Analysis** button.

Figure 8.90. Validation Window

![](media/image88.png){width="3.2180555555555554in"
height="5.625694444444444in"}

In the **Validation** window (see Figure 8.90), select one of the
following options in the **Validation Status** box:

-   **Validation Deferred:** Record status is uncertain and will be
    revisited.

-   **Validation Pending:** Record has not been reviewed.

-   **Validated:** Record is valid with a confirmed or exempted
    disposition.

-   **Invalidated:** Record contains bad data, or the special event or
    atypicality has been badly defined.

-   **Refer For Second Opinion:** Event or analysis will be flagged so
    that it can be recalled and evaluated later by a second analyst.

In addition, analysts can select one or both of the following choices in
the **Actions** box:

-   **Maintenance:** Maintenance is needed on the aircraft associated
    with this flight.

-   **Investigation:** An investigation needs to be performed for this
    event.

To add comments to a validation record, simply enter text into the empty
field , and then click **Add New Comment**. The comment will appear in
the **Comments** box. The user name and date of entry will be added
automatically to the record.

When all the information has been entered for the validation record,
click **Save and Close** to save the validation record and exit the
**Validation** window.

Figure 8.91. Flight Validation

![](media/image89.png){width="6.838888888888889in"
height="5.206944444444445in"}

The validated record now will be updated in the **Flight Validation**
window (see Figure 8.91). Note that **Status** column in the **Analysis
List** table has been updated to "Confirmed" status, and that the
comment box also has been updated.

# Reports

## Overview

The Reports tool allows analysts to create custom graphs and statistics
tables from flight data. Users first build templates, and then create
reports based on the templates. The Reports tool actually consists of
two separate tools that use a similar design:

-   The Performance Report tool generates reports from parameter data in
    the *Full Flight Data (FFD)* or *Scrubbed Full Flight Data (SFFD)*
    file. Analysts group flights by *phase* (or segment), fleet, date,
    and airport. Graph outputs include bar charts, line charts, area
    charts, and histograms. Analysts use this tool to determine the
    overall pattern of performance for an entire group of flights.

**Note:** At this time, the Performance Report tool plots only distance
data on the x-axis. For this reason, the tool is most useful for
analyses of takeoffs and landings.

-   The Special Event Report tool generates reports from a flat file of
    *special events*, or exceedances. Analysts use this tool to evaluate
    the numbers and rates of special events and to make comparisons with
    other flights.

The Performance Report and Special Event Report tools will be described
separately, with an introductory section that describes set-up details
common to both tools.

## Set-up Details

### Log In

Figure 9.92. Reports Login Window

![](media/image90.png){width="6.840972222222222in"
height="4.815972222222222in"}

Unlike other APMS tools, the Reports tool opens with its own **Login**
window (see Figure 9.92). Simply type the appropriate information into
the **User Name** and **Password** fields, and then click **Login**.

**Note:** A user name and password will be provided by the system
administrator.

### Create User Category

Figure 9.93. Reports Home Page Window

![](media/image91.png){width="6.845138888888889in"
height="4.809027777777778in"}

Analysts must create a user category before beginning work in either the
Performance Reports tool or the Special Events report. To create a user
category, click **Manage Categories** in the **Reports Home Page**
window (see Figure 9.93).

Figure 9.94. Report Categories Window

![](media/image92.png){width="6.845138888888889in"
height="4.809027777777778in"}

In the **Report Categories** window (see Figure 9.94), type a user name
in the **Name** field and select a permissions level from the
**Permission** drop-down box. Click **Add** to create the user category.

## Performance Report Details

### Create New Template

Figure 9.95. Reports Home Page Window

![](media/image91.png){width="6.845138888888889in"
height="4.809027777777778in"}

Analysts first build templates, and then create performance reports
based on the templates. Performance report templates define the specific
flight phase (or segment) to be analyzed. They also allow the analyst to
define the type of output (such as a bar chart or histogram) for a
report. To create a template, click **Create Templates** in the
left-side menu of the **Reports Home Page** window (see Figure 9.95).

Figure 9.96. Create Performance Report Templates Window

![](media/image93.png){width="6.841666666666667in" height="5.50625in"}

In the **Create Performance Report Templates** window (see Figure 9.96),
follow these steps to create a template:

-   Type a name for the template in the **Template Name** field.

-   Select the appropriate user category in the **Template Category**
    drop-down list.

-   Select the desired flight phase (or segment) to analyze in the
    **Report Type** drop-down list.

-   Select the desired graph type in the **Graph Type** drop-down list.

-   To overwrite the default *routine event* marking the start of
    selected phase, select a new routine event in the **Starting
    Marker** drop-down list.

-   To overwrite the default routine event marking the end of selected
    phase, select a new routine event in the **Ending Marker** drop-down
    list.

-   Click **Add Segment** to add a phase to the template. The phase
    should appear in the **Report Segments** box.

-   If desired, add additional phases to the template.

-   When finished, click **Create Template**. The new template should
    appear in the template list at the bottom of the page.

**Note:** Templates can be edited for future revision.

### Create New Report

Figure 9.97. Create Performance Reports Window

![](media/image94.png){width="6.841666666666667in"
height="6.274305555555555in"}

A performance report can be built on any template that is available in
the **Create Performance Reports** window (see Figure 9.97). To create a
report, follow these steps:

-   Click **Select** for the appropriate template in the **Report
    Template** list.

-   Type a name for the report in the **Report Name** field.

-   Select the appropriate user category in the **Report Category**
    drop-down list.

-   Select arriving flights, departing flights, or all flights in the
    **Operation** drop-down list.

-   Select the appropriate fleet in the **Fleet** drop-down list.

-   Select one or more airports in the **Airports** scroll list.

-   Select the start date in the **Starting Date** calendar.

-   Select the end date in the **Ending Date** calendar.

-   When finished, click **Run Now**.

**Note:** Reports cannot be edited once they have been created.

### View Report

Figure 9.98. Performance Report Window

![](media/image95.png){width="6.841666666666667in"
height="5.489583333333333in"}

The report results will appear in the **Performance Report** window (see
Figure 9.98). Click **Add to PowerPoint** to automatically load selected
charts into a PowerPoint document. Click **Discard** to remove the
entire report from the reports archive.

To view additional report details, click **View Reports**.

Figure 9.99. View Performance Reports Window

![](media/image96.png){width="6.841666666666667in"
height="5.489583333333333in"}

The **View Performance Reports** window (see Figure 9.99) displays a
list of all saved reports. To view all details of a report, click
**Select** for the appropriate report, and then click **Report
Details**.

**Note**: To create a zipped file containing graphics, statistics, and
XML files for this report, simply click **Download**.

Figure 9.100. View Performance Report Details Window

![](media/image97.png){width="6.841666666666667in"
height="5.517361111111111in"}

The **View Performance Report Details** window (see Figure 9.100) allows
the analyst to view all details of a report. To view a graph that
combines the plots from two or more charts, click\
**Combined.** To view XML data for the report, click **XML File**. To
view a statistics table, click **Statistics**.

## Special Event Report Details

### Create New Template

Figure 9.101. Reports Home Page Window

![](media/image91.png){width="6.845138888888889in"
height="4.809027777777778in"}

Analysts first build templates, and then create special event reports
based on the templates. Special event report templates define the
specific events and phases to be analyzed. They also allow the analyst
to chart the output by event, status, airport, month, or year. To create
a template, click **Create Templates** in the left-side menu of the
**Reports Home Page** window (see Figure 9.101).

Figure 9.102. Create Special Event Report Templates Window

![](media/image98.png){width="6.845138888888889in" height="5.275in"}

In the **Create Special Event Report Templates** window (see Figure
9.102), follow these steps to create a template:

-   Type a name for the template in the **Name** field.

-   Select the appropriate user category in the **Category** drop-down
    list.

-   Select the desired measuring unit (counts or rate) for the x-axis in
    the **Measure** drop-down\
    list.

-   Select the desired chart type (line or bar) in the **Format**
    drop-down list.

-   Select the data category (event, airport, status, month, or year)
    for the y-axis in the **Charted by** drop-down list.

-   Select the desired number of items to chart for the y-axis category
    in the **Top Items** drop-down list. For example, if the data
    category in the **Charted by** list is Airport, a selection of 5 in
    the **Top Items** list will chart results for the five most active
    airports.

-   Select the data category (individual event, individual airport,
    individual status, individual month, individual year, total events,
    or total airports) in the **Separated by** drop-down\
    list. For example, select Individual Month to produce a separate
    chart for each month.

-   Select the desired event levels (all, levels 2 and 3 only, or level
    3 only) in the **Event Levels** drop-down list.

-   Select any or all events in the **Events** drop-down list.

-   Select any or all phases in the **Phases** drop-down list.

-   When finished, click **Add**. The new template should appear in the
    template list at the bottom of the page.

**Note:** Templates can be edited for future revision.

### Create New Report

Figure 9.103. Create Special Event Reports Window

![](media/image99.png){width="6.845138888888889in"
height="7.695833333333334in"}

A special event report can be built on any template that is available in
the **Create Special Event Reports** window (see Figure 9.103). To
create a report, follow these steps:

-   Click **Select** for the appropriate template in the **Report
    Templates** list.

-   Type a name for the report in the **Report Name** field.

-   Select the appropriate user category in the **Report Category**
    drop-down list.

-   Select the appropriate fleet in the **Fleet** drop-down list.

-   Select arriving flights, departing flights, or all flights in the
    **Operation** drop-down list.

-   Select one or more airports in the **Airports** scroll list.

-   Select the start date in the **Starting Date** calendar.

-   Select the end date in the **Ending Date** calendar.

-   When finished, click **Create**.

**Note:** Reports cannot be edited once they have been created.

### View Report

Figure 9.104. Special Event Report Window

![](media/image100.png){width="6.845138888888889in"
height="5.955555555555556in"}

The report results will appear in the **Special Event Report** window
(see Figure 9.104). Click **Add to PowerPoint** to automatically load
selected charts into a PowerPoint document. Click **Discard** to remove
the entire report from the reports archive.

To view additional report details, click **View Reports**.

Figure 9.105. View Special Event Reports Window

![](media/image101.png){width="6.845138888888889in"
height="5.033333333333333in"}

The **View Special Event Reports** window (see Figure 9.105) displays a
list of all saved reports. To view all details of a report, click
**Select** for the appropriate report, and then click **Report
Details**.

**Note**: To create a zipped file containing graphics, statistics, and
XML files for this report, simply click **Download**.

Figure 9.106. View Special Event Report Details Window

![](media/image102.png){width="6.848611111111111in"
height="5.483333333333333in"}

The **View Special Event Report Details** window (see Figure 9.106)
allows the analyst to view all details of a report. To view the next
graph in the series, click **Next.** To add the visible chart to a new
or existing PowerPoint document, click **Add to PowerPoint**. To view
template and report criteria, click **Show Graph Info**. To view a
statistics table, click **Statistics**. To add the entire report to a
new or existing PowerPoint document, click **Add Report to\
PowerPoint**.

# Glossary

## 

  -----------------------------------------------------------------------
  Term                  Description
  --------------------- -------------------------------------------------
  Aggregation           A group of new and existing flights (typically
                        totaling 1,000) used by the Analysis Engine to
                        produce an analysis report. Flights from the same
                        fleet (and, if applicable, from the same
                        originating or destination airport) are grouped
                        to form an aggregation. The Analysis Engine then
                        compares the flights by phase to determine the
                        most atypical flights in the aggregation.

  Analysis Engine Tool  An APMS utility that uses internal algorithms to
                        identify typical patterns and atypical flights
                        represented in bodies of digital flight data.
                        Because it operates without any prior human
                        specification of normal or operationally
                        interesting flight patterns, the Analysis Engine
                        can reveal unexpected events or trends that could
                        compromise the safety of flight operations. This
                        utility produces the analysis reports used by the
                        Morning Report tool.

  Analysis Report       A report generated either manually or
                        automatically by an APMS utility called the
                        Analysis Engine. This report identifies atypical
                        flights and atypical flight phases. It is
                        displayed by the Morning Report tool.

  APMS                  NASA's Aviation Performance Measuring System.

  Atypicality           An anomaly in the digital flight data for a
                        specific flight or phase of a flight. The Morning
                        Report tool is used to view the atypicalities
                        identified by the Analysis Engine utility.

  Cartridge             A removable disc that stores digital flight data.
                        A cartridge usually contains data from multiple
                        flights of a single aircraft. Cartridges are
                        identified by aircraft tail number and date of
                        last recorded data.

  Data Exploration Tool An APMS tool that allows analysts to conduct
                        in-depth research on a flight. It contains links
                        to other tools and utilities, including the
                        Viewer, Parameter Editor, and Loader.

  Derived Parameter     A custom parameter that is defined by the user
                        and generated within APMS. A derived parameter is
                        frequently based on a mathematical equation and
                        the values from other flight parameters. For
                        example, an aircraft's potential energy can be
                        derived at any given moment of the flight by
                        multiplying its gross weight parameter value by
                        its altitude parameter value.

  Event Charts Tool     An APMS tool that report pages containing routine
                        event charts for a selected group of flights.
                        Each event chart is associated with one parameter
                        and uses routine events to plot the parameter's
                        distributions. The charts contained in a report
                        page allow an analyst to evaluate and compare
                        parameter distributions at routine events within
                        a group of flights.

  Event Frame           A selected moment or span of time in a flight. An
                        event frame can be an APMS-defined phase (such as
                        Cruise), a user-defined time period based on
                        routine event markers (such as Taxi Out to
                        Liftoff), or a custom time period created in the
                        advanced mode of Search Pattern (such as 1500 ft
                        AFE Approach to Touchdown). The time represented
                        by an event frame can be as short as a single
                        second or as long as the entire flight.

  Exceedance            See *Special Event*.

  FFD File              Full Flight Data file. A complete set of flight
                        data for a single flight. This unfiltered file
                        contains all parameter values from takeoff to
                        touchdown. The APMS Loader utility creates a
                        separate FFD file for each flight while importing
                        raw flight data.

  Fleet Editor Utility  An APMS data importation utility. For more
                        information, see the APMS 3.0 System
                        Administrator's Guide.

  Flight Validation     An APMS tool that allows a flight analyst to view
  Tool                  all special events, routine events, and
                        atypicalities associated with a flight and to
                        affirm or invalidate the record.

  FOQA                  Flight Operational Quality Assurance team. These
                        aviation-safety analysts review data recorded
                        during flight to improve the safety of flight
                        operations, air traffic control procedures, and
                        airport and aircraft design and maintenance.

  Generic Parameter     A parameter that has been given a standardized
  Name                  name within APMS. Prior to importation to APMS,
                        digital flight data contain parameter names that
                        vary depending on the particular airline, fleet,
                        or recording device. APMS programmers assign a
                        common parameter name to each parameter to enable
                        cross-fleet analyses. Generic parameter names are
                        for internal APMS use only.

  Global Atypicality    An anomaly in the digital flight data associated
                        with a specific flight. A flight with global
                        atypicality contains one or more phases with
                        parameters that vary from those of other related
                        flights. The Analysis Engine utility identifies
                        flights with global atypicality and ranks the
                        degree of variance. A flight can have only one
                        global atypicality ranking per analysis report.
                        Analysts use the Morning Report tool to identify
                        flights with global atypicality.

  GRADE                 Graphical Airspace Design Environment. GRADE,
                        developed by ATAC Corp., is a PC-based,
                        four-dimensional computer tool for displaying,
                        analyzing, designing, and evaluating air traffic
                        operations. The Viewer and Data Exploration tools
                        contain a link to the GRADE system.

  Invalidated           An atypicality that has been rejected and flagged
  Atypicality           as invalid by a flight analyst. This designation
                        usually indicates that the atypicality resulted
                        from bad data.

  Invalidated Special   A special event that has been rejected and
  Event                 flagged as invalid by a flight analyst. This
                        designation usually indicates that the special
                        event resulted from bad data.

  Level 1 Atypicality   An atypical flight or phase with parameters that
                        vary slightly from those of other related flights
                        in an aggregation. The level is assigned by the
                        Analysis Engine utility.

  Level 2 Atypicality   An atypical flight or phase with parameters that
                        vary moderately from those of other related
                        flights in an aggregation. The level is assigned
                        by the Analysis Engine utility.

  Level 3 Atypicality   An atypical flight or phase with parameters that
                        vary greatly from those of other related flights
                        in an aggregation. The level is assigned by the
                        Analysis Engine utility.

  Level 1 Special Event A special event that presents a low risk to
                        aviation safety. The level is assigned by
                        commercial flight data processing software prior
                        to data importation by APMS.

  Level 2 Special Event A special event that presents a medium risk to
                        aviation safety. The level is assigned by
                        commercial flight data processing software prior
                        to data importation by APMS.

  Level 3 Special Event A special event that presents a high risk to
                        aviation safety. The level is assigned by
                        commercial flight data processing software prior
                        to data importation by APMS.

  Loader Utility        An APMS data importation utility that is used to
                        access the online data stores generated by
                        commercial flight data processing software. For
                        more information, see the APMS 3.0 System
                        Administrator's Guide.

  Module                A user-defined flight event composed of one or
                        more parameter conditions (such as N1_Eng_1_corr
                        ≤ 45), applied to a specific time frame (such as
                        Ten Minutes before Touchdown). One or more
                        modules define a pattern. (This term applies only
                        to the Search Pattern tool.)

  Morning Report Tool   An APMS tool that provides textual descriptions
                        and graphical representations of data imported
                        from the Analysis Engine's reports. This tool
                        allows analysts to study selected groupings of
                        flights and to investigate flight and phase
                        atypicalities.

  Parameter             A sensor-monitored flight condition, such as
                        average fuel burned per hour. Digital flight data
                        recorders are used to register and store a
                        numerical value for each parameter every second
                        or fraction of a second throughout the flight.
                        Hundreds, or even thousands, of parameters can be
                        collected for a single flight. Some parameters
                        relate to continuous data (such as altitude and
                        airspeed). Other parameters assume just two, or a
                        few, discrete values (such as the on or off
                        position of the thrust reverser).

  Parameter Cloud       In the Morning Report display, a graphical
                        representation of data from an aggregation of
                        flights. The parameter cloud depicts the range of
                        digitally recorded values for a single parameter
                        during a specific phase. This graphical
                        visualization provides a frame of reference
                        against which the parameter trace from a single
                        atypical flight can be overlaid and visually
                        assessed by human analysts.

  Parameter Condition   A user-defined equation that includes a specific
                        flight parameter, an operator, and a numeric
                        value (for example, Airspd_Computed ≥ 200). One
                        or more parameter conditions, when applied to a
                        specific event frame, define a module. (This term
                        applies only to the Search Pattern tool.)

  Parameter Display     The parameter name that appears in the APMS tools
  Name                  used by flight analysts. Unlike a generic
                        parameter name that is used only by APMS
                        programmers, a display name is usually more
                        meaningful to end-users and can be modified to
                        allow individual airlines to adopt their own
                        terminology.

  Parameter Editor      An APMS data importation utility. For more
  Utility               information, see the APMS 3.0 System
                        Administrator's Guide.

  Parameter Trace       In the Morning Report, a graphical representation
                        of data from a single flight depicting the
                        digitally recorded values for a single parameter
                        during a specific phase. The trace appears as a
                        black line.

  Pattern               A user-defined data map that is used to locate
                        flights that share specific characteristics. Each
                        pattern consists of one or more modules, or
                        user-defined flight events. (This term applies
                        only to the Search Pattern tool.)

  Performance Report    One of two Reports tools. The Performance Report
                        tool generates reports from parameter data in the
                        Full Flight Data (FFD) or Scrubbed Full Flight
                        Data (SFFD) file. Graph outputs include bar
                        charts, line charts, area charts, and histograms.
                        Analysts use this tool to determine the overall
                        pattern of performance for an entire group of
                        flights. See *Reports Tool*.

  Phase                 A distinct segment of a flight (such as Begin
                        Cruise or Final Approach) that is defined by the
                        routine event markers that precede and follow it.

  Phase Atypicality     An anomaly in the digital flight data associated
                        with a specific phase of a flight. A flight with
                        phase atypicality contains parameters that vary
                        to a significant degree from those of other
                        related flights. The Analysis Engine utility
                        identifies flights with phase atypicality and
                        ranks the degree of variance. A single flight can
                        have a different phase atypicality ranking for
                        each atypical phase. Analysts use the Morning
                        Report tool to display flights with phase
                        atypicality. Analysts use the Flight Validation
                        tool to confirm or reject the anomaly.

  Phase Editor Utility  An APMS data importation utility. For more
                        information, see the APMS 3.0 System
                        Administrator's Guide.

  Reports Tools         A pair of APMS tools that allow analysts to
                        create custom graphs and statistics tables from
                        flight data. The Reports tools consist of the
                        Performance Report tool and the Special Event
                        Report tool. The Performance Tool generates
                        reports from parameter data in the Full Flight
                        Data (FFD) or Scrubbed Full Flight Data (SFFD)
                        file. The Special Event Report tool generates
                        reports from a flat file of special events, or
                        undesirable flight occurrences. See *Performance
                        Report Tool* and *Special Event Report Tool*.

  RIN                   An APMS-computed number that is displayed for
                        every flight that matches a pattern. The RIN is
                        the sum of the module risk indices that occurred
                        during a flight. The larger the RIN, the greater
                        the risk. The RIN allows analysts to locate the
                        most critical flights that appear in search
                        pattern results. (This term applies only to the
                        Search Pattern tool.)

  Risk Index            An analyst-assigned risk level for each module in
                        a pattern. This numerical value allows analysts
                        to weight the relative degree of risk from the
                        combined parameter conditions included in the
                        module. The larger the number, the greater the
                        risk. The risk index is used to compute the RIN
                        for every flight that matches a pattern.
                        Currently, there is no default risk index value
                        range in APMS.

  Routine Event         A regular flight occurrence (such as Liftoff)
                        that can be identified by its unique data
                        signature. A routine event occurs when an
                        individual flight parameter (such as air speed,
                        pitch angle, or average fuel burned per hour) or
                        combinations of individual flight parameters
                        reach a predetermined value or range of values.
                        The APMS Loader utility uses pattern search
                        definitions to find and mark routine events in
                        the FFD file while importing raw flight data.

  Search Pattern Tool   An APMS tool that is used to search FFD or SFFD
                        files for patterns in flight data. The Search
                        Pattern tool allows a flight analyst to define
                        flight patterns and use them to query matching
                        flights in the APMS database.

  SFFD                  Scrubbed Full Flight Data file. An SFFD is a
                        filtered version of the original FFD file.

  Special Event         A predefined and undesirable flight occurrence
                        (such as Low Power on Approach) that results from
                        operational anomalies. A special event, also
                        known as an exceedance, occurs when an individual
                        flight parameter (such as air speed, pitch angle,
                        or average fuel burned per hour) or combination
                        of parameters exceeds a predetermined,
                        fleet-specific value or range of values.
                        Commercial flight data processing software is
                        used to identify and record special events prior
                        to data importation by APMS.

  Special Event Report  One of two Reports tools. The Special Event
                        Report tool generates reports from a flat file of
                        special events, or undesirable flight
                        occurrences. Analysts use this tool to evaluate
                        the numbers and rates of special events and to
                        make comparisons with other flights. See *Reports
                        Tool*.

  Validated Atypicality A phase atypicality that has been confirmed and
                        flagged as valid by a flight analyst. This
                        designation usually indicates that the
                        atypicality is legitimate and did not result from
                        bad data.

  Validated Special     A special event that has been confirmed and
  Event                 flagged as valid by a flight analyst. This
                        designation usually indicates that the special
                        event is legitimate and did not result from bad
                        data.
  -----------------------------------------------------------------------