37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 338449 |
Time | |
Date | 199606 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : rnt airport : bfi |
State Reference | WA |
Altitude | msl bound lower : 3000 msl bound upper : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : bfi artcc : saez |
Operator | general aviation : corporate |
Make Model Name | Challenger CL600 |
Operating Under FAR Part | Part 91 |
Navigation In Use | Other Other |
Flight Phase | descent : approach |
Route In Use | approach : visual enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 95 flight time total : 11100 flight time type : 3200 |
ASRS Report | 338449 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | flight crew : returned to intended course or assigned course other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
While on vectors for bfi for a visual runway 31, aircraft passed through final approach course for back course localizer to runway. At that time controller cleared us for the back course and a vector to the approach. The vector lined the aircraft with the runway at renton field runway 33. First officer called airport in sight and we proceeded visual and were cleared to tower. An alert controller at boeing field noticed that we were off course and notified us. This prevented us from continuing further and we proceeded back to the final course for runway 31 at bfi. Had he not noticed it would have been possible to have continued on to renton since the first officer had misidented the runway. After landing I checked with tower and they said this was a common error. Had I crosschecked our instruments more I would have idented the error sooner. Lesson: night strange field stay on the gauges or with the control as long as possible. Don't be anxious to call the field and go VFR.
Original NASA ASRS Text
Title: FLC OF A CANADAIR CL60 MAKING AN APCH TO ONE ARPT RPTED THE RWY IN SIGHT WHEN THEY WERE LOOKING AT AND LINED UP WITH ANOTHER ARPT RWY. THE TWR CTLR AT THE DEST ARPT NOTICED THEIR MISTAKE AND INTERVENED TO ALERT THEM AND BRING THEM BACK TO THE CORRECT ARPT.
Narrative: WHILE ON VECTORS FOR BFI FOR A VISUAL RWY 31, ACFT PASSED THROUGH FINAL APCH COURSE FOR BACK COURSE LOC TO RWY. AT THAT TIME CTLR CLRED US FOR THE BACK COURSE AND A VECTOR TO THE APCH. THE VECTOR LINED THE ACFT WITH THE RWY AT RENTON FIELD RWY 33. FO CALLED ARPT IN SIGHT AND WE PROCEEDED VISUAL AND WERE CLRED TO TWR. AN ALERT CTLR AT BOEING FIELD NOTICED THAT WE WERE OFF COURSE AND NOTIFIED US. THIS PREVENTED US FROM CONTINUING FURTHER AND WE PROCEEDED BACK TO THE FINAL COURSE FOR RWY 31 AT BFI. HAD HE NOT NOTICED IT WOULD HAVE BEEN POSSIBLE TO HAVE CONTINUED ON TO RENTON SINCE THE FO HAD MISIDENTED THE RWY. AFTER LNDG I CHKED WITH TWR AND THEY SAID THIS WAS A COMMON ERROR. HAD I XCHKED OUR INSTS MORE I WOULD HAVE IDENTED THE ERROR SOONER. LESSON: NIGHT STRANGE FIELD STAY ON THE GAUGES OR WITH THE CTL AS LONG AS POSSIBLE. DON'T BE ANXIOUS TO CALL THE FIELD AND GO VFR.
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.