37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1502482 |
Time | |
Date | 201712 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Ground Event / Encounter Other / Unknown |
Narrative:
This was flying a different arrival then was correct. We were about to start to descend on the arrival when an error message displayed on the FMS stating the ILS runway were mismatched and they did not correspond to each other. This was new to me and I knew I would need to hard tune the frequency which I had read about or never done. About this time we were given a descend via and down we went trying to trouble shoot what was going on; sometime after ATC asked what arrival we were flying because of the altitude and we were re-cleared the correct arrival. And that was that.this goes back to before we took off. We had an unusual deicing because it had been sometime since this station had done it and it was slow. We had to call ground twice once to deice at the gate and the other to taxi. [When we called] for taxi ATC changed our arrival. I believe I changed it but I can't remember but what I did; the FMS was showing the incorrect flight number which was really strange; like it changed itself. That was correct and we left. This was a quick flight and we were busy. Getting close to the arrival myself and the other guy saw the FMS ILS error and both of us moved our attention to this. This was about the time to verify the arrival which I had started to do I even had the correct jeppesen chart; but because arrivals have almost identical routing to a point that then one goes north the other south; I had seen most of the arrival until the error happened then I was looking at that then came the descend clearance and we found that it was not right. Maybe the FMS error loaded the original route because of the wrong flight number or maybe I simply missed it with the reconfiguration from deicing and with the change in performance numbers. We have a procedure to catch this but I think we fell into the trap of a new error with the FMS and somebody needs to be flying the plane period no matter what. Also this happening at a time right before we check it and the arrivals having near identical structures. This was not an ECAM (electronic centralized aircraft monitor) just a little amber letters that affect how we were going to land that I had never seen so we both took notice until. Again I believe as we already do that the person who is flying flies period.
Original NASA ASRS Text
Title: A321 flight crew reported flying the incorrect arrival after some distractions both on the ground and in the air.
Narrative: This was flying a different arrival then was correct. We were about to start to descend on the arrival when an error message displayed on the FMS stating the ILS runway were mismatched and they did not correspond to each other. This was new to me and I knew I would need to hard tune the frequency which I had read about or never done. About this time we were given a descend via and down we went trying to trouble shoot what was going on; sometime after ATC asked what arrival we were flying because of the altitude and we were re-cleared the correct arrival. And that was that.This goes back to before we took off. We had an unusual deicing because it had been sometime since this station had done it and it was slow. We had to call ground twice once to deice at the gate and the other to taxi. [When we called] for taxi ATC changed our arrival. I believe I changed it but I can't remember but what I did; the FMS was showing the incorrect flight number which was really strange; like it changed itself. That was correct and we left. This was a quick flight and we were busy. Getting close to the arrival myself and the other guy saw the FMS ILS error and both of us moved our attention to this. This was about the time to verify the arrival which I had started to do I even had the correct Jeppesen chart; but because arrivals have almost identical routing to a point that then one goes north the other south; I had seen most of the arrival until the error happened then I was looking at that then came the descend clearance and we found that it was not right. Maybe the FMS error loaded the original route because of the wrong flight number or maybe I simply missed it with the reconfiguration from deicing and with the change in performance numbers. We have a procedure to catch this but I think we fell into the trap of a new error with the FMS and somebody needs to be flying the plane period no matter what. Also this happening at a time right before we check it and the arrivals having near identical structures. This was not an ECAM (Electronic Centralized Aircraft Monitor) just a little amber letters that affect how we were going to land that I had never seen so we both took notice until. Again I believe as we already do that the person who is flying flies period.
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.