Quality Control: Quick Reference Guide

Back to Top

Table of Contents HOW TO USE THIS REFERENCE GUIDE .............................................................................................. 3 A WORD ON CEDAR ............................................................................................................................... 3 QA/QC: HOW YOU FIT INTO THE EQUATION ....................................................................................... 3 MAKING DESCRIPTIVE COMMENTS ..................................................................................................... 4 MONITORING ............................................................................................................................................... 5 OPERATIONAL SKILLS ASSESSMENTS (OSA) .................................................................................... 6 EMPHASIS ITEMS .................................................................................................................................... 8 SERVICE REVIEWS ................................................................................................................................... 10 SYSTEM SERVICE REVIEW (SSR)....................................................................................................... 11 TRAFFIC MANAGEMENT REVIEW (TMR) ............................................................................................ 13 COVERED EVENT REVIEW (CER) ....................................................................................................... 15 SYSTEMIC ISSUE REVIEW (SYSIR)..................................................................................................... 17 COMPLIANCE VERIFICATION.................................................................................................................. 19 INTERNAL COMPLIANCE VERIFICATION (ICV) .................................................................................. 20 EXTERNAL COMPLIANCE VERIFICATION (ECV) ............................................................................... 22 QC PROGRAMS ......................................................................................................................................... 24 OSA CHECKS ......................................................................................................................................... 25 ON THE JOB TRAINING CHECK ........................................................................................................... 27 EFFICIENCY CHECKS ........................................................................................................................... 29 SYSTEM PERFORMANCE CHECKS .................................................................................................... 31 OSA VALIDATIONS ................................................................................................................................ 33 CERTIFICATION SKILL CHECK VALIDATIONS ................................................................................... 35 ON THE JOB TRAINING DOCUMENTATION VALIDATION ................................................................. 37 REPORTING ............................................................................................................................................... 39 MORS ...................................................................................................................................................... 40 PILOT DEVIATION NOTIFICATIONS..................................................................................................... 42 NEAR MIDAIR COLLISIONS .................................................................................................................. 44 HATR/OHR .............................................................................................................................................. 46 VEHICLE/PEDESTRIAN DEVIATIONS .................................................................................................. 48 AIR TRAFFIC INCIDENT REPORT ........................................................................................................ 50

2

Quality Control: Quick Reference Guide

Back to Top

How to Use this Reference Guide The information provided here is meant to be a reference to help remind you how to fill out a report or steps to take in an incident. Refer directly to the orders for detailed information on actions to take, specific forms to file, etc.

A Word on CEDAR CEDAR is an important and powerful tool for all staff members, but it is important to remember that CEDAR is just a tool to assist you in filling out required forms and to stay organized. If CEDAR were to disappear today, you would still be required to fill out all necessary forms associated with your operational duties. Since CEDAR works as a digital version of these forms, understanding the forms will increase your effective use of CEDAR.

QA/QC: How You Fit Into the Equation The Quality Control function is a big part of the Safety Management System in the ATO. The primary goal is to collect data for analysis and finding potential risk. Without continuous, detailed data, it is difficult to find potential risk, so it’s important to collect and analyze as much data as possible. Every report matters! For example, let’s say a driver realizes his car doors are not locking properly. He takes the car to his mechanic, has them fixed, and goes on his way. Later that year, car mechanics meet at their annual convention to discuss everything related to car repair and the types of work they have done. Every mechanic says they’ve only done, “minor repairs.” Mechanics that don’t attend, don’t contribute. However, if every mechanic says, “I’ve fixed a door lock that had electrical problems between the switch and the lock,” it won’t take long to realize every mechanic has fixed the same problem, therefore the car model’s door locks are faulty and a recall needs to be performed. This is similar to the QC process. You never know if one of your reports documenting a minor, local problem will help QA recognize a pattern occurring nationwide.

3

Quality Control: Quick Reference Guide

Back to Top

Making Descriptive Comments When describing an event, it is important to use as much detail as necessary to give everyone involved an accurate picture of what happened. Descriptive Examples Poor description: “The plane went off the runway.” Better description: “After touching down, high wind shear and ice on the runway caused the tail of the plane to slide during a turn.” Poor description: “I couldn’t understand the pilot.” Better description: “At least once during every transmission from the pilot, the audio would cut to static requiring a repeat of nearly every communication. This did NOT happen with any other aircraft, so it was likely a problem from the aircraft.” Poor description: “The pilot didn’t know how to fly.” Better description: “Due to a medical emergency, the aircraft’s original pilot was unable to fly or communicate. A passenger with experience flying light aircraft took the controls, but was unfamiliar with the equipment.” Reviewing Your Descriptions After writing your report, you should ask yourself the following questions to determine if you should edit your description(s) of any incidents. 1. 2. 3. 4. 5.

Did I describe the event in chronological order? Does this explain exactly what happened, or did I just summarize the event? Would anyone need to ask follow-up questions to learn necessary details? Did I leave out any important information? Could any of my descriptions be confused with a different, but similar, incident?

NOTE: The more accurate and descriptive you are in these forms, the less likely anyone from Quality Assurance will contact you for more information!

4

Quality Control: Quick Reference Guide

Back to Top

MONITORING

5

Quality Control: Quick Reference Guide

Back to Top

Operational Skills Assessments (OSA)

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Manager, District Managers

WHAT

QC OSAs are a quality control monitoring method used to assess controller technical performance against the standard. All QC OSAs are anonymous and are conducted through indirect or direct observation.

WHEN

Facilities must conduct a number of QC OSAs that will ensure an accurate assessment of facility performance. Click here for recommended quarterly targets.

WHERE

WHY

Facility Level OSAs support other quality control processes and help give an accurate, overall picture of the facility personnel’s technical performance.

OSA: Best Practices • • • • • •

