 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Mem final monitor issues corrective instructions to an A306 crew on final but crew did not respond until after 3 calls.
| Attributes | |
| ACN | 628368 |
| Time | |
| Date | 200408 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : mem.airport |
| State Reference | TN |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : mem.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | A300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : mem.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar pilot : instrument |
| Experience | controller radar : 24 controller time certified in position1 : 14 |
| ASRS Report | 628368 |
| Person 2 | |
| Function | controller : approach |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance non adherence : required legal separation non adherence : published procedure |
| Independent Detector | atc equipment : conflict alert other controllera other controllerb other flight crewa other flight crewb other other : 3 |
| Resolutory Action | controller : issued advisory controller : issued new clearance controller : separated traffic flight crew : took evasive action |
| Consequence | faa : investigated |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Weather ATC Human Performance Aircraft |
| Primary Problem | Ambiguous |
Narrative:
While working final monitor west during simultaneous ILS approachs to runway 36L and 36R. Air carrier Y was not locked on the localizer for runway 36R and started to enter the ntz. The controller next to me gave instructions to air carrier Y to return and air carrier Y did not respond. When he entered the ntz I issued air carrier X a traffic alert and broke him out. At first air carrier X did not respond, so I issued the instructions again. Air carrier X did not respond so I contacted the tower to see if he had indeed checked in. The tower confirmed that he was on frequency. When I called him the third time he finally responded with the instruction I had given him several seconds earlier. This could have been a lot worse situation. I do not understand why the pilot did not respond quicker.
Original NASA ASRS Text
Title: MEM FINAL MONITOR ISSUES CORRECTIVE INSTRUCTIONS TO AN A306 CREW ON FINAL BUT CREW DID NOT RESPOND UNTIL AFTER 3 CALLS.
Narrative: WHILE WORKING FINAL MONITOR W DURING SIMULTANEOUS ILS APCHS TO RWY 36L AND 36R. ACR Y WAS NOT LOCKED ON THE LOC FOR RWY 36R AND STARTED TO ENTER THE NTZ. THE CTLR NEXT TO ME GAVE INSTRUCTIONS TO ACR Y TO RETURN AND ACR Y DID NOT RESPOND. WHEN HE ENTERED THE NTZ I ISSUED ACR X A TFC ALERT AND BROKE HIM OUT. AT FIRST ACR X DID NOT RESPOND, SO I ISSUED THE INSTRUCTIONS AGAIN. ACR X DID NOT RESPOND SO I CONTACTED THE TWR TO SEE IF HE HAD INDEED CHKED IN. THE TWR CONFIRMED THAT HE WAS ON FREQ. WHEN I CALLED HIM THE THIRD TIME HE FINALLY RESPONDED WITH THE INSTRUCTION I HAD GIVEN HIM SEVERAL SECONDS EARLIER. THIS COULD HAVE BEEN A LOT WORSE SIT. I DO NOT UNDERSTAND WHY THE PLT DID NOT RESPOND QUICKER.
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.