Skip to main content

Analysis of general aviation single-pilot IFR incident data obtained from the NASA Aviation Safety Reporting System

· NASA (NTRS) · 1983

Public domain · NASA (NTRS)Technical Reports

Overview

An analysis of incident data obtained from the NASA Aviation Safety Reporting System (ASRS) has been made to determine the problem areas in general aviation single-pilot IFR (SPIFR) operations. The Aviation Safety Reporting System data base is a compilation of voluntary reports of incidents from…

Publisher
NASA (NTRS)
Document
Year
1983
Pages
7

Document

ANALYSIS OF GENERALAVIATION SINGLE-PILOT IFR INCIDENT DATA OBTAINED FROMTHE NASA AVIATION SAFETY REPORTINGSYSTEM Hugh P. Bergeron NASA Langley Research Center An analysis of incident data obtained from the NASA Aviation Safety Reporting System (ASRS) has been made to determine the problem areas in general aviation single-pilot IFR (SPIFR) operations. The Aviation Safety Reporting System data base is a compilation of voluntary reports of incidents from any person who has observed or been involved in an occurrence which was believed to have posed a threat to flight safety. This paper examines only those reported incidents specifically related to general aviation single-pilot IFR operations. The frequency of occurrence of factors related to the incidents was the criterion used to define significant problem areas and, hence, to suggest where research is needed.

The data was cataloged into one of five major problem areas: (1) controller judgment and response problems, (2) pilot judgment and response problems, (3) air traffic control (ATC) intrafacility and interfacility conflicts, (4) ATC and pilot The relative significance of communication problems, and (5) IFR-VFR conflicts.

each of these problem areas was determined by the number of citations corresponding to each area. In addition, several points common to all or most of the problems were observed and reported. These included human error, communications, procedures and rules, and work load.

The ASRS incident data analyzed in this report is limited to the general aviation operations typically involved in SPIFR. Since no specific category in the ASRS data base relates directly to general aviation SPIFR, the following criteria were chosen in interrogating the data base. All fixed-wing operations under air taxi, charter operations, utility operations, corporate aviation, qersonal business, pleasure flights,. and training flights were selected for the analysis. All rotary wing operations were deleted. Also, only those flights on either an IFR or SVFR flight plan were used. These criteria produced 79 reports out of the total 2174 reports collected during the period from May 1, 1978 (the beginning of ASRS report reformatting) to January 1, 1979.

Based on their sources, these 79 reports included pilot reports of flight crew errors (14 reports), ATC reports of flight crew errors (15 reports), pilot reports of ATC errors (16 reports), and ATC reports of ATC errors (34 reports).

FORMULATION OF INCIDENT DATA ALL FIXED-WING OPERATIONSUNDERAIR TAXI, CHARTEROPERATIONS, UTILITY OPERATIONS, CORPORATE AVIATION, PERSONALBIJSINESS, PLEASURE FLIGHTS, AND TRAINING FLIGHTS ON EITHER AN IFR OR SVFR FLIGHT PLAN The incident data reports consisted of a synopsis and several categories of factors related to the incidents. These categories included enabling factors, associated factors, descriptors, recovery factors, and supplemental key words.

Only two of these, enabling factors and associated factors, were considered relevant to this study and were used in the analysis. An enabling factor is an element that is present in the history of an occurrence and without which the occurrence probably would not have happened.

An associated factor is an element that is present in the history of an occurrence and is pertinent to the occurrence under study, but which does not fulfill the requirements of an enabling Examples of both enabling and associated factors are controller factor.

perception, intrafacility coordination, pilot discretion, and pilot vigilance.

There were 40 different enabling factors and 58 associated factors listed in the 79 incident reports. The 40 enabling factors were cited a total of 99 times; the 58 associated factors were cited 82 times.

(A factor citing is a listing of that factor in the incident report.) These data imply that more than one factor was cited in some of the incident reports.

DATA ANALYSIS CRITERIA AN ELEMENTTHAT IS PRESENTIN THE HISTORY ENABLING FACTOR (40): OF AN OCCURRENCE AND WITHOUTWHICH THE OCCURRENCE PROBABLYWOULD NOT HAVE HAPPENED.

ASSOCIATEDFACTOR (58): AN ELEMENTTHAT IS PRESENTIN HISTORY OF AN OCCURRENCE AND IS PERTINENT TO THE OCCURRENCE UNDERSTUDY, BUT WHICH DOES NOT FULFILL THE REQUIREMENTS OF AN ENABLING FACTOR.

o CONTROLLER PERCEPTION EXAMPLES: 0 INTRAFACILITY COORDINATION o PILOT DISCRETION 0 PILOT VIGILANCE The ASRS synopsis and various categories assigned to each reported incident were examined by the author to determine the types of problems suggested by the data. This review of the incident reports revealed five major problem areas that were considered to be general aviation SPIFR specific. These problem areas (2) pilot judgment and response are (1) controller judgment and response problems, problems, (3) ATC intrafacility and interfacility conflicts, (4) ATC and pilot communication problems, and (5) IFR-VFR conflicts.