A QC OSA is separate from an IPM-OSA. They must not include any personally identifiable information and are not to be used to support individual performance. OSAs can be customized in CEDAR to your facility. (Example: If a facility doesn’t have radar, there is no need to address radar portions of the job.) Emphasis Items should be utilized within OSAs to enhance the ability to identify risk at the local level. OSAs may be done by physical or remote monitoring in real-time, or via playback tools. You are encouraged to use playback tools (FALCON, DALR, etc.) as the primary method. A common practice is to print the OSA Worksheet (3120-25) for making quick marks, then filling out the OSA later in CEDAR. Recommended monthly QC OSA targets are listed in ATO-SG-14-05.

6

Quality Control: Quick Reference Guide

Back to Top

How to Conduct an OSA 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. Under Safety, select the New OSA link. A pop-up window will now open titled OSA. 3. In the new OSA window, select the Type from the two radio button choices. 4. Next, select the Method from the two radio button choices. 5. Next, select the Job Function from the three radio button choices. This will open the Summary Information window. 6. In the Summary Information window, select Position. Then, select the Date, Start Time, and Stop Time. 7. In the next window National Emphasis Items, a table shows ten NEIs with corresponding references. Rate each ‘observed’ EI with one of the three options. 8. If you have any Facility Emphasis Items, you must rate any that have been observed. Note: You must create Facility Emphasis Items yourself. 9. In the next window Standard Items, the 24 OSA Job Subtask Default items are all listed under this window with three options to rate each that have been observed/identified. 10. In the next window Systemic Issues, you are asked, “Were any possible system issues identified?” a. If YES, you will then be asked to “Select the type of systemic issue identified” from the drop-down menu. Explain your reasoning. (Be detailed!) b. If NO, you will continue to the next window. 11. In the next window, Additional Comments add any helpful information and continue to the next window. (It is good practice to provide comments on all items observed during the review even those items that are not a listed subtask.) 12. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. You are encouraged to attach Falcon 3 Bookmarks, Replays, Voice Tapes, and any information that would be useful when reviewing the data. 13. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 14. Select Save Draft, Submit, or Cancel and the OSA has now been completed. 7

Quality Control: Quick Reference Guide

Back to Top

Emphasis Items (EIs)

WHO

QC Specialist or other designee.

WHAT

Emphasis Items are prioritized custom sub-tasks in OSAs that need extra attention and should be used to collect data on specific focus items for a period of time, defined by the facility.

WHEN

At all times, but no specific requirement. EIs should be created based on suspected issues, implemented CAPs, and potential, special focus issues.

WHERE

Facility Level There are three (3) primary purposes of EIs:

WHY

1. Corrective Action Plan (CAP) Monitoring 2. Collecting additional data to validate suspected trends or issues 3. Emphasizing special focus issues EIs allow you to go beyond gathering standard data and start looking at specifics.

Emphasis Items: Best Practices • • • • •

Emphasis Items are severely underutilized in the field! EIs are one of the most effective tools for finding issues at your facility. Emphasis Items can only be chosen from current standard items. Therefore, you may need to create something as a standard item first. It is strongly encouraged your facility set the TOP 5 as special Emphasis Items. Every facility is encouraged to create their own, local Emphasis Items. Each EI must have a defined start and stop time period. Select a time period that will ensure sufficient data is collected on the sub-task, a minimum of 90 days is recommended.

8

Quality Control: Quick Reference Guide

Back to Top

How to Create Emphasis Items 1. On the top menu bar of the CEDAR home screen, select the Configuration tab to open the Configuration window. 2. Select Configure OSAs and the OSA Configuration popup window will display. 3. In the Job Function window, choose from the three radio buttons. 4. Now in the Type window, chose Emphasis Items from the given options to display the Emphasis Items window. 5. Select Add Emphasis Item 6. Select an Emphasis Item from Select from the Current Standard Items the dropdown menu. 7. Enter a Start Date and End Date to specify the date range for this EI. 8. At the bottom of the Emphasis Item window, click OK, to display the OSA Configuration window. 9. In the OSA Configuration window, click Submit.

9

Quality Control: Quick Reference Guide

Back to Top

SERVICE REVIEWS

10

Quality Control: Quick Reference Guide

Back to Top

System Service Review (SSR)

WHO

Facility managers or other personnel as designated by the facility manager

WHAT

The intent of an SSR is to review the air traffic services provided in any situation at any time under any circumstances. The SSR is to guide them through that process of what's going on in the entire operation and to try and find the big picture.

WHEN

Routinely, randomly, by inquiry, post event, and by request

WHERE

WHY

Facility Level By reviewing the facility randomly and on a scheduled basis, this ensures assessment of facility performance outside of negative incidents.

SSR: Best Practices • •

At large facilities, SSRs should be performed a minimum of once a week; daily is ideal. Individual Performance notes do not have to be negative. Note any great performance that should be recognized since their methods may be better for everyone. This will trigger a QC OSA.

11

Quality Control: Quick Reference Guide

Back to Top

How to Conduct an SSR 1. On the top menu bar of the CEDAR home screen, select the Tools &

Resources tab.

2. In the center of the screen, under Safety, select the New SSR link. A pop-up window will now open titled System Service Review. NOTE: When you initiate an SSR, or receive a request from somebody, a temporary SSR number is assigned, and when you complete the SSR, a permanent number will be assigned. 3. In the Preliminary Data window, enter Date, Start Time, End Time, and Position. 4. Enter data related to aircraft, A/C Type, flight rules, etc. 5. Answer all questions presented. In order to conduct the SSR, you (and the rest of the review team) will be looking at all the aspects of the operation. Each section of the SSR will ask you a series of questions depending on how you answered the preceding question. All sections must be addressed to finish the SSR. 6. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. You are encouraged to attach Falcon 3 Bookmarks, Replays, Voice Tapes, and any information that would be useful when reviewing the data. 7. In the QC Comments window, provide any comments or a summary. 8. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 9. Scroll to the top of the SSR. On the right is a window displaying a “custody trail”, showing everybody who has been responsible for the SSR. NOTE: Check the “ATSAP filed” checkbox if you are aware an ATSAP report has been filed. Individual ATSAP boxes will be displayed next to each employee in the Employee Performance section so you can identify which employee filed an ATSAP report. 10. To complete the SSR, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Close: When you are finished. c. Cancel: If you don't want to save changes.

12

Quality Control: Quick Reference Guide

