1

Human Factors Engineering (HFE

Gulfstream Flight Deck Developm

and Certification

Susan Taylor

September 17, 2014
2

Gulfstream Current Product Line
3

Gulfstream - The Need for Speed

QSJ G550 Mmo 0.885 G650 Mmo 0.925

QSJ M

Increasing Speeds for Increased Productivity

G200 LRC 0.75M G280 LRC 0.80M

Customers:

“It Saves Time – The Most Valuable Reso
4

Technology Driven by Safety, Custo

• Accident / incident data is continuously review

assess new flight deck designs

– Pilot input solicited at each stage of design

• Performance changes affect flight deck techno

– Example: supersonic nose and fuselage size

• Ongoing investment in Flight Deck technology

– Ability to go anywhere, anytime– More displays, simplification where needed– Synthetic Vision, Enhanced Vision, External Vis
5

HFE Integral Part of Flight Dec

Design Process at Gulfstream
6

HFE Resides in Systems Engineerin
7

HFE Role in Gulfstream Engineering

ME(d

Electrical

Engineering

(avionics displays, crew 

alerting)

Flight Operations(crew procedures, pilot workload)

Flight Test

(human factors specific test plans 

and reports)

Human Factors

Engineering

• Generate Data 

Driven Requirements

• Develop and Apply 

Structured Test Methods
8

Where Does HFE Get Applied?

Flight Deck

Equipment

Cabin

Systems

Mainten

Accessi

M

A

Emergency

Egress

Doors
9

HFE Process Applied to All New Prog

Program Milestones HFE Process HFE De

Program 

Objectives

Mission

RequirementDefinition

Crew Workload and Human 

Factors Simulator and Flight Test

FinalRequirementVerification

HFE Regul

Flight T

Prototyping

HFE Analysis

RequirementDefinition

HFE Certif

Function Allocat

Requirements M

FH

Human E

PDR

Engineering 

Development Unit Test

Detailed

DesignDefinition

In

(HFE sce

CDR

Flight Deck Design 

Guidelines

Operational

RequirementDefinition

Colo

Flight Deck 
10

Flight Deck Philosophy 

• Referenced from top leve

requirements, ARP4754 

• Philosophy Elements

– Pilot Characteristics / CRM – Certification Requirements– Alerting Guidelines– Control Interface Guideline– Crew Error Mitigation– New and Novel Criteria– Automation Guidelines

• Created in DOORS to As

Top Level HFE RequiremTraceability
New and Novel Classification Criteria

• New and Novel Defined as Not Previously Certifi

Implementation 

• All New and Novel Identified in HFE Certification • Classifications per AC/AMC 25.1302 plus the fol

– Complexity

• Number of information elements used by the crew, 

control

– Integration

• Interactions or dependencies among systems (<2=

4=moderate, >4=high)

• New and Novel Intended Functions Clearly Desc

Specifically Tested

11
New and Novel Development Testing

• New and Novel Continuously Scrutinized Throug

Process

– New and Novel Items Area of Focus for Human Error A

• Crew Error Emphasis in Developmental Testing (

Simulator Test if required)

• Test Points Specifically Developed to Target Inte

Function

– Addressed in early scenario-based testing as part of ITP

failure cases

– Tested during Crew Workload and Human Factors Cert

Simulator and Flight Test

12
Analysis / Prototyping

13

• Simulation Models Used 

HFE Requirements

– CATIA V5 Human Builder– 3DSSPP Strength Model– OPTIS SPEOS– Lumicam– Process Simulation– Display Animation (iDATA 

• Physical Prototypes Use

Validate Early HFE Req

– Operational Prototyping a

Evaluation Lab (OPEL)

• System SRDs in DOOR
Engineering Development Unit Test

• Two Types of HFE Testin

Performed During this St

– System-Specific

• Flight Controls Aspects 

Shaker Evaluation)

• Displays (e.g, Standby 

3D AMM, etc.)

– Integrated Test Procedure

• Scenario-Based• Phase of Flight Specifi• Requirements Based

• Problem Reports (PRs) G

from Both Types of Testi

14
Certification Simulator Test

15

• Simulator Test

– Flight profiles (Day VMC, Ni

Day IMC, Night IMC)

– Multiple crews

• 5’2” to 6’3” pilot stature• Low time pilot, demo (lin

included

• FAA/EASA test pilot part

– Failures assessed– New and novel intended fun

points included

– Real ATC simulated– FSI familiarization training w– Simulator test familiarization 
Certification Flight Test

16

• Flight Test

– Minimum four FAA/EASA 

GAC safety pilot

– Left/right seat combination– Multiple approach types– Lighting Characteristics– Vibration effects– Validates simulator test re– Verifies any items that cou

tested during simulator tes

– Addresses PRs identified 

simulator test

– Includes high density airpo
Certification 

• All Deliverables per HFE 

Certification Plan submitt

– Analyses– Test Plans and Reports– Supporting Analyses (e.g., 

Out, High/Low Temp AnalyEmergency Egress, etc.)

• Summary Compliance Re

Completed

• All PRs Disposed Of (e.g

revisions, future software etc.)

17
Implementing An HFE Function 

Engineering

18
19

Benefits of Standardizing HFE Meth• Well Accepted Good Engineering Design Practic

Address HFE As Early As Possible 

• HFE Documentation Provides Rationale for Des

Decisions (Natural Fit for ARP4754 Process)

• Early Simulation Modeling to Generate Requirem

Reduces Problems with Physical Prototypes

• Multidiscipline Design Team Sensitizes Other 

Engineering Disciplines to HFE, Usability

• HFE Contributes Structured Approach to Interfa

Design vs. Ad Hoc or “Shoot From the Hip” Des

– Considers full range of pilot sizes, types, experien
20

Challenges of Standardizing HFE in 

1. Industry Acceptance of HFE Role as Integral to 

Development– Clearly Defined HFE Role in Certification Helps R

Confusion (e.g., AR role)

• Ambiguity Between Groups (e.g., Flight Test; STC v

vs. TC – how much HFE support is required?)

– Documented Methods Standardize Role

Recommendation: Establish HF AR in 

Test; Support HFE Methods Standardiza
21

Challenges of Standardizing HFE in 2. 25.1302 Compliance, Human Error Analysis Dif

Standardize

– Ambiguous language (HFE-ese)

• Differences between authorities on how to operat

of authority involvement required

• Gulfstream uses combination of analysis, simulato

test; typically situation-specific

– Human Error Analysis complements safety analy

safety looks for quantitative approach

• HFE research data needed to provide hard numb

justify cost for OEM

Recommendation: Provide Specific Meth

25.1302, Including Human Error Analysis M
22

3. Simulation Methods Reduce Prototyping and F

Time

– Human Modeling Easy Benefit Because of Indus

Transition to Electronic Design Tools

– Strength Modeling Easy Benefit Because Quant

Output

– Interface Prototyping Tools Typically Require De

Experts (and More Resources)

– More simulation tools (lighting simulation, proces

needed

Challenges of Standardizing HFE in 

Recommendation: Provide List of Appr

Simulation Methods To Use for Certifica
23

Challenges of Standardizing HFE in 4. Crew workload testing

– Situation-specific (e.g., display symbology vs. glo– Subjective instruments still best method for certif

• Easy to administer in flight; easy for pilots to unde• Video recording supports pilot ratings / comments• Flight Technical Error, if applicable

– Quantitative Methods very useful, situation speci

• Airspeed, ATC communication lapses, etc.

Recommendation: Support Research 

Secondary Task Measures for Crew Work

Validate Subjective Data
24

Challenges of Standardizing HFE in 

5. Staffing Qualified HFEs

– Hard to Fill Positions; Gulfstream Engineering Has 

HFE as a Critical Need 

• Skill set unique combination of engineering/sci

psychology: OJT required and breadth of systeknowledge creates steep, and lengthy learning 

• BCPE attempted to standardize, but probably n

revision in light of recent FAA changes

– 25.1302– More emphasis on HFE, HF AR qualificatio

Recommendation: Partner with Univers

Develop Curricula that Ensures Qualified H

Factors Engineers 
25

Future Directions• Gulfstream continues research and evaluation o

potential solutions or new technologies that:

– Directly enhance operator safety and performanc– Sustain (and improve) a very high dispatch reliab– Provide efficiencies to meet future performance 

requirements

– Target flight deck solutions that support superson