 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Aircraft X with a full data block was given descent clearance by ZID controller. Aircraft Y with a limited data block was below aircraft X. Controller claims he did not see aircraft Y because the limited tag was covered by the full data block.
| Attributes | |
| ACN | 404844 |
| Time | |
| Date | 199806 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : hyk |
| State Reference | KY |
| Altitude | msl bound lower : 22200 msl bound upper : 23000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid artcc : zbw |
| Operator | common carrier : air taxi |
| Make Model Name | Falcon 20FJF/20C/20D/20E/20F |
| Operating Under FAR Part | Part 135 |
| Navigation In Use | Other Other |
| Flight Phase | descent other |
| Route In Use | arrival other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air taxi |
| Make Model Name | Challenger CL604 |
| Operating Under FAR Part | Part 135 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar other other : other pilot : student |
| Experience | controller non radar : 9 controller radar : 7 flight time total : 20 |
| ASRS Report | 404844 |
| Person 2 | |
| Affiliation | company : air taxi |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | controller : issued new clearance none taken : unable other |
| Consequence | Other |
| Miss Distance | vertical : 800 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft #1 was an arrival into sdf and descended per LOA. Aircraft #2 was not pointed out and entered my airspace as a limited data block underneath a full data block. The limited was therefore not seen until conflict alert activated. Appropriate action was taken but wasn't enough to keep separation. 2 1/2 mi and 800 ft (FL222 and FL230). An automatic flash through procedure or a patch that automatically put a data block on the scope when a limited data block, within the prescribed stratum, crossed the lateral boundary, may have eliminated this error.
Original NASA ASRS Text
Title: ACFT X WITH A FULL DATA BLOCK WAS GIVEN DSCNT CLRNC BY ZID CTLR. ACFT Y WITH A LIMITED DATA BLOCK WAS BELOW ACFT X. CTLR CLAIMS HE DID NOT SEE ACFT Y BECAUSE THE LIMITED TAG WAS COVERED BY THE FULL DATA BLOCK.
Narrative: ACFT #1 WAS AN ARR INTO SDF AND DSNDED PER LOA. ACFT #2 WAS NOT POINTED OUT AND ENTERED MY AIRSPACE AS A LIMITED DATA BLOCK UNDERNEATH A FULL DATA BLOCK. THE LIMITED WAS THEREFORE NOT SEEN UNTIL CONFLICT ALERT ACTIVATED. APPROPRIATE ACTION WAS TAKEN BUT WASN'T ENOUGH TO KEEP SEPARATION. 2 1/2 MI AND 800 FT (FL222 AND FL230). AN AUTOMATIC FLASH THROUGH PROC OR A PATCH THAT AUTOMATICALLY PUT A DATA BLOCK ON THE SCOPE WHEN A LIMITED DATA BLOCK, WITHIN THE PRESCRIBED STRATUM, CROSSED THE LATERAL BOUNDARY, MAY HAVE ELIMINATED THIS ERROR.
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.