Back to Top

Traffic Management Review (TMR)

WHO

TMRs should normally only be conducted at facilities with a TMU or at the ATCSCC. TMRs must be performed by facility-designated staff.

WHAT

The review team looks at all aspects of the operation in an attempt to identify potential risks. The goal behind the TMR is to guide them through the process of what is going on in the entire operation and provide a view of the big picture. This should include items that need correcting as well as identification and recognition of best practices.

WHEN

Routinely, randomly, special events, post event, by request. (TMRs can be conducted at any time and for any reason.)

WHERE WHY

Facility Level TMRs offer a big picture look at a facility’s air traffic management.

TMR: Best Practices •

When reviewing metrics, consider traffic management data from adjacent facilities when such data would be pertinent to the review.

13

Quality Control: Quick Reference Guide

Back to Top

How to Conduct a TMR 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the New TMR link. A pop-up window will now open titled Traffic Management Review. 3. At the top of the window, enter the Facility, Event Date, Start Time and End Time. 4. Under Reason for Review, select your reasoning from the drop-down menu, then explain your choice in the Details text field. Be as descriptive as possible! 5. Continue down the form and answer all questions presented. Answering Yes to any will produce additional questions to provide more details, and then include a text field for adding Details in your own words. Note: All fields with an asterisk must be addressed accordingly. 6. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. You are encouraged to attach Falcon 3 Bookmarks, Replays, Voice Tapes, and any information that would be useful when reviewing the data. 7. Under Findings, explain any notable information you have discovered as a result of the incident. 8. Under Recommendations/Best Practices/Conclusions, detail any suggestions that may allow for better operations in the future. 9. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 10. To complete the TMR, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Close: When you are finished. c. Cancel: If you don't want to save changes.

14

Quality Control: Quick Reference Guide

Back to Top

Covered Event Review (CER)

WHO

Facility managers or other personnel as designated by the facility manager.

WHAT

Covered Event Reviews are conducted as a result of an aircraft accident. The review team looks at all aspects of the operation in an attempt to identify potential risks. The intent of a CER is to supplement and document the existing required review of air traffic services rendered during an aircraft accident. In addition, CERs require facilities to review each accident in-depth, looking beyond the areas of individual performance.

WHEN

Required after accidents or when directed by the director of operations. Must initiate a CER when directed by the director of operations, senior advisor, or the QCG on behalf of the director(s) of operations. (Facility must complete a CER within 3 administrative days following the accident when ATC services were provided (FAAO JO 7210.634, Section 3-4))

WHERE

WHY

Facility Level Every variable of an accident needs to be documented and analyzed to see if it had any contribution to the incident. CERs ensure no stone is left unturned during this process.

CER: Best Practices • • • • •

Filing an ATSAP report does NOT prevent a CER being conducted. When filling out the Individual Performance field, you can identify any pertinent employee performance, good or bad. A CER-OSA will be generated on completion of the CER for each position identified under employee performance. Each assigned user must take some action within one business day. Involved ATC employees must be removed from operation as soon as operationally possible, and must remain relieved until the CER and any assigned training is completed. Click here for a reference to avoid the most common errors in an Accident Package. (The following document contains comment icons which are best viewed in Acrobat Reader.) 15

Quality Control: Quick Reference Guide

Back to Top

How to Conduct a CER 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the New CER link. A pop-up window will now open title, Covered Event Review. NOTE: When you initiate a CER, a temporary CER number is assigned. When you complete the CER, a permanent number will be assigned. 3. In the Preliminary Data window, enter the Date, Start Time, End Time and Position. 4. Enter data related to aircraft, A/C Type, flight rules, etc. 5. In the Individual Performance window, select relevant employees and their position. Justify their inclusion in the Explain field. 6. Continue by answering all questions presented. All sections marked with an asterisk must be addressed to finish the CER. 7. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. You are encouraged to attach Falcon 3 Bookmarks, Replays, Voice Tapes, and any information that would be useful when reviewing the data. 8. In the QC Comments window, provide any comments or a summary. 9. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 10. Scroll to the top of the CER. On the right is a window showing the “custody trail” of everybody who has been responsible for the CER. NOTE: Check the “ATSAP filed” checkbox if you are aware an ATSAP report has been filed. Individual ATSAP boxes will be displayed next to each employee in the Employee Performance section so you can identify which employee filed an ATSAP report. 11. To complete the CER, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Close: When you are finished. c. Cancel: If you don't want to save changes.

16

Quality Control: Quick Reference Guide

Back to Top

Systemic Issue Review (SYSIR)

WHO

Each SDP must identify in CEDAR, a lead and designees for the systemic areas of training, efficiency, airspace/airport, procedures, directives, and technical operations.

WHAT

A method for anyone that conducts an OSA, SSR, or CER to identify areas that have a potential system impact, whether at the SDP, service area, or service level.

WHEN

As systemic issues are identified

WHERE WHY

Facility Level SYSIRs ask why an incident occurred rather that what occurred.

SYSIR: Best Practices • • •

A concurred risk mitigation procedure does not have to be completed to close the SYSIR in CEDAR. The investigative methods in Step 3 are suggestions. Take any steps necessary to investigate. You must remain objective. You cannot assume a particular person is at fault.

17

Quality Control: Quick Reference Guide

Back to Top

How to Conduct a SYSIR 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the New SYSIR link. The Systemic Issue pop-up window opens. 3. In the Systemic Issues section, select the type of systemic issue identified from the following options: a. Airspace/Airport b. Directives c. Efficiency d. Procedures e. Resource Management f. Equipment g. Training 4. Enter Specific Details into the text field. Note: Since there are no additional questions prompted by the system, it is critical to be detailed and thorough in your explanation so the issue can be properly investigated. 5. At the bottom of the report, click Submit and a SYSIR report is generated. Example 1: When conducting a QC OSA, the reviewer identifies the incorrect application of vectors to intercept the final approach course. The reviewer believes this may be more widespread beyond one QC OSA and a possible systemic training issue may exist in the facility. The reviewer enters a potential systemic training issue in the OSA and describes the issue. The SYSIR is then forwarded to the facility lead/designee for review of all Training SYSIRs. The Training SYSIR designee validates the issue to determine if it is actually a systemic issue and develops an appropriate mitigation, if necessary. Example 2: When conducting an SSR, the collaborative team determines via interviews that the application of tower visual separation is not being properly applied by facility personnel due to knowledge gaps and poor understanding of the language in JO 7110.65. As a result, the team believes a potential systemic issue of directives and training exists in the facility. The team enters both a potential systemic directives and training issue in the SSR and, respectively, describes both issues. Each SYSIR is then respectively forwarded to the facility lead/designee for Directives and Training SYSIRs for review. The two SYSIRs will be linked through the original SSR to ensure they are reviewed in tandem. The responsible facility point of contact must review each SYSIR forwarded for their review.

