Contents:
Example for Dynamically Populating Flight Plan
Information Elements
Focus shifts among the components and categories of the Flight Object
over the lifecycle of a flight, as illustrated by this example showing
how the information elements are populated with flight plan information.
Note that the information does not move so much as propagate,
because each component is capturing different elements of the flight information.
For more detail on events that affect information elements in a component,
click on that component's name in the diagram.
For more information on current flight plan processing: Understanding
Role of Flight Data Processing Across NAS Operational Domains,
Elvan McMillen, 24 August 1999, The MITRE Corporation, McLean, VA.
- Available as a slideshow
to view animated walk-through
- Available as a briefing
![[pdf]](/images/pdf.gif)
with notes to read description
In the current flight plan processing, it is not clear whether the flight's
clearance is considered current when the flight plan is activated (as
shown above) or when the predeparture clearance is given to the pilot
(see associated issue).
See more detail on the availability time frame needed by the capabilities
accessing flight information:
See more detail on the availability time frame for information elements:
Top of Page
Representations of Future Flight Path
Similar information elements can differ in content in different components
(see associated issue). An example of this
is seen here for the predicted flight path:
- as represented in the Host (under
Flight As Cleared:Current)
- as represented in URET and other
automation capabilities (under Flight As Cleared: Planned or Projected)
See also the associated issues on trajectory
components and the common representation
of trajectories.
Top of Page
Definitions
- FL
- Flight Level
- LOA
- Letter of Agreement
- URET
- User Request Evaluation Tool
Top of Page
Site Links
Go to Introduction:
Go to View by Capability
Go to View by Aspect |
