1. Lessons learned from pilot involvement in ASAS experiments Rob Ruigrok & Hans Huisman ASAS Thematic Network Workshop 3 “ASAS - Making it happen”, Toulouse

2. 2 Contents ASAS experiments Pilot involvement ASAS applications tested Data gathered Example: Responsibility Lessons learned Finally … Demonstration

3. 3 ASAS Experiments MFF ASAS Self-Separation –MAS-FFAS transitions FL280 FL290 MAS FFAS

4. 4 ASAS Experiments MFF ASAS Spacing –En-route & descent

5. 5 ASAS Experiments MA-AFAS ASAS Spacing –R/T versus CPDLC –Automatic versus Manual speed control –Using Interactive Navigation Display with advanced Cursor Control Device. –Using time-based sequencing & merging

6. 6 Pilot involvement About 25 different pilots in 3 ASAS experiments (8 MFF Self-Sep, 8 MFF Spacing, 20 MA-AFAS). Current on “glass cockpit” aircraft (757-200, MD-11, 737-300/400/700/800/900 and 747-400). Average experience around 6000 hours, minimum 700 hours, maximum 16500 hours The results of these experiments cover their “average” opinion.

7. 7 ASAS applications tested ASAS Spacing –Follow (distance & time) –Merge Behind –Continue/Resume –Pass Above, Below, Pass Behind, Abeam ASAS Self-separation –climb, en-route, descent –including transitions

8. 8 During & post run questionnaires –Workload, Acceptability, Events Debriefing questionnaires –ASAS system (CDTI, CD&R, Tools), Procedures, Responsibility Instantaneous Self-Assessment (ISA) –Workload, Workload peaks Data gathered

9. 9 Example: Responsibility MFF Self-Separation:

10. 10 Lessons learned Responsibility for separation assurance needs to be clear. –If responsibility is unclear, the procedures need to be redesigned. –Example: Transition layer between MAS and FFAS removed. ASAS applications need to be unambiguous. –ASAS applications often tested separately. In real-life, an ASAS avionics suite involving all applications will find its way into the cockpit. –Example: currently “Remain Behind” in ASAS Spacing and ASAS Separation.

11. 11 Lessons learned ASAS needs to be simple. –Pilots comment that they have to be able to operate it during a 9 hour flight, through time- zones, while fighting sleep. –Example: Reduction of ASAS instruction set (37=>14) and simplified phraseology proposed. Test bad-case and worst-case scenarios. –Example: Pilots question “What happens with significant weather ?”, “What happens with failures ?”, “What happens with military operations ?”, etc.

12. 12 Lessons learned Pilot input required from very start. –Pilots sometime have no problem with foreseen issues by the ASAS procedure designers, and vice versa. –Example: use of callsign for target selection. Pilots appear very (fuel)efficiency-minded. –ASAS procedure should be designed with this in mind to increase acceptability & benefits. –Example: pilots reduced speed in heading-then-follow manoeuvre.

13. 13 Lessons learned Do not rely on opinion of one pilot. –Pilots of the same crew sometimes completely disagreed on ASAS. –Example: use of priority rules in Self-Separation. Design for all pilots. –A senior captain with 16000 hours needs to be able to operate it, as well as a flying school graduate with 200 hours. –Example: some youngsters are FMS wizzards.

14. 14 Finally... A selection of the (many) positive remarks on ASAS, recorded during the experiments: –“A great system on its way to perfection.” –“Looks like this is going to be reality.” –“You get something to do as pilot.” –“When using this system for a few days, it feels like you are using it for years.” –“It is an ergonomic strong design.” –“Workload was very low, almost boring.” –“Almost no difference between flying in MAS or FFAS, except for communication with ATC.” ASAS - Making it happen !

15. 15 Demonstration When: this evening, from 17:30. Where: see program. What: –ASAS avionics suite ASAS Awareness ASAS Spacing ASAS Separation ASAS Self-Separation Including pre-liminary ASAS/ACAS integration (note: exact copy of NLR full-flight simulator software on laptop) Come and fly yourself all elements of ASAS in realistic scenarios

16. 16