18

Quality Control: Quick Reference Guide

Back to Top

COMPLIANCE VERIFICATION

19

Quality Control: Quick Reference Guide

Back to Top

Internal Compliance Verification (ICV)

WHO

ICVs are expected to be conducted by an ICV team designated by the facility manager or terminal district manager following all applicable national collective bargaining agreements.

WHAT

Internal CVs are planned assessments accomplished through the use of a checklist and random sampling methods such as, but not limited to, direct operational observation, discussions with facility personnel, review of voice or radar data, equipment parameters, certification parameters, and examination of other documentation.

WHEN

All FAA air traffic control facilities and federal contract towers must conduct an ICV annually each fiscal year. The schedule for conducting an ICV will be determined by the facility in order to produce the most comprehensive evaluation results within the annual time period.

WHERE WHY

Facility Level ICVs use standardized checklists to identify facility non-compliance in areas that may not be reviewed through other QC processes.

Internal Compliance Verification: Best Practices •

A facility will determine when an ICV should take place to produce the most comprehensive evaluation results for the fiscal year.

20

Quality Control: Quick Reference Guide

Back to Top

Guidelines for Internal Compliance Verification 1. Internal Compliance Verifications (ICV) assess compliance with specific requirements using a checklist. Facilities must conduct an ICV once per fiscal year and assess compliance with each required checklist item. 2. Use of a standardized checklist requires facilities to assess requirements that may not normally be reviewed through other quality control processes. 3. Facilities should use a variety of methods to assess compliance with checklist items. This includes monitoring of operations (live and via playback tools), reviewing collected data in CEDAR, and interviews of facility personnel. 4. It is imperative that facilities document all non-compliance identified through the ICV process. This ensures an accurate record of facility compliance and correction. 5. ICVs (and ECVs) must be conducted in accordance with Article 51 of the FAA/NATCA collective bargaining agreement which defines union participation. Facilities are encouraged to establish collaborative teams to conduct ICVs. 6. Items assessed as non-compliant require a corrective action (mitigation) plan. Corrective action plans must be documented in the Compliance Verification Tool accessed through the ATO Portal. 7. Facilities may use SSRs to better understand non-compliance identified through the ICV process. SSR findings must be documented in CEDAR; any additional information or findings related to the original non-compliance should also be documented in the CV Tool in the mitigation section for the appropriate issue.

21

Quality Control: Quick Reference Guide

Back to Top

External Compliance Verification (ECV)

WHO

Primarily conducted by service center QCGs

WHAT

External CVs are assessments of facilities that are conducted on an as needed basis as determined by the service unit, director of operations, and/or the QCG (with the concurrence of the director of operations). ECVs may be conducted through various methods that may include developing a custom checklist, review of available data (CEDAR quality control and quality assurance data, Risk Analysis, Event Analysis, information from ATSAP, etc.), direct observation, interviews with personnel, and other means as appropriate.

WHEN

Determinations to conduct ECVs will be based on data analysis that identifies potential risk within specific facilities.

WHERE WHY

Facility Level ECVs assess a facility in response to data-driven indicators of risk.

External Compliance Verification: Best Practices •

When defining scope, the service center Quality Control Group must consider trend analysis. The scope may be very broad or focus narrowly on a few items.

22

Quality Control: Quick Reference Guide

Back to Top

Guidelines for External Compliance Verification 1. External Compliance Verifications (ECVs) assess compliance with requirements based on data collected and assessed by service area and/or headquarters quality control and/or quality assurance staff. ECVs are conducted on an “asneeded” basis by teams from outside of a facility. 2. ECVs (and ICVs) must be conducted in accordance with Article 51 of the FAA/NATCA collective bargaining agreement which defines union participation.

23

Quality Control: Quick Reference Guide

Back to Top

QC PROGRAMS

24

Quality Control: Quick Reference Guide

Back to Top

OSA Checks

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

An OSA Check is intended to look for trends identified in the OSA process and develop mitigations for identified issues.

WHEN

A minimum of once per fiscal year at intervals spaced no closer than 180 days apart.

WHERE

WHY

Facility Level All Quality Control Checks combine data and multiple points of view to identify risks and inefficiencies and assist in the development of corrective action. Limiting checks to every 180 days ensures a wide range of data for analysis.

OSA Checks: Best Practices • •

•

Facilities are encouraged to establish collaborative teams to conduct Quality Control Checks. Resulting outcomes of QC Checks can include: • Development of a Corrective Action Plan (CAP) by the check team • Referral of the issue to an SSR team for additional analysis • Collection of additional data through Emphasis Items or monitoring of future QC OSAs QC Check teams should prioritize issues, and focus their efforts on higher consequence, non-compliance issues.

25

Quality Control: Quick Reference Guide

Back to Top

How to Conduct OSA Checks 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the OSA Check link. 3. Select OSA Type from the available options. The OSA Subtask Summary window will display, and the OSA Check pop-up window opens with the current date. 4. In the New Issues window you can select any newly identified issues category from the drop down menu. If new issues are identified, complete the details text entry box. Mitigations to correct the issue are captured in the mitigations details text entry box. 5. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 6. To complete the OSA Check, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

26

Quality Control: Quick Reference Guide

Back to Top

On The Job Training Checks (OJT Checks)

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

OJT Checks look for trends and develop mitigations for unsatisfactory/needs improvement training items identified in skill checks.

