1 / 51

Bird Strike Mitigation for Aviation

Bird Strike Mitigation for Aviation. Christopher Drummond Graduate Studies, School of EECS Chris Bartone, Ph.D., P.E. Professor, School of EECS bartone@ohio.edu, 740-591-1660 (m) Ohio University Russ College of Engineering and Technology School of EECS FAA Joint University Program

gadd
Download Presentation

Bird Strike Mitigation for Aviation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bird Strike Mitigation for Aviation Christopher Drummond Graduate Studies, School of EECS Chris Bartone, Ph.D., P.E. Professor, School of EECS bartone@ohio.edu, 740-591-1660 (m) Ohio University Russ College of Engineering and Technology School of EECS FAA Joint University Program August 1-2, 2016 Ohio University, Athens, OH

  2. Acknowledgment • This work is sponsored by the FAA, Airport Technology R&D Branch (ANG-E26), Airport Safety R&D Section (ANG-E261) Ryan King.

  3. Outline • Background • Bird Strikes in Aviation • Previous FAA efforts • Ohio University Research Items • Overall Approach • Universal Access Transceiver (UAT) Data Link • TIS-B/FIS-B Considerations for UAT • Focus on TIS-B messages • FIS-B messages will be explored in the future • TIS-B Target Report Formatting/Distribution • Applicability of Target Report • Future Plans

  4. Background: Bird Strikes in Aviation • Occur when a bird collides with an aircraft; usually cause little damage, but can be devastating (ex. American Airlines Flight 1549 Hudson River incident). • Roughly 10,000 strikes are reported annually; estimates suggest that as few as half of total strikes are reported. • Less than 8% of strikes occur above 3,000 feet and 61% occur at less than 100 feet (according to FAA Wildlife Hazard Management Manual). • FAA estimates $400 million in damages annually are attributed to bird strikes in the United States alone, and over $1.2 billion in damages occur annually worldwide. Ref: http://www.faa.gov/airports/airport_safety/wildlife/media/wildlife-strike-report-1990-2013-usda-faa.pdf

  5. Ohio University Research Plans: Overview • Goal: Reduce bird strikes for aviation • Utilize ground-based radar detection via avian radar systems and Information/signal transmission to ATC tower and aircrafts in/around airport • Implement specialized avian ground-based radar on the airport property • Produce target detections and performance parameters • Target categorize and validation with avian processor • Create target reports suitable for transmission in NAS • Transmit Interface to NAS via aviation data links • Aircraft: ADS-B equipped and non-ADS-B equipped via UAT and 1090ES

  6. Ohio University Research Plans: Overview Avian Surveillance System GPS Airport Database 1090ES & UAT ADS-B IN Avian Radar System Target Categorization and Validation Format Avian Target Reports Radio Transmit Target Detections & Performance parameters TIS-B FIS-B

  7. Related RTCA Documents for Avian Messages • DO-242A Minimum Aviation System Performance Standards for Automatic Dependent Surveillance Broadcast (ADS-B) • DO-338 Minimum Aviation System Performance Standards (MASPS) for ADS-B Traffic Surveillance Systems and Applications (ATSSA) • DO-318 Safety, Performance and Interoperability Requirements Document for Enhanced Air Traffic Services in Radar-Controlled Areas Using ADS-B Surveillance (ADS-B-RAD) • DO-348 Safety, Performance and Interoperability Requirements Document for Traffic Situation Awareness with Alerts (TSAA) • DO-319 Safety, Performance and Interoperability Requirements Document for Enhanced Traffic Situational Awareness During Flight Operations (ATSA-AIRB) • DO-286B Minimum Aviation System Performance Standards (MASPS) for Traffic Information Service - Broadcast (TIS-B) • DO-260B with Corrigendum 1 - Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance - Broadcast (ADS-B) and Traffic Information Services - Broadcast (TIS-B) • DO-282B with Corrigendum 1, Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance – Broadcast • DO-267A Minimum Aviation System Performance Standards (MASPS) for Flight Information System - Broadcast (FIS-B) • DO-358 Minimum Operational Performance Standards for Flight Information System – Broadcast (FIS-B) with Universal Access Transceiver (UAT) Ref: RTCA, Inc., www.rtca.org

  8. Avian Radar Info Received • Information on the SRC, BSTAR Avian Surveillance and Warning System, Accipiter Avian Radars, and DeTect, Merlin, Avian Radar Systems: 1. Performance Specifications that, for example, include minimum radar cross section, range, number of targets supported, target update rates, azimuth, and elevation resolutions/performance, range performance, etc. 2. Interface Control Documents (ICDs) that, for example, discuss output target detections/reports on data busses (data format and content, message structures, etc.), bus hardware and software communication protocols, etc. 3. Test reports on any performance and test assessments of the avian radar systems. 4. Any design documents such as Final Design Reviews, delivery documentation, etc for the avian radar systems. • A non-disclosure agreement has been executed between Ohio University and SRC regarding proprietary data. • Received Interface Control Document (ICD) for the Asterix Interface on the BSTAR Version 1.14, 10 February, 2016 (Export Controlled Data)

  9. TIS-B or FIS-B Avian Messages • Typical TIS-B: • Broadcast data collected from avian ground-based radar • Broadcast to participating users for cockpit display of traffic information • Messages can be sent via UAT or 1090ES • Typical FIS-B: • Broadcast data collected from external sensors • Weather text, weather graphics, • NOTAMS (notice to airmen) • ATIS (Automatic Terminal Information Service) • Periodic broadcast requirements • Transmitted on UAT only • Plan to explore both, but for now, we will focus on the TIS-B structure and will explore FIS-B over the next quarter Ref: DO-242A Minimum Aviation System Performance Standards for Automatic Dependent Surveillance Broadcast (ADS-B), pg 124/475.

  10. UAT Avian Message Development • Plan UAT Avian message development first (before 1090ES TIS-B) • TIS-B Avian Messages, • FIS-B Avian Messages • Both of these TIS-B and FIS-B messages are planned to be transmitted by the stand-alone Avian Radar System (as a ground based surveillance subsystem)

  11. TIS-B Service • Provides ADS-B active users with: • Low-latency stream of position reports of non-ADS-B users. • TIS-B Client: receive avian report (i.e., aircraft or ATC tower) • TIS-B Target: avian target • TIS-B messages can contain higher-priority (i.e., time-sensitive/real-time, etc) traffic information (more so than FIS-B service) Ref: DO-338 Minimum Aviation System Performance Standards (MASPS) for ADS-B Traffic Surveillance Systems and Applications (ATSSA), pdf, pg 80/294.

  12. Ohio University Research Plans: Overview Avian Surveillance System GPS Airport Database 1090ES & UAT ADS-B IN Avian Radar System Target Categorization and Validation Format Avian Target Reports Radio Transmit Target Detections & Performance parameters TIS-B FIS-B

  13. TIS-B Avian Functional Block Diagram Airport GIS Data Base Flight Data Info Processing Avian Radar System • ADS-B in GPS Location • Create and Maintain Tracks • Assess Track Quality • Generate TIS-B Track Reports Ground Surveillance Processing TIS-B Track Reports TIS-B Target Reports • TIS-B Target Report Filtering • Target Report Distribution • Distribute Service Status Distribution • UAT • 1090 ES • Extrapolate Target Position • Assemble TIS-B Message • Transmit TIS-B Message Ground-Link-Specific Processing, Formatting, And Physical Layer Ref: RTCA, DO286B Minimum Aviation System Performance Standards (MASPS) for TIS-B, Table 3.3, pg. 5

  14. TIS-B Track Report Definition(data required to make a TIS-B message) Ref: RTCA, DO286B Minimum Aviation System Performance Standards (MASPS) for TIS-B, Table 3.3, pg. 30.

  15. Universal Access Transceiver (UAT) • Frequency: 978 MHz • Vertical Polarization • Designed to be a multi-purpose data link for surveillance related applications • Nominal channeling signal rate: ~1Mbps • Can support: • Automatic Dependence Surveillance-Broadcast (ADS-B), • Flight Information Service-Broadcast (FIS-B), • Traffic Information Service-Broadcast (TIS-B), • Potentially other applications • “Uplink” from ground contains: • 176ms of 1000 ms UAT Frame=1 UTC second • Weather, flight information , advisories, etc. • “Downlink” from Aircraft: • 800ms of 1000 ms UAT Frame=1 UTC second • ADS-B information • “TIS-B information is preferably transmitted by the ground-based broadcast facility in the ADS-B Segment of the UAT frame”; Ref: RTCA MOPS, UAT DO-282B, pp. 38/704. Ref: RTCA, MOPS for UAT ADS-B, DO-282B, SC-186, Dec. 13, 2011

  16. UAT Transmission Frame (per second) • Ground Segment transmission consists of 32 ground broadcast slots @ 5.5 ms in length, each containing 432 bytes of data • Avian Radar message would occupy one of these broadcast slots each for TIS-B and FIS-B message support • FIS-B data transmitted in this Ground Segment (in dedicated time slot) • ADS-B Segment 145 messages @ 5.5 ms in length (e.g., xtm by aircraft) • TIS-B data transmitted in this ADS-B Segment (Random Access) • Avian radar systems must be able to track 1000 targets and update no less than every 5 seconds • Message capacity vs target reports rates under further assessment. Ref: RTCA D0-282B with Corrigendum 1 page 36

  17. Ground and ADS-B Uplink Frames Synchronization: 111010101100110111011010010011100010 ADS-B Message Frame Synchronization: 000101010011001000100101101100011101 Ground Uplink Message Frame Ref: RTCA D0-282B with Corrigendum 1 pp 24-25

  18. Ground Uplink Payload • First 8 bytes comprise UAT-specific header • Remaining 424 bytes are application-specific data (which we are free to define) Ref: RTCA D0-282B with Corrigendum 1 page 26

  19. Ground Uplink Payload (App Data) The frame on the left breaks down the payload into the UAT-specific header and information frames. Ref: RTCA D0-282B with Corrigendum 1 page 27

  20. Ground Uplink Payload Frame Type • Frame type encoded above for each I-frame • Message type we send over ground uplink will be determined by this • May implement “future use” sequence coding to signify avian messages (e.g., 0010) Ref: RTCA D0-282B with Corrigendum 1 page 29-30

  21. Ground Uplink Payload (App Data) The frame on the left breaks down the payload into the UAT-specific header and information frames. Ref: RTCA D0-282B with Corrigendum 1 page 27

  22. Ground Segment App Data Field • For uniquely defined Avian TIS-B (or FIS-B) Frame Type, we can define the Application Data field • Further investigation is needed into: • ATC secondary radar TIS-B formats • Avionic manufacturers formats. • Plan to leverage ADS-B Segment (e.g., typically transmitted from aircraft) message formats • Recall each Ground Segment and ADS-B Segment message is 5.5ms in length • Following details of ADS-B Segment messages will be applied for Avian Ground Segment TIS-B message formatting. Ref: DO-338 Minimum Aviation System Performance Standards (MASPS) for ADS-B Traffic Surveillance Systems and Applications (ATSSA), pdf, pg 80/294.

  23. Ground and ADS-B Uplink Frames Synchronization: 111010101100110111011010010011100010 ADS-B Message Frame Synchronization: 000101010011001000100101101100011101 Ground Uplink Message Frame Ref: RTCA D0-282B with Corrigendum 1 pp 24-25

  24. ADS-B Payload Composition • These are the essential elements to a message sent in the ADS-B frame. They are defined in later slides. Ref: RTCA D0-282B with Corrigendum 1 page 32

  25. Surveillance State Vector Definition Ref: RTCA, DO242A Minimum Aviation System Performance Standards (MASPS) for ADS-B Section 3.4.3.1.1 Table 3-6

  26. ADS-B Payload Composition These are the essential elements to a message sent in the ADS-B frame. They are defined in later slides. Ref: RTCA D0-282B with Corrigendum 1 page 32

  27. Mode Status (MS) Report Definition • Call Sign: Up to 8 alphanumeric symbols (e.g. BIRD1, DUCK, FLOCK, etc) • Emitter Category: Identifies the type of target being reported (defined on next slide) • A/V Length and Width Codes: Indicates size of target (e.g. flock size) Ref: RTCA, DO-242A Minimum Aviation System Performance Standards (MASPS) for ADS-B, Table 3-8, pg. 119, 135/475, June 25, 2002.

  28. Emitter Category • The MS Emitter Category (Section 3.4.4.5 referenced to Section 2.1.2.2.3) determines the type of target being reported. • Use cluster/point targets depending on what is detected • Also possibility that one of the unassigned values can be assigned as a bird category Ref: RTCA, DO286B Minimum Operational Performance Standards (MOPS) for ADS-B, Page 90 Table 2-42.

  29. Possible Avian Display Symbology • FAA investigated three different potential display formats for avian reports: • Text • Target, for display on the Standard Terminal Automation Replacement System (STARS) • Supervisor. Speed Direction Altitude Avian Symbol • Yellow: Medium priority (i.e., advisory) • Blue: Low priority Ref: Anton Koros, ANG-C43, Wildlife Surveillance Concept (WiSC), Socialization Briefing,ANG-C5 Brief, June 25, 2015

  30. Conclusion • Continue to define methodology to take avian radar target detections and produce avian target reports, suitable for transmission in the NAS to reduce bird strikes. • Recent efforts have refined the UAT TIS-B message formatting. • Avian TIS-B messages uniquely identified with Frame Type • Additional definition of Application Data field to be further investigated (ADS-B Segment like message or new format)

  31. Ohio University Research Plans • Continue development • Provide Quarterly Updates to the FAA via the JUP, with plans to concentrate on: • Continuing to evaluate overall approach • Avian Radar output requirements and capabilities • TIS-B data link formats • FIS-B data link formats

  32. Bird Strike Mitigation for Aviation Christopher Drummond Graduate Studies, School of EECS Chris G. Bartone, Ph.D., P.E., Professor, School of EECS Russ College of Engineering and Technology Ohio University, Athens, OH USA For additional information: Chris Bartone, Ph.D., P.E. Professor, School of EECS 740-593-9573 (o) 740-591-1660 (m) bartone@ohio.edu Comments/Questions/Suggestions???

  33. Target State Definition Ref: RTCA, DO242A Minimum Aviation System Performance Standards (MASPS) for ADS-B, p. 146

  34. TIS-B Target State Vector Definition Ref: RTCA, DO286B Minimum Aviation System Performance Standards (MASPS) for TIS-B, Table 3.3, pg. 33.

  35. Reed-Solomon FEC Parity • FEC Parity is achieved using a systematic RS 256-ary code with 8-bit code bytes • The first parity bit is treated as the Most Significant Digit (moving rightwards to Least Significant) • RS code is defined over a Galois field GF(28) , and all the non-zero elements can be described as roots of a polynomial; so, the primitive polynomial of the encoding using binary coefficients is given as: • p(x)= x8 + x7 + x2 + x + 1 Ref: RTCA, DO282B Minimum Operational Performance Standards (MOPS) for UAT p. 31-32 and Appendix C

  36. Interleaving for FEC Parity • The “Interleaved Payload and FEC Parity” consists of 6 interleaved RS blocks • The Interleaver is a 6x92 matrix where each entry is an 8-bit RS symbol • Each row comprises a single RS(92,72) block as shown above • The blocks are transmitted down the columns, then left-to-right Ref: RTCA D0-282B with Corrigendum 1 page 32

  37. ASTERIX All-Purpose STructuredEurocontrolSuRveillanceInformation Exchange • EUROCONTROL Standard • Primarily used by Air Traffic Control (ATC) Centers • ATM Surveillance Data Binary Messaging format (and ASCII) • Allows transmission of harmonized information between any surveillance and automation system • Suitable for real-time implementation • For specific applications, data items are able to be grouped into 256 separate categories • Defines structure of data to be exchanged over communication medium • Support for Presentation (6) and Application (7) layers as defined by the OSI Model Ref: ASTERIX Overview http://www.eurocontrol.int/asterix

  38. Participant Address and Address Qualifier • The Participant Address (24 bits) is a unique identifier for all ADS-B participants. • Address Qualifier “3” (encoding shown above) specifies that as the TIS-B data source, the stand-alone system is enabled to assign an address to any and all targets it detects. Ref: RTCA DO-282B § 2.2.4.5.1.3.4 • Thus, Avian radar can assign domain specific 24 bit address with appropriate Address Qualifier of “3”. Ref: RTCA, DO282B Minimum Aviation System Performance Standards (MASPS) for TIS-B p. 64 Table 2-12

  39. MS Call Sign Field • ADS-B participants call sign: • Up to 8 alphanumeric characters, capital letters A-Z and digits 0-9, and “-” • Considerations for avian targets • BIRD • BIRD-SML, BIRD-MED, BIRD-BIG • FLOCK • DUCK Ref: RTCA, DO-242A Minimum Aviation System Performance Standards (MASPS) for ADS-B, Table 3-8, pg. 118, 136/475, June 25, 2002.

  40. MS A/V Length and Width Codes The width and length of aircraft are encoded by these four bits. The appropriate bit sequence for a cluster target (ie flock of birds) will be assigned by this (Section 3.4.4.6 table 3-10) Ref: RTCA, DO242A Minimum Aviation System Performance Standards (MASPS) for ADS-B, p. 138

  41. Air-Referenced Velocity Definition Optional message transmission, not required at all times. Can be useful to ATC and pilots regarding moving targets when this information is known and able to be transmitted. Ref: RTCA, DO242A Minimum Aviation System Performance Standards (MASPS) for ADS-B, p. 144

  42. Avian Targets as TSAAs Investigating reporting Avian Targets as Traffic Situational Awareness Alerts (TSAA) with ADS-B IN, to provide: Alerts to flight crew to mid-air and near mid-air collisions Voice annunciations to flight to draw attention2 Adds visual cues to Traffic Displays2 Aids in visual acquisition and avoidance of traffic in both Visual Meteorological Conditions and Instrumented Meteorological Conditions; applicable under Visual Flight Rules (VFR) and Instrument Flight Rules (IFR)1 TIS-B information to flight crew with indications of nearby avian activity to support see-and-avoid2 The alert is intended for airborne conflicts.1 Supported at an update 2 sec (requires additional verification)1 Alerts specified at 2 sec, but max rate is 1 Hz for 1090 and UAT for airport Surface Detection Equipment, Model X (ASDE-X) tracks. Ref 1: DO-338 Minimum Aviation System Performance Standards (MASPS) for ADS-B Traffic Surveillance Systems and Applications (ATSSA), pdf pg 28/294, and pg 82/294. Ref 2: DO-348 Safety, Performance and Interoperability Requirements Document for Traffic Situation Awareness with Alerts (TSAA), pdf pg 67-68/226.

  43. FIS-B Avian Information • Avian activities could be collected and formatted on a FIS-B for advisory purposes: • More specific/detailed avian advisory than is currently broadcast on ADAS (Automated Weather Observing System (AWOS) Data Acquisition System (ADAS)). • Could be used to collect historical data on avian activity at a particular airport (some of which is done manually today). • FIS-B data could be used to illustrate avian regions of activity (i.e., similar to broadcast weather text and graphics information).

  44. Ref: DO-338 Minimum Aviation System Performance Standards (MASPS) for ADS-B Traffic Surveillance Systems and Applications (ATSSA), pdf, pg 35/294.

  45. 1090ES ADS-B Transmission Ref: RTCA D0-260B With Corrigendum 1 pp 95 & 64

  46. FIS-B Avian Information • Avian activities could be collected and formatted on a FIS-B for advisory purposes: • More specific/detailed avian advisory than is currently broadcast on ADAS (Automated Weather Observing System (AWOS) Data Acquisition System (ADAS)). • Could be used to collect historical data on avian activity at a particular airport (some of which is done manually today). • FIS-B data could be used to illustrate avian regions of activity (i.e., similar to broadcast weather text and graphics information).

  47. Traffic Information Service-Broadcast (TIS-B) • Broadcasts information to the cockpit (TIS client) via Mode S (1090ES) data link or Universal Access Transceiver (UAT) • Similar to VFR radar traffic information normally received over voice radio • Provides a situational awareness display to the pilot for up to 8 “intruder” aircraft within 7 nmi horizontal distance (time of potential contact <34 s): • estimated position, altitude, altitude trend, and ground track • +3,500 and −3,000 ft vertically of the TIS client • Provides data updates every 5 sec (commensurate with ground radar update rate) • Both TIS client, and possible intruder aircraft: • Have to be TIS equipped (minimum of transponder (Mode A, C or S)). • Within range of the ground TIS, Mode S radar (< 55 nmi) • TIS-Broadcast (TIS-B) provides ADS-B equipped aircraft with data on non-ADS-B equipped aircraft

  48. Ohio University Research Plans: Overview Avian Surveillance System GPS 1090ES & UAT ADS-B IN Avian Radar System Target Categorization and Validation Format Aviation Target Reports Radio Transmit Target Detections & Performance parameters TIS-B FIS-B UAT

  49. Ohio University Research Plans:Target Categorization & Risk Assessment Considering: Avian target detections requirements Avian radar output capabilities Investigate best place to do Target Categorization and Risk Assessment: Within avian radar systems Separate processor (external to radar) Interface and parameter production requirements Implement external parameters: Bring in ADS-B-IN to display actual A/C flight path Airport surface database (i.e., runway locations) Weather, etc.

  50. Ohio University Research Plan:Target Report Formatting Take validated target detections and create TIS-B Track Reports Categorize Track Reports and output Target Reports Format Target Reports in a standard aviation format, suitable for distribution Investigate Automatic Dependence Surveillance-Broadcast (ADS-B) integration: Universal Access Transceiver (UAT) Traffic Information Service – Broadcast (TIS-B) Flight Information System – Broadcast (FIS-B) Will focus on UAT due to both TIS-B and FIS-B options being available 1090 MHz Extended Squitter (1090ES) Traffic Information Service – Broadcast (TIS-B) only

More Related