National and International Aviation Data Standards

1
National and International Aviation Data Standards
International data standards, data architecture,
and their use in FAA data standardization
Near Mid-Air Collision System
Open Forum 2003 on Metadata Registries Day 3, 2
pm Rick Jordan, FAA Information Management
Division within the Office of the CIO With Burton
Parker FAA Data Registry Administrator January
2003
2
Outline

• Part I Emerging International Aviation Safety
  Data Standards
• Part II FAA Data Architecture and Standards
• Part IV Star Data Structure for Aviation Safety
• Time permitting Translation of an Incidents
  data into Tables

3
Part I Emerging International Aviation Safety
Data Standards

• CAST/ICAO Common Taxonomy Team
• CAST Commercial Aviation Safety Team
• ICAO International Civil Aviation Organization

4
Objective of the CAST/ICAO Common Taxonomy Team

• Common terms, definitions, and taxonomies for
  aviation accident/incident reporting systems to
  enable world-wide coordination and focus on
  common safety agendas
• Published to a Web site for downloading
• Draft Site www.intlaviationstandards.org
• Focus is on reference table data including an
  internationally accepted list of valid values for
  
• Phase of Flight
• Aircraft identification groupings (make, model,
  and series)
• Types of Accidents and Incidents (occurrences)

5
Background - Basis for the need

• Lack of International Standards for Aviation
  Safety Data
• Some are available, but no international
  agreement on them to support categorization and
  aggregation of aviation accidents and incidents
• Civil Aviation Authority data standards FAA,
  NTSB, Canada, UK CAA, etc.
• ICAO aircraft type designator for air traffic
  control purposes
• ATA Spec 100 and 2200
• Bureau Veritas participation of UK, France and
  Italy CAAs offering aviation data
• Lays Foundation For
• Worldwide Sharing Of Common Accident/incident
  Data
• Focused, Data Driven, Coordinated Safety Agenda
• Common Investigation/reporting And Post Accident
  Analysis
• Shifting From Reactive To Proactive Safety
  Assessment
• Team meets every 6 months (since 2/99)

6
Team Composition

• Organizations participating
• Commercial Aviation Safety Team International
  Civil Aviation Organization
• National Transportation Safety Board
• Federal Aviation Administration
• National Aeronautics and Space Administration
• USAF Safety Center
• Transport Canada
• Transportation Safety Board -Canada
• Civil Aviation Authority- United Kingdom
• National Aerospace Laboratory- Netherlands
• BEA- France
• Eurocontrol
• Aircraft Accident Investigation Center(Japan)
• Airline Pilots Association
• International Society of Air Safety
  Investigators Airbus Industries
• Boeing

Pratt and Whitney General Aviation Manufacturers
Assn Volpe National Transportation Systems
Center Air Claims, Ltd. Bureau Veritas ....an
d growing additional international outreach
underway
7
Recent Activities

• Released Products
• Aircraft Make/Model Series Code Common Taxonomy
• Aviation Occurrence Categories (types of
  accidents and incidents)
• Phase of Flight Definitions
• Sub- Teams created and working the following
• Engine Make/Model/Series Code Common Taxonomy
• Web site in draft mode www.intlaviationstandards.
  org

8
Aviation Occurrence Categories (Accidents
Incidents)
Excerpt
9
Phases of Flight Excerpt from Oct. 2002
10
The Aircraft Identification Problem

• How the same type of aircraft is named in
  different systems

11
Airbus A300 - Make/Model/Series
Same System Different FormatsDifferent Systems
Different Formats
Airclaims (UK, private)
Near Mid-Air Collision System
Service Difficulty Reporting System
FAA Aircraft Registry
National Transportation Safety Board
As of 6/99 With assistance from McFadden Assoc.
Inc.
12
CAST/ICAOs Solution Aircraft Identification

• Provide standard definitions and formats for key
  identifying terms
• Aircraft make, model, series, etc.
• Business Rules document
• Publish a clean list of valid values from a Web
  site and support downloading of that list
• Example Aircraft Make
• Definition The name assigned to the aircraft by
  the manufacturer when each aircraft was produced.
  In most cases aircraft make is the organisation
  common name of the aircraft manufacturer. If the
  organisation that holds rights to an aircraft
  design permits another organisation to build that
  aircraft, in most cases the aircraft make would
  be the aircraft name assigned by the organisation
  that holds rights to an aircraft design. If an
  aircraft manufacturer is amateur construction, in
  most cases the aircraft make would be the name of
  the organisation responsible for design.
• Valid Values
• AGUSTA
• BELL
• CESSNA
• HAWKER SIDDELEY

13
Example Aircraft Model

• Definition An aircraft model is an aircraft
  manufacturers designation for an aircraft
  grouping with similar design or style of
  structure.
• Sample Rules
• The aircraft model is listed in the aircraft type
  certificate.