WHEN

A minimum of once per fiscal year at intervals spaced no closer than 180 days apart.

WHERE

WHY

Facility Level All Quality Control Checks combine data and multiple points of view to identify risks and inefficiencies and assist in the development of corrective action. Limiting checks to every 180 days ensures a wide range of data for analysis.

OJT Checks: Best Practices • •

•

Facilities are encouraged to establish collaborative teams to conduct Quality Control Checks. Resulting outcomes of QC Checks can include: • Development of a CAP by the check team • Referral of the issue to an SSR team for additional analysis • Collection of additional data through Emphasis Items or monitoring of future QC OSAs. QC Check teams should prioritize issues, and focus their efforts on higher consequence, non-compliance issues.

27

Quality Control: Quick Reference Guide

Back to Top

How to Conduct OJT Checks 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the OJT Check link. 3. Select OJT Type from the available options. 4. In the New Issues section, select a newly identified issue from the drop-down menu. 5. In the Details text box, explain the issue in as much detail as possible. 6. Under Training Program Revision, detail a plan to correct the problem you described. 7. Below the Training Program Revision text box, you can Add Another Issue if there are more issues to address. This link will simply add another Newly Identified Issue drop-down menu, repeating Steps 4 – 6. 8. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 9. To complete the OJT Check, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

28

Quality Control: Quick Reference Guide

Back to Top

Efficiency Checks (ECs)

WHO

Only facilities with TMUs and the ATCSCC should normally conduct efficiency checks. Facilities without TMUs may conduct ECs with district support and guidance. Facility-designated quality control personnel must perform efficiency checks.

WHAT

An EC is intended to identify trends for issues identified in TMRs and develop mitigations for these identified issues.

WHEN

A minimum of once per fiscal year at intervals spaced no closer than 180 days apart.

WHERE

WHY

Facility Level All Quality Control Checks combine data and multiple points of view to identify risks and inefficiencies and assist in the development of corrective action. Limiting checks to every 180 days ensures a wide range of data for analysis.

Efficiency Checks: Best Practices • •

•

Facilities are encouraged to establish collaborative teams to conduct Quality Control Checks. Resulting outcomes of QC Checks can include: • Development of a Corrective Action Plan (CAP) by the check team • Referral of the issue to an SSR team for additional analysis • Collection of additional data through Emphasis Items or monitoring of future QC OSAs. QC Check teams should prioritize issues, and focus their efforts on higher consequence, non-compliance issues.

29

Quality Control: Quick Reference Guide

Back to Top

How to Conduct Efficiency Checks 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the Efficiency Check link. 3. In the New Issues section, select a newly identified issue from the drop-down menu. 4. In the Details text box, explain the issue in as much detail as possible. 5. Under Mitigation, detail a plan to correct the problem you described. 6. Below the Mitigation text box, you can Add Another Issue if there are more issues to address. This link will simply add another Newly Identified Issue drop-down menu, repeating Steps 3 – 5. 7. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 8. To complete the Efficiency Check, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

30

Quality Control: Quick Reference Guide

Back to Top

System Performance Checks

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

SPCs are intended to review SYSIRs and to identify groupings of systemic issues that continue to recur, document them and develop mitigations.

WHEN

A minimum of once per fiscal year at intervals spaced no closer than 180 days apart.

WHERE

WHY

Facility Level All Quality Control Checks combine data and multiple points of view to identify risks and inefficiencies and assist in the development of corrective action. Limiting checks to every 180 days ensures a wide range of data for analysis.

System Performance Checks: Best Practices • •

•

Facilities are encouraged to establish collaborative teams to conduct Quality Control Checks. Resulting outcomes of QC Checks can include: • Development of a Corrective Action Plan (CAP) by the check team • Referral of the issue to an SSR team for additional analysis • Collection of additional data through Emphasis Items or monitoring of future QC OSAs. QC Check teams should prioritize issues, and focus their efforts on higher consequence, non-compliance issues.

31

Quality Control: Quick Reference Guide

Back to Top

How to Conduct System Performance Checks 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the

System Performance Check link. 3. In the New Issues section, select a newly identified issue from the drop-down menu. 4. In the Details text box, explain the issue in as much detail as possible. 5. Under Mitigation, detail a plan to correct the problem you described. 6. Below the Mitigation text box, you can Add Another Issue if there are more issues to address. This link will simply add another Newly Identified Issue drop-down menu, repeating Steps 3 – 5. 7. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 8. To complete the System Performance Check, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

32

Quality Control: Quick Reference Guide

Back to Top

OSA Validations

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

A validator will conduct the OSA, document their findings, and compare them with findings from original conductor of OSA. If validation identifies that improvement is necessary, facilities should develop and implement a mitigation plan in a timely fashion. The purpose of this initiative is to ensure the manager has captured the performance of the employee accurately.

WHEN

Anytime

WHERE WHY

Facility Level It is imperative facilities accurately capture data. Validations ensure effective identification of non-compliance and associated CAPs.

OSA Validations: Best Practices • • • •

Validations should be done by QC staff since the original may not have been done by a QC staff member. You are not looking for trends. The goal is to check the accuracy of the original OSA reviewer to ensure an impartial and accurate review has been conducted. Use all necessary data to validate the OSA, including radar and voice data where available. Validations cannot negatively impact an employee’s overall performance evaluation.

33

Quality Control: Quick Reference Guide

Back to Top

How to Conduct OSA Validations 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the Checks and Validations Report link. 3. Under, What facility would you like to view?, select the facility that conducted the OSA you wish to validate. 4. Under, What would you like to see?, select OSA Validations. 5. When asked, What dates would you like to see?, select from the available options. 6. Next, How many items would you like to see?, select All or a Random Sample. 7. Click Submit. Keep in mind that selecting to view all reports in steps 5 and 6 can generate a very long list, so try to refine your search whenever possible. 8. After submitting, the QC Checks/Validations section appears with a table of all matching reports. Navigate the table and select the report you wish to validate by clicking on it. You can also repeat Steps 5 and 6. The Submit button has now been replaced by a Refresh button to refine your results. 9. Click the Validate button in the upper-right corner, and the report will add an additional column of rating checkmarks. Review the OSA using all available supporting data to determine if the original assessment is supported. 10. When finished, under the Validation section near the bottom, note whether the reviewer who filled out the original OSA was Exemplary, Met Requirements, or Needs Improvement when filling out OSAs. 11. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. You are encouraged to attach Falcon 3 Bookmarks, Replays, Voice Tapes, and any information that would be useful when reviewing the data. 12. Next, in Forward, use this section to do any of the following: a. Send as Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Send it as an informational item to an unlimited number of people at the facility. 13. To complete the OSA Validation, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

