 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Controller copied wrong altitude on aircraft #2 (4 F-16). Reporter issued clearance to aircraft #1 to descend through aircraft #2's altitude. Aircraft #1 had a TCASII RA, stopped descent above aircraft #2. No separation lost.
| Attributes | |
| ACN | 424909 |
| Time | |
| Date | 199901 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : bvl |
| State Reference | UT |
| Altitude | msl bound lower : 23000 msl bound upper : 24500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B727 Undifferentiated or Other Model |
| Flight Phase | descent other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | other |
| Make Model Name | Fighting Falcon F16 |
| Navigation In Use | Other Other |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Experience | controller radar : 2 |
| ASRS Report | 424909 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | non adherence : published procedure other anomaly other |
| Independent Detector | aircraft equipment other aircraft equipment : unspecified |
| Consequence | Other |
| Miss Distance | horizontal : 30000 vertical : 1500 |
| Supplementary | |
| Air Traffic Incident | other |
Narrative:
Approximately XA52Z, clover control called with a pointout. The communication was somewhat garbled, so I confirmed that the aircraft being pointed out was aircraft #2 (4 F16). In my mind the pointout was to be at FL200. The reality was the pointout was at FL230. After approving the pointout, I entered a temporary altitude of FL200 in the data block. Aircraft #1 checked on at FL330. I gave aircraft #1 a descent clearance to FL270 for traffic. After clearing the traffic at FL260, I issued descent to FL210 to clear the pointed out traffic. Aircraft #1 stated that he was responding to TCASII. Just a few seconds later, aircraft #1 reported at FL250. I called clover control to confirm the altitude that the pointed out traffic was at FL200. Clover responded FL230. By that time the aircraft were laterally separated, so I issued a descent to 17000 ft then over to approach with aircraft #1. I didn't inform the supervisor when it happened because I did not remember that it was mandatory to report it. I did not lose separation.
Original NASA ASRS Text
Title: CTLR COPIED WRONG ALT ON ACFT #2 (4 F-16). RPTR ISSUED CLRNC TO ACFT #1 TO DSND THROUGH ACFT #2'S ALT. ACFT #1 HAD A TCASII RA, STOPPED DSCNT ABOVE ACFT #2. NO SEPARATION LOST.
Narrative: APPROX XA52Z, CLOVER CTL CALLED WITH A POINTOUT. THE COM WAS SOMEWHAT GARBLED, SO I CONFIRMED THAT THE ACFT BEING POINTED OUT WAS ACFT #2 (4 F16). IN MY MIND THE POINTOUT WAS TO BE AT FL200. THE REALITY WAS THE POINTOUT WAS AT FL230. AFTER APPROVING THE POINTOUT, I ENTERED A TEMPORARY ALT OF FL200 IN THE DATA BLOCK. ACFT #1 CHKED ON AT FL330. I GAVE ACFT #1 A DSCNT CLRNC TO FL270 FOR TFC. AFTER CLRING THE TFC AT FL260, I ISSUED DSCNT TO FL210 TO CLR THE POINTED OUT TFC. ACFT #1 STATED THAT HE WAS RESPONDING TO TCASII. JUST A FEW SECONDS LATER, ACFT #1 RPTED AT FL250. I CALLED CLOVER CTL TO CONFIRM THE ALT THAT THE POINTED OUT TFC WAS AT FL200. CLOVER RESPONDED FL230. BY THAT TIME THE ACFT WERE LATERALLY SEPARATED, SO I ISSUED A DSCNT TO 17000 FT THEN OVER TO APCH WITH ACFT #1. I DIDN'T INFORM THE SUPVR WHEN IT HAPPENED BECAUSE I DID NOT REMEMBER THAT IT WAS MANDATORY TO RPT IT. I DID NOT LOSE SEPARATION.
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.