37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 175053 |
Time | |
Date | 199103 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : hkg |
State Reference | FO |
Altitude | agl bound lower : 3000 agl bound upper : 3000 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : hkg |
Operator | common carrier : air carrier |
Make Model Name | Widebody, Low Wing, 4 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | descent : approach descent other landing : go around |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 90 flight time total : 5000 flight time type : 180 |
ASRS Report | 175053 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were descending and being vectored for an ILS to runway 31 in hkg, bcc. The controller informed us that we would be vectored through the localizer. We were on near perpendicular path to cross the localizer. The aircraft was on autoplt (command) and map was selected on the nd. After passing through the localizer, ATC gave us a turn to 240 degrees (approximately). At some point I looked at raw data on the pfd and believe (although not completely sure looking back) that it indicated as expected. ATC gave us a further turn to the right and cleared us for ILS 31 approach. We had manually set course and frequency for ILS 31. We had discussed deselecting pou VOR for navigation updating, but felt we had a new data base that didn't include it (possibly an error on our part). I selected approach on the MCP and stayed in missed approach. It showed we were a few mi southwest of OM and would intercept the localizer approximately at the OM. G/south captured and we commenced descent. My intention was to select approach display the no at intercept. I didn't check pfd raw data as we approached (should have). Just as we showed we were approaching the marker (with about a 30 degree intercept), ATC informed we were 3 1/2 mi right off localizer, go around. ATC turned as out over the water, climbed to 4500'. We shot the approach (with nd in approach) and landed. Something seemed slightly odd about the second vector turn after the localizer (still interminable). The unexpected go around was unsettling. A vector to turn right while right of course over tathong point caused brief confusion (executed as instructed). Had one of the nd's been in approach early on, we would have had a much better change of catching the shift than relying on raw data (pfd) for initial maneuvering. The latest I will select approach (nd) will be when I select approach (MCP). 'Cleared for the approach' should be taught as a 2-SWITCH-event (approach and approach). Simulator training should also demonstrate shifts in ingrain and develop patterns to catch it. This would help a lot. Note: with a firehose-in-the-mouth pace in initial training and 10 actual lndgs since 10/90, true proficiency is slow coming in this aircraft.
Original NASA ASRS Text
Title: ACR WDB TRACK HEADING DEVIATION DURING IAP ILS APCH TO HKG AT NIGHT. APCH CTLR HAD TO CALL A GO AROUND BECAUSE OF TRACK DEVIATION.
Narrative: WE WERE DSNDING AND BEING VECTORED FOR AN ILS TO RWY 31 IN HKG, BCC. THE CTLR INFORMED US THAT WE WOULD BE VECTORED THROUGH THE LOC. WE WERE ON NEAR PERPENDICULAR PATH TO CROSS THE LOC. THE ACFT WAS ON AUTOPLT (COMMAND) AND MAP WAS SELECTED ON THE ND. AFTER PASSING THROUGH THE LOC, ATC GAVE US A TURN TO 240 DEGS (APPROX). AT SOME POINT I LOOKED AT RAW DATA ON THE PFD AND BELIEVE (ALTHOUGH NOT COMPLETELY SURE LOOKING BACK) THAT IT INDICATED AS EXPECTED. ATC GAVE US A FURTHER TURN TO THE RIGHT AND CLRED US FOR ILS 31 APCH. WE HAD MANUALLY SET COURSE AND FREQ FOR ILS 31. WE HAD DISCUSSED DESELECTING POU VOR FOR NAVIGATION UPDATING, BUT FELT WE HAD A NEW DATA BASE THAT DIDN'T INCLUDE IT (POSSIBLY AN ERROR ON OUR PART). I SELECTED APCH ON THE MCP AND STAYED IN MISSED APCH. IT SHOWED WE WERE A FEW MI SW OF OM AND WOULD INTERCEPT THE LOC APPROX AT THE OM. G/S CAPTURED AND WE COMMENCED DSNT. MY INTENTION WAS TO SELECT APCH DISPLAY THE NO AT INTERCEPT. I DIDN'T CHK PFD RAW DATA AS WE APCHED (SHOULD HAVE). JUST AS WE SHOWED WE WERE APCHING THE MARKER (WITH ABOUT A 30 DEG INTERCEPT), ATC INFORMED WE WERE 3 1/2 MI RIGHT OFF LOC, GO AROUND. ATC TURNED AS OUT OVER THE WATER, CLBED TO 4500'. WE SHOT THE APCH (WITH ND IN APCH) AND LANDED. SOMETHING SEEMED SLIGHTLY ODD ABOUT THE SECOND VECTOR TURN AFTER THE LOC (STILL INTERMINABLE). THE UNEXPECTED GAR WAS UNSETTLING. A VECTOR TO TURN RIGHT WHILE RIGHT OF COURSE OVER TATHONG POINT CAUSED BRIEF CONFUSION (EXECUTED AS INSTRUCTED). HAD ONE OF THE ND'S BEEN IN APCH EARLY ON, WE WOULD HAVE HAD A MUCH BETTER CHANGE OF CATCHING THE SHIFT THAN RELYING ON RAW DATA (PFD) FOR INITIAL MANEUVERING. THE LATEST I WILL SELECT APCH (ND) WILL BE WHEN I SELECT APCH (MCP). 'CLRED FOR THE APCH' SHOULD BE TAUGHT AS A 2-SWITCH-EVENT (APCH AND APCH). SIMULATOR TRNING SHOULD ALSO DEMONSTRATE SHIFTS IN INGRAIN AND DEVELOP PATTERNS TO CATCH IT. THIS WOULD HELP A LOT. NOTE: WITH A FIREHOSE-IN-THE-MOUTH PACE IN INITIAL TRNING AND 10 ACTUAL LNDGS SINCE 10/90, TRUE PROFICIENCY IS SLOW COMING IN THIS ACFT.
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.