![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 128630 | 
| Time | |
| Date | 198911 | 
| Day | Wed | 
| Local Time Of Day | 1201 To 1800 | 
| Place | |
| Locale Reference | atc facility : fnt | 
| State Reference | MI | 
| Altitude | msl bound lower : 14000 msl bound upper : 14000  | 
| Environment | |
| Flight Conditions | IMC | 
| Light | Daylight | 
| Aircraft 1 | |
| Controlling Facilities | artcc : zob | 
| Operator | general aviation : corporate | 
| Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng | 
| Flight Phase | cruise other | 
| Flight Plan | IFR | 
| Person 1 | |
| Affiliation | government : faa | 
| Function | controller : radar | 
| Qualification | controller : radar | 
| ASRS Report | 128630 | 
| Person 2 | |
| Affiliation | Other | 
| Function | flight crew : captain oversight : pic  | 
| Qualification | pilot : instrument | 
| Events | |
| Anomaly | non adherence : published procedure other anomaly other other anomaly other  | 
| Independent Detector | other controllera | 
| Resolutory Action | none taken : anomaly accepted | 
| Consequence | Other | 
| Supplementary | |
| Primary Problem | ATC Human Performance | 
| Air Traffic Incident | Intra Facility Coordination Failure Inter Facility Coordination Failure Operational Deviation  | 
Narrative:
Aircraft #1 traveling west 14000', handed off from toronto center to ZOB, flint sector. Aircraft #1 made initial radio contact and proceeded on course. Sometime later toronto center attempted radar handoff on aircraft #2 at 8000' to fnt sector. Aircraft #2 was below ZOB's radar coverage. When controller attempted to start a track (data block) for aircraft #2, the computer identify for aircraft #1 was mistakenly used, causing the data block for aircraft #1 to be disassociated from the actual radar target. Controller failed to notice that incorrect data block had been placed in the approximately position of aircraft #2, and with no data block connected to aircraft #2's target, allowed aircraft #1 to proceed through the ZOB lansing sector and into ZOB's area west/O handoffs.
Original NASA ASRS Text
Title: CTLR INADVERTENTLY DROPPED DATA BLOCK, CAUSING ACFT TO PENETRATE ADJACENT SECTOR AND CENTER AIRSPACE.
Narrative: ACFT #1 TRAVELING W 14000', HANDED OFF FROM TORONTO CENTER TO ZOB, FLINT SECTOR. ACFT #1 MADE INITIAL RADIO CONTACT AND PROCEEDED ON COURSE. SOMETIME LATER TORONTO CENTER ATTEMPTED RADAR HDOF ON ACFT #2 AT 8000' TO FNT SECTOR. ACFT #2 WAS BELOW ZOB'S RADAR COVERAGE. WHEN CTLR ATTEMPTED TO START A TRACK (DATA BLOCK) FOR ACFT #2, THE COMPUTER IDENT FOR ACFT #1 WAS MISTAKENLY USED, CAUSING THE DATA BLOCK FOR ACFT #1 TO BE DISASSOCIATED FROM THE ACTUAL RADAR TARGET. CTLR FAILED TO NOTICE THAT INCORRECT DATA BLOCK HAD BEEN PLACED IN THE APPROX POS OF ACFT #2, AND WITH NO DATA BLOCK CONNECTED TO ACFT #2'S TARGET, ALLOWED ACFT #1 TO PROCEED THROUGH THE ZOB LANSING SECTOR AND INTO ZOB'S AREA W/O HDOFS.
Data retrieved from NASA's ASRS site as of August 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.