37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 936193 |
Time | |
Date | 201103 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation X (C750) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | ILS/VOR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 75 Flight Crew Total 12700 Flight Crew Type 3000 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
On approach being vectored to the south for a right turn to the north east to intercept the back course localizer to runway 3R. The turn on to final was a large heading change. I don't remember how many degrees. The pilot flying (not me) started the turn onto the final approach course. The needle came alive almost immediately. The pilot flying pressed 'app' instead of 'back course.' the autopilot started to turn left (ILS mode) instead of right (back course mode). The autopilot was disconnected and a course correction flown manually. About this time the controller called us telling us we had triggered a low altitude warning at our present deviation from the localizer. Notwithstanding this procedural error; the localizer was not full scale deviation and we were at the correct altitude (2;100 ft). Even though we briefed the approach; I think that a preview of our SOP's may be in order. When cleared for an approach; perhaps we should call out the mode being engaged (there are several possible approach mode selections); rather than just 'cleared for the approach.'
Original NASA ASRS Text
Title: A CE750 was vectored in tight for a back course localizer and as the localizer was coming alive the First Officer selected APP instead of BC causing the aircraft to turn the incorrect direction. The aircraft was at the correct altitude but ATC advised of a low altitude alert because the aircraft was off track.
Narrative: On approach being vectored to the south for a right turn to the north east to intercept the back course localizer to Runway 3R. The turn on to final was a large heading change. I don't remember how many degrees. The pilot flying (not me) started the turn onto the final approach course. The needle came alive almost immediately. The pilot flying pressed 'APP' instead of 'BC.' The autopilot started to turn left (ILS mode) instead of right (BC mode). The autopilot was disconnected and a course correction flown manually. About this time the Controller called us telling us we had triggered a low altitude warning at our present deviation from the localizer. Notwithstanding this procedural error; the localizer was not full scale deviation and we were at the correct altitude (2;100 FT). Even though we briefed the approach; I think that a preview of our SOP's may be in order. When cleared for an approach; perhaps we should call out the mode being engaged (there are several possible approach mode selections); rather than just 'cleared for the approach.'
Data retrieved from NASA's ASRS site as of April 2012 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.