1. Capabilities of TIS-B for Supporting ASAS
Dr. Andrew Zeitlin
19-21 April 2004
ASAS-TN 3rdWorkshop

2. Status of TIS-B Defined in RTCA MASPS (DO-286, April 2003)
Work underway on DO-286A, expected approval October 2004
Several implementations of TIS-B sites
Will increase to 40 stations on U.S. East Coast
Will increase to 62 radars’ coverage
Implementing at 2 ERAU locations
Implementing at 1 Alaska location

3. Purpose of TIS-B
ADS-B
ADS-B
RADAR

4. TIS-B Concept
Broadcast ground surveillance data to display non-ADS-B targets onboard ADS-B aircraft (“gap-filler”)
ADS-B Rebroadcast across different links (“Multilink Gateway”)
Optional roles, may be defined in future editions:
Full traffic picture broadcast
ADS-B equipped targets to improve their surveillance quality for use in demanding applications
Validation of aircraft ADS-B broadcasts by comparison to ground surveillance data

5. Principles of TIS-B
RTCA DO-286 defines TIS-B to be complementary to, and compatible with, ADS-B surveillance data
Uses Same Data Links
Similar messages
Surveillance quality measures
Flexible in supporting current and future surveillance architectures
Initially defined for Visual Acquisition of Traffic applications (airborne and on airport surface)
Provisions to support more demanding applications if surveillance requirements can be met

6. TIS-B Functions Rebroadcast Path Ground Surveillance Processing
Input from Sensor(s)
Rebroadcast Path
Extract Target Reports & Provide to ASAS Processing
Ground Surveillance Processing
Create & Maintain Tracks
Assess Track Quality
Airborne Link-Specific Processing
Filter & Distribute Target Reports to Broadcast System
Distribution
Broadcast Messages
Ground Link-Specific Processing
Format Messages
Manage Data Link

7. Rebroadcast Service
Link A
Link B
No ADS-B
Radar

8. Some TIS-B Topics of Interest
Service Volume
where users receive a defined service
Traffic Information Volume
where the traffic picture comes from
can be same or different from Service Volume
Surveillance Quality Parameters
Track Accuracy (NAC)
Track Integrity (NIC, SIL)
Track Quality Level (TQL – denoting continuity, latency, etc.)
Stand-alone and Network Architectures
Both are supported