Documents / Report

Defense Intelligence Reference Document Cockpits In The Era Of Breakthrough Flight

Defense Intelligence Agency · 57 pages · text from the file's own layer

This Defense Intelligence Reference Document from the Defense Intelligence Agency, dated 1 November 2010, is one of a series of advanced technology reports produced in FY 2009 under the Advanced Aerospace Weapon System Applications (AAWSA) Program. It proposes a provisional cockpit design for craft driven by speculative breakthrough propulsion, such as control of gravity and inertia and faster-than-light travel. It draws mainly on the book Frontiers of Propulsion Science and on human-machine interface research.

  • p. 18 …For more complex missions, additional crew will be required, and thus additional displays and controls specific…
  • p. 19 …If these distances are determined to be excessive, then automated flight controls are mandatory. Another aspect…
  • p. 31 …operations to maintain fluency between pilot and mission control communications. - Include buffers in checklists to provide…
UNCLASSIFIED/ ,'F811. 8Fflli1Ale lal!i! 8111elf
• Limit the number of alarms.
• Display alarms in a dedicated, predictable location.
• Link alarms to a pictorial representation of the system to help recognize root causes,
causal relations, and where to focus corrective action.
• Provide a means to acknowledge the attention-getting aspect of the alarm without
turning off its alert status indication.
• In the case of multiple triggered alarms, the system's most prominent display
should be the highest hierarchical alarm, the highest causal alarm, or the location
on which to focus corrective action.
• Link the alarm clearly to the control response options.
Checklists
Checklists are a standard and useful tool in the operation of vehicle systems. They can
be displayed on adaptive displays where the list corresponds to the vehicle's current
status (e.g., preflight readiness or postflight checks). Recommended features of a
checklist should include the following: 41
• Display the desired and current value with each checklist item.
• Require that buttons/switches have to be touched to acknowledge that each item
has been checked off. This helps avoid skipping items and helps the user keep a
sense of involvement in the process.
• Include a completion call at the end of the checklist.
• For long lists, subdivide using the following guides:
26
- List critical items first.
- Use geographical (i.e., physical location) flow or pictorial flow to help users
retain relation between the model of the system and the procedures being
performed in the checklist.
- Use parallel tasks between the onboard operation and the ground operations
to maintain fluency between pilot and mission control communications.
- Include buffers in checklists to provide recovery time for anomalies. Decouple
tasks if possible so that the failure to meet a given checklist item does not
leave a parallel item in an open state.
- Standardize checklists within the system (assuming nested, hierarchical, or
multiple checklists) to minimize the mental burden necessary to extract
information when going from one format to another.
UNCLASSIFIED//Flilll. lilFFUilil:le lal!i! a,11e¥

Not linked to a story yet.

About this file

Report, from the dia collection. The PDF is mirrored here; the original link is above. 57 pages are in the text index: search them above, or from the library's search.