o CONTROLLER JUDGMENT AND RESPONSE PROBLEMS o PILOT JUDGMENT AND RESPONSE PROBLEMS o ATC INTRAFACILITY AND INTERFACILITY CONFLICTS o ATC AND PILOT COMMUNICATION PROBLEMS o IFR-VFR CONFLICTS III1 I I The analysis of the data showed that the problem areas could be described by more specific subelements. The "controller judgment and response problems", for example, can be primarily attributed to three elements: (1) excessive/ impeding procedural requirements, (2) training/proficiency/experience related mistakes, and (3) equipment operational problems.

Similarly, "pilot judgment and response problems" can be attributed primarily to three elements: (1) excessive/ impeding procedural requirements, (2) training/proficiency flight infractions, and (3) limitations due to limited avionics. These problem elements can be used to determine the areas that need further research.

o CONTROLLER JUDGMENT AND RESPONSE PROBLEMS -EXCESSIVE/IMPEDING PROCEDURAL REQUIREMENTS -TRAINING/PROFICIENCY/EXPERIENCE RELATEDMISTAKES -EQUIPMENT OPERATIONALPROBLEMS o PILOT JUDGMENT AND RESPONSE PROBLEMS -EXCESSIVE/IMPEDING PROCEDURAL REQUIREMENTS -TRAINING/PROFICIENCY FLIGHT INFRACTIONS -LIMITATIONS DUE TO LIMITED AVIONICS o ATC INTRAFACILITY AND INTERFACILITY CONFLICTS -INTERNAL COMMUNICATION PROBLEMS -HAND-OFF PROBLEMS -MIXED DEPARTURE AND ARRIVAL CONFLICTS -EQUIPMENT OPERATIONALPROBLEMS o ATC AND PILOT COMMUNICATION PROBLEMS -MISUNDERSTANDING OF INSTRUCTIONS -FREQUENCY CONGESTION -EXCESSIVE FREQUENCY CHANGES -EXCESSIVE/IMPEDING PROCEDURAL REQUIREMENTS o IFR-VFR CONFLICTS -AIRCRAFT PROXIMITY AT BREAKOUT -1FR FLIGHT IN VFR AND MVFR CONDITIONS A review of the problem areas pinpointed several points common to all or most of the problems. These included human error, communications, procedures and rules, and work load.

COMMON DENOMINATOR TO ALL PROBLEM AREAS o HUMANERROR o COMMUNICATIONS o PROCEDURES AND RULES o WORKLOAD BIBLIOGRAPHY Bergeron, Hugh P.: Analysis of General Aviation Single Pilot IFR Incident 1.

Data Obtained from the NASA Aviation Safety Reporting System.

NASA TM-80206, 1980.

2. Forsyth, Donna L,; and Shaughnessy, John D.: Single Pilot IFR Operating Problems Determined from Accident Data Analysis. NASA TM-78773, 1978.

3. Billings, Charles E.; Lauber, John K.; Funkhouser, Hallie; Lyman, E. Gene; NASA Aviation Safety Reporting System.

and Huff, Edward M.: Quarterly Report Number 76-1, April 15, 1976 through July 14, 1976. NASA TM X-3445, 1976.

4. NASA Aviation Safety Reporting System: Second Quarterly Report, July 15 - October 14, 1976. NASA TM X-3494, 1976.

Third Quarterly Report, 5. NASA Aviation Safety Reporting System: October 15, 1976 - January 14, 1977. NASA TM X-3546, 1977.

Fourth Quarterly Report, 6. NASA Aviation Safety Reporting System: January 15, 1977 - April 14, 1977. NASA TM-78433, 1977.

7. NASA Aviation Safety Reporting System: Fifth Quarterly Report, April 1 - June 30, 1977. NASA TM-78476, 1978.

NASA Aviation Safety Reporting System: 8. Sixth Quarterly Report, July 1, 1977 - September 30, 1977. NASA TM-78511, 1978.

Seventh Quarterly Report, 9. NASA Aviation Safety Reporting System: October 1, 1977 - December 31, 1977. NASA TM-78528, 1978.

10. NASA Aviation Safety Reporting System: Eighth Quarterly Report, January 1, 1978 - March 31, 1978. NASA TM-78540, 1978.

Hoffman, William C.; and Hollister, Walter M.: Forecast of the General 11.

Aviation Air Traffic Control Environment for the 1980's. NASA CR-137909, 1976.

L

Source & rights

Source: ntrs.nasa.gov. Public-domain U.S. Government work (17 USC §105) — freely reproducible.

Permanent URL — we don’t break links.

Document details

Doc number
Publisher
NASA (NTRS)
Year
1983
Pages
7
File size
320 KB