37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1249975 |
Time | |
Date | 201503 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Component | |
Aircraft Component | Autoflight System |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
We flew a RNAV rnp app. To [destination airport]. We set up the app. Using normal airbus blue pages and the app. Was completely briefed even with our plan b that we used a visual app. After being cleared for app.; we armed the app. But we did not get what we expected on our pfd FMA. We had loc and GS in blue armed mode and ls flashing in amber but this was not what was in the box that we had checked. This would be correct for an ILS but not for an RNAV rnp. We discontinued the RNAV and since it was VMC we applied the visual app. And landed. After the shutdown checklist was complete we debriefed what might have caused the problem. We then noticed both captain and first officer radio management panel nav buttons were green. This places the nav in a manual tune situation. These are guarded push buttons and are almost never used. This explained why the aircraft was expecting an ILS even though a RNAV app was in the box. We both missed this during our preflight. The aircraft had come from the hangar and other switches normally not used were also pushed that we found during the prefight. We might also have missed this since this green push button lines up perfectly with others and so it did not look out of place. Please pass this information on to the airbus fleet so others will not make the same mistake.
Original NASA ASRS Text
Title: A319 pilot reported both he and the other cockpit crewmember during preflight missed two out of position autoflight selectors that resulted in confusion during an RNAV approach.
Narrative: We flew a RNAV RNP app. to [destination airport]. We set up the app. using normal Airbus blue pages and the app. was completely briefed even with our plan b that we used a visual app. After being cleared for app.; we armed the app. but we did not get what we expected on our PFD FMA. We had Loc and GS in blue armed mode and LS flashing in amber but this was not what was in the box that we had checked. This would be correct for an ILS but not for an RNAV RNP. We discontinued the RNAV and since it was VMC we applied the visual app. and landed. After the shutdown checklist was complete we debriefed what might have caused the problem. We then noticed both Captain and FO radio management panel Nav buttons were green. This places the nav in a manual tune situation. These are guarded push buttons and are almost never used. This explained why the aircraft was expecting an ILS even though a RNAV app was in the box. We both missed this during our preflight. The aircraft had come from the hangar and other switches normally not used were also pushed that we found during the prefight. We might also have missed this since this green push button lines up perfectly with others and so it did not look out of place. Please pass this information on to the Airbus fleet so others will not make the same mistake.
Data retrieved from NASA's ASRS site 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.