20,741
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Implementing VNAV support in FlightGear (view source)
Revision as of 17:53, 2 December 2013
, 2 December 2013no edit summary
Flyingsolo (talk | contribs) |
mNo edit summary |
||
| Line 4: | Line 4: | ||
{{#ev:youtube|h4AUfkEcwIg}} | {{#ev:youtube|h4AUfkEcwIg}} | ||
--> | --> | ||
== VNAV == | |||
The Vertical Navigation (VNAV) function of the Flight Management System (FMS) serves as an intelligent agent during all flight phases by automatically selecting appropriate targets (e.g. altitude, speed, and vertical speed) and pitch/thrust control modes to satisfy the objectives of each leg of the flightplan. | |||
The VNAV function provides three automated features: | |||
* VNAV automatically selects altitude targets and speed targets according to pilot MCP entries and the altitude and speed constraints in the FMS flightplan. | |||
* VNAV automatically selects pitch and thrust control modes to fly to the targets. For example during descent, VNAV chooses between a FLCH descent, a vertical | |||
speed (fixed rate-of descent), and an FMS path descent. In the case where VNAV selects vertical speed control mode, VNAV also selects the vertical speed target. | |||
* for the descent and approach, VNAV automatically provides an optimum path that is used as the reference for all automated altitude/speed target and control mode | |||
selections. | |||
In a study of the software of contemporary VNAV functions, Sherry & Polson (1999), found that the typical VNAV function automatically chooses the active altitude target from a possible list of sixteen, and chooses the active speed target from a possible list of twenty-six. | |||
{{Appendix|all| | |||
* {{cite web |url=http://human-factors.arc.nasa.gov/publications/20051025130903_VNAVCogEngJournal1TM.pdf |title=Why VNAV in Descent is Difficult to Use }} | |||
}} | |||
== Problem == | == Problem == | ||