Collecting and Sharing of Operations and Safety Data (2020) / Chapter Skim
Currently Skimming:
Pages 63-74
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 63... ...
63 Developing an Operations and Safety Database Chapter 4 describes considerations for developing an operations and safety database, asso ciated challenges, and a method for collecting and sharing operations and safety data internal to airports for the purpose of improving riskbased decisionmaking at an airport. 4.1 Motivation The collection of operations and safety data internal to airports is primarily driven by the federal mandates of 14 CFR Part 139, Airport Certification.
|
From page 64... ...
64 Collecting and Sharing of Operations and Safety Data Operations data at airports is generally measured in terms of the volume and character of aircraft movements or passenger activity and is recorded on a regular basis (daily/monthly/ annually) by the airport or through a variety of federal resources.
|
From page 65... ...
Developing an Operations and Safety Database 65 At an individual airport, the data can be useful for discerning unforeseen conditions, and to identify policies, practices, and trends that may require mitigation. By sharing the data with others, the collective understanding of common safety risks that can be avoided may be achieved, and in many cases, the development of a forum for sharing lessons learned and best practices to avoid future safetyrelated events.
|
From page 66... ...
66 Collecting and Sharing of Operations and Safety Data specific circumstances can be entered by checking the appropriate boxes. The report data will eventually have to be manually transcribed and entered into a digital database to be useful.
|
From page 67... ...
Developing an Operations and Safety Database 67 by their state laws to disclose public records (upon request)
|
From page 68... ...
68 Collecting and Sharing of Operations and Safety Data to anonymously report safetyrelated incidents. The ASRS database is available for querying and reporting relevant data to specific inquiries.
|
From page 69... ...
Developing an Operations and Safety Database 69 Other AOX Checkbox/Alpha Experience (EX) 2 years or less EX1 Checkbox (Y/N)
|
From page 70... ...
70 Collecting and Sharing of Operations and Safety Data Airplane P1R Checkbox (Y/N) Helicopter P1H Checkbox (Y/N)
|
From page 71... ...
Developing an Operations and Safety Database 71 4.3.8 Results Allowing the user to identify results related to the event can also assist with lessons learned. Details on physical injuries, damage to aircraft vehicles or equipment, and evasive maneuvers or similar data resulting from the event should be identified to establish the significance and importance of the event.
|
From page 72... ...
72 Collecting and Sharing of Operations and Safety Data Field Name Code Format Remarks Event Location (EL) Runway (Active)
|
From page 73... ...
Developing an Operations and Safety Database 73 Event Response (ES) Multiple Entries Allowed Supervisor Dispatched ET1 Checkbox (Y/N)
|
From page 74... ...
74 Collecting and Sharing of Operations and Safety Data The metadata for each of these basic categories can be subdivided into specific data fields that serve as the taxonomy for the operations and safety database. Tables 41 through 48 are examples of a proposed taxonomy for an operations and safety database.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.