34

Quality Control: Quick Reference Guide

Back to Top

Certification Skill Check Validations

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

The purpose of this initiative is to ensure the FLM/STMC/NTMO certifier has accurately captured the performance of the employee during certification and look for accuracy and completeness of the form. If validation identifies that improvement is necessary, facilities should develop and implement a mitigation plan in a timely fashion.

WHEN

Anytime

WHERE

WHY

Facility Level It is imperative facilities accurately capture data. Validations ensure effective identification of non-compliance and associated Corrective Action Plans (CAPs).

Certification Skill Check Validations: Best Practices • •

Whenever possible, scan any paper documents and attach as a PDF. Employees must not be de-certified as a result of a Certification Skill Check Validation.

35

Quality Control: Quick Reference Guide

Back to Top

How to Conduct Certification Skill Check Validations 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the

Checks and Validations link. 3. Under, What would you like to see?, select Certification Skill Check Validations. 4. Select the Certifier to validate from the drop-down menu. 5. Select the Position, Date, Start Time and Stop Time. 6. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. If Supporting Data is included, enter details the description window and use the Browse or Upload button to attach identified supporting data. 7. In the Validation section, you will be asked, “How was the accuracy and completeness of the Certification Skill Check?” Select one of the three available options and include details. Be as descriptive as possible! 8. Next, in Forward, use this section to do any of the following: a. Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. b. Delegate it to 1 person in their facility that has permission to work on it. c. Cancel to cancel the forwarding. 9. To complete the CSC Validation, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

36

Quality Control: Quick Reference Guide

Back to Top

On The Job Training Documentation Validations

WHO

Quality Control Managers/Specialists, Frontline Managers, Operations Manager, Facility Managers

WHAT

A validation process to assess the accuracy and completeness of the documentation provided by OJT instructors each fiscal year. This validation process must assess only those OJT instructors that have actually provided on-the-job training during the fiscal year under review. An OJTD Validation reviews for accuracy and completeness. If validation identifies that improvement is necessary, facilities should develop and implement a mitigation plan in a timely fashion.

WHEN

At any time, facilities must review a representative sampling of the OJT documentation.

WHERE WHY

Facility Level The purpose is to ensure OJT is to accurately capture the performance of the employee during On-the-Job Training.

OJT Documentation Validations: Best Practices • •

When possible, scan any paper documents and attach as a PDF. There are no time restrictions on OJT Validations. Smaller facilities may wish to validate all of them.

37

Quality Control: Quick Reference Guide

Back to Top

How to Conduct On the Job Training Documentation Validations 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the OJTD Validation link. 3. In the OJT Session Information, Select the Position, Data, Start Time, and Stop Time. 4. Now, in the Supporting Data window, there is a drop-down menu for selecting data options to attach. If Supporting Data is included, enter details the description window and use the Browse or Upload button to attach identified supporting data. 5. In the Validation section, you will be asked, “How was the accuracy and completeness of the OJT Form?” Enter one of the three available options and include details. Be as descriptive as possible! 6. Next, in Forward, use this section to do any of the following: d. Informational or delegate/select somebody to receive it and enter their comments. They will be notified on their home page. e. Delegate it to 1 person in their facility that has permission to work on it. f. Cancel to cancel the forwarding. 7. To complete the OJTD Validation, select one of the following options at the bottom: d. Save Draft: When you want to gather more information before finishing. e. Submit: When you are finished. f. Cancel: If you don't want to save changes.

38

Quality Control: Quick Reference Guide

Back to Top

REPORTING

39

Quality Control: Quick Reference Guide

Back to Top

MORs (Manual Occurrence Reporting)

WHO

All employees must report occurrences according to this directive. Employees may satisfy reporting requirement by filing a VSRP report, if appropriate.

WHAT

An occurrence involving air traffic services for which the collection of associated safety-related data and conditions is mandatory.

WHEN

When any of the MOR criteria apply (see Appendix A in Order JO 7210.632)

WHERE WHY

Facility Level If any pilot commits, or is suspected of committing, a deviation from controller instructions, it must be documented for review.

MORs: Best Practices • •

By order, an MOR has to be submitted by the end of your shift. CEDAR includes a Step-By-Step function to guide you through the process if necessary.

40

Quality Control: Quick Reference Guide

Back to Top

How to Report MORs 1. On the top menu bar of the CEDAR home screen, select the Tools & Resources tab. 2. In the center of the screen, under Safety, select the New MOR link. A pop-up window will now open titled Occurrence Report. 3. Under Preliminary Data, enter the Event Date and Time 4. Then, select the MOR Type from the drop-down list. 5. The following fields will update automatically based on the type of MOR selected. Requested information may include: a. Reported By (Position) b. Nearest Airport c. Significant Event? d. Training In Progress? e. Aircraft(s) Involved f. Event Location You may also be prompted to enter a Summary of the incident. 6. To complete the MOR, select one of the following options at the bottom: a. Save Draft: When you want to gather more information before finishing. b. Submit: When you are finished. c. Cancel: If you don't want to save changes.

41

Quality Control: Quick Reference Guide

Back to Top

Pilot Deviation Notifications

WHO

Employee providing air traffic services

WHAT

When the employee providing air traffic services determines that pilot actions affected the safety of operations, the employee must report through the MOR process and notify the flight crew as soon as operationally practical.

WHEN

As soon as operationally practical

WHERE WHY

Facility Level If any pilot commits, or is suspected of committing, a deviation from controller instructions, it must be documented for review.

