 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Loss of separation occurred between aircraft X and aircraft Y because radar controller was expecting a full data block on aircraft X.
| Attributes | |
| ACN | 445856 |
| Time | |
| Date | 199908 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | navaid : ape.vortac |
| State Reference | OH |
| Altitude | msl bound lower : 25000 msl bound upper : 28000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zid.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Citation V |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller radar : 13 |
| ASRS Report | 445856 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : handoff position |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert atc equipment other atc equipment : error detection printer other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 24000 vertical : 0 |
| Supplementary | |
| Problem Areas | ATC Human Performance ATC Facility |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft X yyz ape cince 3 cvg at FL280. Aircraft Y cle ape south FL250 up to FL290. Toronto center entered an amended code on aircraft X, but mistakenly entered the number as a speed rather than code. This action caused the NAS fdp system to project the aircraft's route of flight 5 times faster than normal which led to a loss of flight data and subsequent automated fdp functions. ZOB tried to make a manual handoff/flight plan coordination to my radar associated controller during a busy period. I did not perceive the limited data block of aircraft X overtaking aircraft Y. When the flight plan was finally reentered into the computer, I noticed the confliction at the same time aedp and conflict alert activated.
Original NASA ASRS Text
Title: LOSS OF SEPARATION OCCURRED BTWN ACFT X AND ACFT Y BECAUSE RADAR CTLR WAS EXPECTING A FULL DATA BLOCK ON ACFT X.
Narrative: ACFT X YYZ APE CINCE 3 CVG AT FL280. ACFT Y CLE APE S FL250 UP TO FL290. TORONTO CTR ENTERED AN AMENDED CODE ON ACFT X, BUT MISTAKENLY ENTERED THE NUMBER AS A SPD RATHER THAN CODE. THIS ACTION CAUSED THE NAS FDP SYS TO PROJECT THE ACFT'S RTE OF FLT 5 TIMES FASTER THAN NORMAL WHICH LED TO A LOSS OF FLT DATA AND SUBSEQUENT AUTOMATED FDP FUNCTIONS. ZOB TRIED TO MAKE A MANUAL HDOF/FLT PLAN COORD TO MY RADAR ASSOCIATED CTLR DURING A BUSY PERIOD. I DID NOT PERCEIVE THE LIMITED DATA BLOCK OF ACFT X OVERTAKING ACFT Y. WHEN THE FLT PLAN WAS FINALLY REENTERED INTO THE COMPUTER, I NOTICED THE CONFLICTION AT THE SAME TIME AEDP AND CONFLICT ALERT ACTIVATED.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.