Boeing and Airborne Surveillance Boeing and Airborne Surveillance

Boeing and Airborne Surveillance

Boeing and Airborne Surveillance Some good news…………. and some other news. 2

ADS-B-OUT • Boeing has included Mode S-based ADS-B transmission capabilities in its wiring and hardware updates for Elementary and Enhanced Surveillance • Retrofit service bulletins available • DO-260 A ADS-B MOPS upgrades will follow when available in vendor implementations 3

ADS-B/CDTI • No firm plans for ADS-B-IN and CDTI • First hurdle will be the business case • Not wholly dependent, but likely to be tied to ARINC 768 Integrated Surveillance System hardware availability. 4

The Business Case – What is Needed? • Operators are the building blocks of the manufacturer’s business case • So we see the relationship between operational benefits and costs of function provision through a filter • The operator’s business case remains shaky at best, even in profitable times • Non-traditional approaches need to be worked • Assure rapid, efficient implementation 5

Reduce the Risks • Understand the effects of the “filter” • Research • • Understand the benefits Understand the costs Understand the relevance in the future ATM system Understand liability – legal and financial • • Manufacturer and operator The product has to be right – Not just avionics – procedures, ground services, etc. too 6

Reduce the Risks • Understand certification criteria • • Establish airplane certification criteria Establish ground system certification criteria • Understand the effects of fleet mix • New build and retrofit solutions • Understand the human element • Acceptance – what will it take? 7

Ensure Global Interoperability • At a variety of levels • Political/Strategic • Operational • Functional • System 8

Ensure Global Interoperability • Political/Strategic • Rules of the air • ICAO standards • Mandates • Safety case • Similar procedures in similar airspace 9

Ensure Global Interoperability • Operational • Harmonization of procedure development – Involve regulators and service providers • Definition of minimum requirements – The lowest common denominator • Consistency in data output – Stable standards • Consistent range of applications – Service provider capabilities 10

Ensure Global Interoperability • Functional • Common frequencies – Mode S…. but then what? • Common protocols and data – Standards • Common algorithms – Predictable responses 11

Ensure Global Interoperability • System • Consistent performance – Early definition of requirements • Pilot interface requirements – Reduce variability from crew performance • Controller requirements – Conformance monitoring etc. 12

Conclusions • Business case is an imperative • Still some work to do on standards 13