Pilot Deviation Notifications: Best Practices • • • • • • •

A complete description of these guidelines can be found in JO 8020.16B, paragraph 112. By order, an MOR has to be submitted by the end of your shift. Within 10 days of the occurrence prepare and submit FAA Form 8020-17 electronically via AT Quality Assurance (ATQA). Notify the facility(s) to collect and retain pertinent air traffic data associated with the occurrence. Via CEDAR or other means, retain all pertinent data used in the decision to forward the occurrence. Determine all pertinent conversations or contacts. Involved facilities record voice data from 15 minutes before initial conversation or contact until 15 minutes after last conversation or contact. Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data.

42

Quality Control: Quick Reference Guide

Back to Top

Guidelines for Pilot Deviation Notifications 1. Workload permitting, notify the pilot. If workload does not permit, alternative actions should be taken to notify the pilot. 2. Notify the Watch Supervisor, or Controller-In-Charge as appropriate, of the circumstances involved so the occurrence can be reported. 3. Document the incident. Gather pertinent information such as the pilot’s name, certificate number and contact information, and statements from involved personnel. 4. When advised by QAG, collect and retain pertinent data associated with the occurrence. The QAG may require the facility to conduct an SSR in order to determine the necessary data. a. For occurrences that require pertinent information from a flight service station contact AFSIAG or FSPO to obtain data. The QCG may assist. b. For occurrences that require pertinent information from a flight planning contractor contact both DTC DUAT and CSC DUATS. The QCG may assist. 5. The facility where the occurrence happened must produce an enforcement replay or plot when needed for enforcement court proceedings. 6. Follow the MOR process for incidents not observed by but reported to air traffic. 7. Produce a certified index listing the data held at your facility. 8. Produce a memo from the facility manager (or acting manager) addressed to the facility's file listing the data retained by the facility. 9. Produce a certified partial or full transcript of requested by the ATO Litigation Support Group, QCG, FSPO or regional counsel. 10. Retain all pertinent data. Originals remain at the facility that produced them.

43

Quality Control: Quick Reference Guide

Back to Top

Near Midair Collisions

WHO

Employee providing air traffic services

WHAT

An incident associated with the operation of an aircraft in which the possibility of collision occurs as a result of proximity of less than 500 feet to another aircraft, or a report is received from a pilot or flight crewmember stating that a collision hazard existed between two or more aircraft.

WHEN

As soon as operationally practical

WHERE WHY

Facility Level All variables contributing to a potential collision must be recorded for analysis

Near Midair Collisions: Best Practices • • • • • • • • •

A complete description of these guidelines can be found in JO 8020.16B, paragraph 112. By order, an MOR has to be submitted by the end of your shift. Only a pilot or flight crew member can initiate the filing of a NMAC report. If an NMAC is reported after tapes are no longer available, investigate based on available data. Within 10 days of the occurrence prepare and submit FAA Form 8020-21 electronically via AT Quality Assurance (ATQA). Notify the facility(s) to collect and retain pertinent air traffic data associated with the occurrence. Via CEDAR or other means, retain all pertinent data used in the decision to forward the occurrence. Determine all pertinent conversations or contacts. Involved facilities record voice data from 15 minutes before initial conversation or contact until 15 minutes after last conversation or contact. Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data.

44

Quality Control: Quick Reference Guide

Back to Top

Guidelines for Near Midair Collisions 1. Workload permitting, notify the pilot. If workload does not permit, alternative actions should be taken to notify the pilot. 2. Notify the Watch Supervisor, or Controller-In-Charge as appropriate, of the circumstances involved so the occurrence can be reported. 3. Document the incident. Gather pertinent information such as the pilot’s name, certificate number and contact information, and statements from involved personnel. 4. When advised by QAG, collect and retain pertinent data associated with the occurrence. The QAG may require the facility to conduct an SSR in order to determine the necessary data. a. For occurrences that require pertinent information from a flight service station contact AFSIAG or FSPO to obtain data. The QCG may assist. b. For occurrences that require pertinent information from a flight planning contractor contact both DTC DUAT and CSC DUATS. The QCG may assist. 5. The facility where the occurrence happened must produce an enforcement replay or plot when needed for enforcement court proceedings. 6. Follow the MOR process for incidents not observed by but reported to air traffic. 7. Produce a certified index listing the data held at your facility. 8. Produce a memo from the facility manager (or acting manager) addressed to the facility's file listing the data retained by the facility. 9. Produce a certified partial or full transcript of requested by the ATO Litigation Support Group, QCG, FSPO or regional counsel. 10. Retain all pertinent data. Originals remain at the facility that produced them.

45

Quality Control: Quick Reference Guide

Back to Top

HATR/OHR (Hazardous Air Traffic Reports and Operational Hazard Reports)

WHO

Service Area QA Specialists

WHAT

The HATR program is the USAF system for collecting information on NMACs and other hazardous air traffic situations. This program complements but does not replace similar reporting programs sponsored by the National Aeronautics and Space Administration (NASA) and the FAA.

WHEN

As necessary

WHERE WHY

Facility Level All variables contributing to a potential collision must be recorded for analysis

HATR/OHR: Best Practices • • • • • • • • •

A complete description of these guidelines can be found in JO 8020.16B, paragraph 112. By order, an MOR has to be submitted by the end of your shift. Advance notification of a HATR/OHR will come from the USAF or US Army. If more than one facility is notified, one will need to be selected to coordinate the investigation. Within 10 days of the occurrence prepare and submit FAA Form 8020-21 electronically via AT Quality Assurance (ATQA). Notify the facility(s) to collect and retain pertinent air traffic data associated with the occurrence. Via CEDAR or other means, retain all pertinent data used in the decision to forward the occurrence. Determine all pertinent conversations or contacts. Involved facilities record voice data from 15 minutes before initial conversation or contact until 15 minutes after last conversation or contact. Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data.

46

Quality Control: Quick Reference Guide

Back to Top