• The aircraft model when concatenated with the
  aircraft make must be unique in order to identify
  that aircraft grouping.
• The aircraft model must not contain a space as a
  separator between alpha and numeric characters
  (for example, use 269A, not 269 A).
• The aircraft model may not contain a dash (-),
  slash (/), or other special character.

14
Use of these Taxonomies in FAA

• Proposed FAA Aircraft identification data
  standard is based on it
• Entered into our FDR as candidate data standards
• In review for formal approval
• Planning to propose data standards for two kinds
  of reference data
• Flight_phase_code Phase of Flight
• Use the international list as the set of
  permissible values
• Occurrence_type_code types of accidents and
  incidents
• Use the international list as the set of
  permissible values

15
Part II FAA Data Architecture and Standards

• FAA data architecture
• Priorities for FAA data standardization
• Application of 11179 in data element standard
  naming
• Relationship of Data Architecture to Data
  Standardization

16
Subject Areas

• FAA Data Architecture consists of 8 subject area
  diagrams
• In Entity-Relationship format
• Conceptual data models with partial logical
  detail (selected attributes and primary keys)
• All entities have definitions.

17
FAA Data Architecture Top Level - Conceptual
18
Priorities for Data Standardization in the FAA
thus far

• Upcoming NAS modernization programs potential
  to provide data standards that can be built into
  these new automation systems
• Pressing data quality problem areas
• System security
• Reference data greater payoff potential

19
Data Architectures Entities and 11179

• FAA Data
• Architecture
• brings the business into our naming practices

Proposed Data Standards
Existing FAA Data Elements
(Can include list of Permissible values)
20
Data Standard Example
 
Data naming convention Object Class_Property_Valu
e Domain
Airport_Type_code
 
21
Part III Star Data Structure for Aviation
Safety

• Useful for Database Design of Data Marts and Data
  Warehouses relating to Aviation Hazards
• Broadly applicable to all modes of transportation
• A Future Concept

22
Safety Event Data

• Definitions
• Safety Event is an unplanned and undesired
  aviation accident or incident. It may exist for
  an aviation asset or aviation asset type/model
• Event Factor (includes hazard) is a state,
  condition, or action that occurred during a
  Safety Event. It includes all events in a string
  making up an unplanned safety event including
  corrective, negative, and normal aspects.
• Shows the dimensions of a safety event the
  who, what, when, where, why how
• Some of these dimensions are subject to
  standardization efforts for a common taxonomy or
  standard reference list of values
• Indicates the relationship scope of taxonomy
  efforts

23
Star Data Structure for Aviation Safety Safety
Event Pattern Applicable to Other Transportation
Modes
Safety Events Factors Data, Reference/Dimension
Data
Reference Data (i.e. dimensions)
Event Factor Category code tables (i.e.
taxonomies)

• Safety Events
• Event Type/Category
• Party/Carrier ID
• Place/Infrastructure
• Vehicle/Aircraft Type

Person/Party Role Type
Safety Event / Accident Category
who
what event
Place / Transportation Infrastructure
where
Classification Scheme
contains
defines
part of
Period
when

• Safety Factors
• Factor Type / Category
• Factor Value

Safety Factor / Precursor Category
Product / Vehicle Type Model
why how
what object
24
Star Data Structure for Aviation Safety In
More Detail
June 15, 2001
Aircraft / Other Asset Reference Data
Reference Data (Dimensions Taxonomies)
Aircraft / Asset Type aircraft model (e.g. Boeing
747-200C) engine type/model (e.g. GE XY) other
aircraft equipment / component ATC equipment
type/model
is a
embodied in
Aircraft / Other Asset (events primary subject)
e.g. aircraft instance, ATC asset
Event Category e.g. runway incursion, CFIT,
categorizes
What events happen?
comprises
has
has
involved in
comprises
involved in
of
Operation/Service Type e.g. commercial, GA,
what subject
what object

• Failure Mode
• - severity
• likelihood / rate
• failure effects

what

• Safety Event (accident,
• incident, hypothetical scenario)
• - What happened? (big picture category)
• - When it happened? (service,phase,flight)
• Where it happened? (coordinates,airport)
• Who it happened to? (air carrier/operator)
• What aircraft it happened to? (by tail)
• What aircraft model it happened to?
• What other objects/assets were involved?

Phase of Flight
when
Flight, Flight Event
How a thing breaks?
of
circumstance of
When events happen?

• Preventive Maintenance Requirement / Task
• required task frequency

location of
Airspace Class
where
Airspace Structure Sector, Route, Fix,
What tasks prevent failures?
who
has
Airport / ATC Facility
of
how why
what object
Hazard/Risk Factor Category human factor
category, technical failure by ATA code, external
environment (weather)
Where events happen?
is a

• Event Factor (events tree,
• causal factor, hazard, outcome)
• - what aircraft/asset component failed
• - what material/cargo type was involved
• what Failure Mode, Factor Category it is
• what operation / maintenance task it is
• who was involved (role rather than name)
• how it happened (preceding events)
• why (causal/contributing factor, hazard)

