37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1618515 |
Time | |
Date | 201902 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | Us |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was the pilot monitoring on the flight. While stopped and holding short of the departure runway I requested the ATIS for ZZZ. During this process I missed that I requested the departure ATIS for ZZZ it was romeo. Once in route the pilot flying asked if I have ever been to ZZZ with our company and I stated no. He told me from his past experience we do the ILS Z xxr approach. The pilot flying set up and we briefed the ILS Z xxr approach. As we got closer; I requested an updated ATIS in which I showed to the pilot flying on the CDU. The new ATIS was foxtrot; which seemed strange to me they went from right to F. I updated the winds and altimeter on the performance software. We both missed on the ATIS they were calling for the approach ILS Y xxr. I read what I wanted to see and missed the 'Y' portion of the text. On checking in with approach they stated expect ILS xxr. As we were descending through 10;000 feet; I asked the pilot flying if he was ready for approach check. He said yes; but did not have an identification yet for the ILS. He then asked me to try to identification it from listening to it. Both pilots heard beeps but they were broken up and hard to hear. We were getting vectored for the approach and ATC told us to intercept the localizer. I told the pilot flying he needed to arm the localizer. He stated he did not have one shown. About that time; ATC gave us another heading to rejoin the localizer. I stated to ATC that we did not have the localizer for the ILS Z xxr. ATC then said they were doing the ILS Y xxr. As the pilot monitoring; I looked up the correct frequency for that localizer tuned it in and we were able to join the approach and without further incident. Once on the ground we briefed the errors; we made as a crew. For further discussion; it would be nice if the approach controller could state the exact approach in use instead of just ILS xxr. It would be beneficial for ILS yankee xxr. This was definitely pilot error on our part and very thankful there was no loss of separation by us with ATC. I will definitely be more diligent when requesting and updating the ATIS. I should have more diligence requesting and reading the ATIS. Do not 'poison the well' with type of approach expected from past experience. ATC could advise type of approach in use weather it is ILS zulu/yankee xxr/left.
Original NASA ASRS Text
Title: B757 flight crew reported misreading the ATIS and selected the incorrect approach.
Narrative: I was the Pilot Monitoring on the flight. While stopped and holding short of the departure runway I requested the ATIS for ZZZ. During this process I missed that I requested the departure ATIS for ZZZ it was ROMEO. Once in route the Pilot Flying asked if I have ever been to ZZZ with our company and I stated no. He told me from his past experience we do the ILS Z XXR approach. The Pilot Flying set up and we briefed the ILS Z XXR approach. As we got closer; I requested an updated ATIS in which I showed to the Pilot flying on the CDU. The new ATIS was Foxtrot; which seemed strange to me they went from R to F. I updated the winds and altimeter on the Performance software. We both missed on the ATIS they were calling for the approach ILS Y XXR. I read what I wanted to see and missed the 'Y' portion of the text. On checking in with approach they stated expect ILS XXR. As we were descending through 10;000 feet; I asked the Pilot Flying if he was ready for approach check. He said yes; but did not have an ID yet for the ILS. He then asked me to try to ID it from listening to it. Both Pilots heard beeps but they were broken up and hard to hear. We were getting vectored for the approach and ATC told us to intercept the localizer. I told the Pilot Flying he needed to arm the localizer. He stated he did not have one shown. About that time; ATC gave us another heading to rejoin the localizer. I stated to ATC that we did not have the localizer for the ILS Z XXR. ATC then said they were doing the ILS Y XXR. As the Pilot Monitoring; I looked up the correct frequency for that localizer tuned it in and we were able to join the approach and without further incident. Once on the ground we briefed the errors; we made as a crew. For further discussion; it would be nice if the Approach Controller could state the exact approach in use instead of just ILS XXR. It would be beneficial for ILS YANKEE XXR. This was definitely pilot error on our part and very thankful there was no loss of separation by us with ATC. I will definitely be more diligent when requesting and updating the ATIS. I should have more diligence requesting and reading the ATIS. Do not 'poison the well' with type of approach expected from past experience. ATC could advise type of approach in use weather it is ILS ZULU/YANKEE XXR/L.
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.