Guidelines for HATR/OHR 1. Workload permitting, notify the pilot. If workload does not permit, alternative actions should be taken to notify the pilot. 2. Notify the Watch Supervisor, or Controller-In-Charge as appropriate, of the circumstances involved so the occurrence can be reported. 3. Document the incident. Gather pertinent information such as the pilot’s name, certificate number and contact information, and statements from involved personnel. 4. When advised by QAG, collect and retain pertinent data associated with the occurrence. The QAG may require the facility to conduct an SSR in order to determine the necessary data. a. For occurrences that require pertinent information from a flight service station contact AFSIAG or FSPO to obtain data. The QCG may assist. b. For occurrences that require pertinent information from a flight planning contractor contact both DTC DUAT and CSC DUATS. The QCG may assist. 5. The facility where the occurrence happened must produce an enforcement replay or plot when needed for enforcement court proceedings. 6. Follow the MOR process for incidents not observed by but reported to air traffic. 7. Produce a certified index listing the data held at your facility. 8. Produce a memo from the facility manager (or acting manager) addressed to the facility's file listing the data retained by the facility. 9. Produce a certified partial or full transcript of requested by the ATO Litigation Support Group, QCG, FSPO or regional counsel. 10. Retain all pertinent data. Originals remain at the facility that produced them.

47

Quality Control: Quick Reference Guide

Back to Top

Vehicle/Pedestrian Deviations

WHO

Service Area QA Specialists

WHAT

When an unauthorized vehicle or pedestrian is observed by air traffic control or other parties on any portion of the airport movement area.

WHEN

As necessary

WHERE

Facility Level

WHY

All variables contributing to a deviation of this kind must be recorded for analysis

Vehicle/Pedestrian Deviations: Best Practices • • • • • • •

A complete description of these guidelines can be found in JO 8020.16B, paragraph 112. By order, an MOR has to be submitted by the end of your shift. Within 10 days of the occurrence prepare and submit FAA Form 8020-24 electronically via AT Quality Assurance (ATQA). Notify the facility(s) to collect and retain pertinent air traffic data associated with the occurrence. Via CEDAR or other means, retain all pertinent data used in the decision to forward the occurrence. Determine all pertinent conversations or contacts. Involved facilities record voice data from 15 minutes before initial conversation or contact until 15 minutes after last conversation or contact. Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data.

48

Quality Control: Quick Reference Guide

Back to Top

Guidelines for Vehicle/Pedestrian Deviations 1. Workload permitting, notify the pilot. If workload does not permit, alternative actions should be taken to notify the pilot. 2. Notify the Watch Supervisor, or Controller-In-Charge as appropriate, of the circumstances involved so the occurrence can be reported. 3. Document the incident. Gather pertinent information such as the pilot’s name, certificate number and contact information, and statements from involved personnel. 4. When advised by QAG, collect and retain pertinent data associated with the occurrence. The QAG may require the facility to conduct an SSR in order to determine the necessary data. a. For occurrences that require pertinent information from a flight service station contact AFSIAG or FSPO to obtain data. The QCG may assist. b. For occurrences that require pertinent information from a flight planning contractor contact both DTC DUAT and CSC DUATS. The QCG may assist. 5. The facility where the occurrence happened must produce an enforcement replay or plot when needed for enforcement court proceedings. 6. Follow the MOR process for incidents not observed by but reported to air traffic. 7. Produce a certified index listing the data held at your facility. 8. Produce a memo from the facility manager (or acting manager) addressed to the facility's file listing the data retained by the facility. 9. Produce a certified partial or full transcript of requested by the ATO Litigation Support Group, QCG, FSPO or regional counsel. 10. Retain all pertinent data. Originals remain at the facility that produced them.

49

Quality Control: Quick Reference Guide

Back to Top

Air Traffic Incident Reports

WHO

Service Area QA Specialists

WHAT

An occurrence other than an accident associated with the operation of an aircraft, which affects or could affect the safety of operations.

WHEN

As necessary

WHERE WHY

Facility Level All variables contributing to all air traffic incidents must be recorded for analysis

Air Traffic Incident Reports: Best Practices • • • • • • • •

Copies submitted to other departments, directors, etc. have specified deadlines, sometimes within only a few hours of the incident, so act quickly when observing or being notified of these incidents A complete description of these guidelines can be found in JO 8020.16B, paragraph 112. By order, an MOR has to be submitted by the end of your shift. Within 10 days of the occurrence prepare and submit FAA Form 8020-9 electronically via AT Quality Assurance (ATQA). Notify the facility(s) to collect and retain pertinent air traffic data associated with the occurrence. Via CEDAR or other means, retain all pertinent data used in the decision to forward the occurrence. Determine all pertinent conversations or contacts. Involved facilities record voice data from 15 minutes before initial conversation or contact until 15 minutes after last conversation or contact. Radar and Automation data must be retained in sufficient quantity in order to be able to reasonably recreate the event on the automation platform that recorded the data.

50

Quality Control: Quick Reference Guide

Back to Top

Guidelines for an Air Traffic Incident Report 1. Workload permitting, notify the pilot. If workload does not permit, alternative actions should be taken to notify the pilot. 2. Notify the Watch Supervisor, or Controller-In-Charge as appropriate, of the circumstances involved so the occurrence can be reported. 3. Document the incident. Gather pertinent information such as the pilot’s name, certificate number and contact information, and statements from involved personnel. 4. When advised by QAG, collect and retain pertinent data associated with the occurrence. The QAG may require the facility to conduct an SSR in order to determine the necessary data. a. For occurrences that require pertinent information from a flight service station contact AFSIAG or FSPO to obtain data. The QCG may assist. b. For occurrences that require pertinent information from a flight planning contractor contact both DTC DUAT and CSC DUATS. The QCG may assist. 5. The facility where the occurrence happened must produce an enforcement replay or plot when needed for enforcement court proceedings. 6. Follow the MOR process for incidents not observed by but reported to air traffic. 7. Produce a certified index listing the data held at your facility. 8. Produce a memo from the facility manager (or acting manager) addressed to the facility's file listing the data retained by the facility. 9. Produce a certified partial or full transcript of requested by the ATO Litigation Support Group, QCG, FSPO or regional counsel. 10. Retain all pertinent data. Originals remain at the facility that produced them.

51