is a
where
Organization / Person and air carrier system
elements (e.g. maintenance personnel)
operator for
What hazards exist?
related to
involved in
concerns
who
Role / Responsibility pilot, crew, mechanic,
manager, traffic controller, inspector,
Safety Rule / Standard FAR, Visual Flight Rules,
involved in
who
What controls/standards exist?
Who was involved?
related to
Database / System
How Why did events happen?
source of
Where did data come from?
25
Conclusion

• Working on reference data standardization at the
  international level
• Using a 11179 compliant method to shape data
  standards in the FAA
• Using the FAA Data Architecture as an input to
  crafting data standards especially for object
  class naming
• Star Structure for Transportation Accidents and
  Incidents reviewed

26
Useful References

• Brackett, Michael. Data Sharing Using a Common
  Data Architecture, John Wiley Sons Inc., New
  York, 1994.
• Chisholm, Malcolm, Managing Reference Data in
  Enterprise Databases, 2001.
• Cook, Melissa A. Building Enterprise Information
  Architectures Reengineering Information Systems.
  Upper Saddle River, New Jersey Prentice-Hall,
  Inc., 1996.
• Hay, David C. Data Model Patterns Conventions of
  Thought, Doset House Publishing, New York, 1996.
• FAA Data Modeling Process, Federal Aviation
  Administration, Office of Information Services
  and Chief Information Officer, Version 1.0, dated
  September 26, 2001.
• Federal Enterprise Architecture Framework, Chief
  Information Officer (CIO) Council, Version 1.1,
  dated September 1999.
• A Practical Guide to Federal Enterprise
  Architecture, Federal Architecture Working Group
  (Federal Chief Information Officer Council),
  Version 0.9, 2/2/2001 (Draft)
• Purba, Sanjiv (editor). Handbook of Data
  Management 1999, CRC Press LLC, Boca Raton, 1999.
• Spewak, Steven H. Enterprise Architecture
  Planning Developing a Blueprint for Data,
  Applications and Technology, John Wiley Sons
  Inc., New York, 1992.
• Whitemarsh Information Systems Corp., Achieving
  Data Standardization, 1997. (www.wiscorp.com )
• Zachman, John. A Framework for Information
  Systems Architecture, IBM Systems Journal, Vol.
  26, No. 3, 1987.

Rick Jordan, 781-238-7372 Visit our FAA/AIO-300
Web Site - http//www.faa.gov/aio/InfoMgmt/index.h
tm
27
Appendix Translation of An Incidents Data into
Tables
28
Accident/Incident Hazard Portion of Data Model
Safety Event
Causal Chain of Events
System Safety Concepts of Severity Likelihood
29
Application of this Database Design to an
Aviation Incident
NTSB Identification DCA991A019 Scheduled 14
CFR 121 operation of DELTA AIRLINES Incident
occurred DEC-06-98 at NEAR HAMPTON, NY Aircraft
Boeing 767, registration UNK Injuries 0 On
December 6, 1998, about 2200 eastern standard
time, Delta Airlines flight 66, a Boeing 767, and
Caledonian Airways flight 5199 (CKT5199), a
Lockheed L1011, were involved in a near midair
collision approximately 10 miles south of
Hampton, New York at 33,000 feet (FL330) mean sea
level. Both flights were being handled by the
Boston Air Route Traffic Control Center (Boston
Center) According to the FAA, at 2145 the Boston
Center computer display channel (CDC) failed and
the direct access radar channel (DARC) equipment
loss its ability to interface with the National
Airspace System (NAS). Because of this, most of
the aircraft identification, track, and flight
plan data normally displayed on controllers
radar displays, were unavailable. (Transponder
beacon codes and Mode C altitude information
continued to be displayed.) The radar controller
accepted a handoff from New York Center on DAL66
level at FL330. The same radar controller then
accepted a radar handoff on CKT5199 Level at
FL330. The flights were on converging courses.
The flight crew of DAL66 received a traffic alert
and collision avoidance system (TCAS) resolution
alert (RA) to descend, and the Flight crew of
CKT5199 received a TCAS RA to climb. At 0300
UTC, the two airplanes passed each other with 1.5
miles horizontal and 900 feet vertical
separation. The pilot of CKT5199 reported
sighting DAL66 and said he would file a near
midair condition report.
30
Event Factors for Near Mid-Air Collision Delta 66
8. CDC Failure
7. Loss of Radar Display
3.Evasive Action (Descend)
9. DARC Capability Loss
6. Incorrect Navigation Directions
4. TCAS Alert
2.Evasive Action (Climb)
5. Loss Of Separation
10. Caledonian 5199 Approach
1. Near Mid-Air Collision
11. Delta 66 Approach
31
Translation into Data Tables
Sample Tables