Narrative:

Cleared via koltt one RNAV arrival from original filed flight plan; then clearance as filed by dispatch. Programmed FMC for runway atl ILS 26R based on current ATIS and prior experience that landings in atl are usually on shorter runways and with arrival from the north; 26R was expectation and highest probability. Initial descent via arrival and ATC altitudes assignments; to include crossing erlin at 14;000 at 280 knots. Initial contact with atl approach control confirmed runway 26R as assigned landing runway. Then over or just after passing koltt and in descent to 7;000 feet; landing runway was changed to 27L and told to 'follow runway 27L path.' as pilot monitoring; I immediately selected ILS 27L from FMS database; and then attempted to select koltt arrival for 27L. There are 18 pages of arrivals for atl and FMS would not cycle through the arrivals to correct page. Tried to get the correct page for 25-30 seconds; too long. At the same time; the pilot flying was attempting to manually enter eagyl fix to get an initial heading to join the arrival. The pilot flying asked me to get a heading from ATC; and I told ATC that 'XXX; having FMS programming problem; request heading.' ATC issued a heading of 170; pilot flying made the heading change; and then was heads down making inputs on his CDU to manually input points on the arrival starting with eagyl. Both pilot flying and pilot monitoring were heads down making inputs. I took over making FMC inputs after eagyl through tammy. The boxed items on the descent checklist were completed. We were turned to 095 heading; but inside the programmed/charted koltt RNAV flight path. I asked approach control how long the final was and was told '10 miles.' shortly afterwards; approach control turned us north; heading 360; asked is we had the field in sight; pilot flying said he had the field; and I told approach control; 'XXX; has field in sight.' the vector was just outside the final approach fix. We were cleared for a visual approach; and switched to tower frequency. Remainder of approach and landing were normal. Preventive measure: there are 18 pages of arrivals for atl in the FMS database; starts on page one when departure/arrival selected. It is time-consuming to get to the desired page in a short time period. It was taking several seconds to cycle from one page to the next...too long in a time critical segment. Pilot flying was making manual arrival fix inputs; as pilot monitoring was trying to select the correct koltt RNAV arrival for 27L. Selected ILS 27L first; thinking it might limit the arrival choices...it did not. Didn't realize the pilot flying was heads down also; until he said he had eagyl fix programmed. Kept trying to get the arrival page too long; maybe 20-25 seconds. Both pilots were heads down for 15-20 seconds; too long for phase of flight; though augmented crew was theoretically was listening and watching. Should have just stayed with heading assignments from approach control. Fortunately; it was VFR. Seems making a 'short notice' runway change by approach control; requiring FMS reprogramming; and telling the crew to follow the '27L path;' a terminology or phraseology I am not familiar with; added unnecessary threat to the arrival.

Google
 

Original NASA ASRS Text

Title: An air carrier international crew reported that A80 changed the approach over KOLTT on the ATL KOLTT 1 from an ILS 26R to Runway 27L and because there are 18 pages of arrivals the crew requested vectors to final while re-programming the FMS.

Narrative: Cleared via KOLTT ONE RNAV arrival from original filed flight plan; then clearance as filed by Dispatch. Programmed FMC for Runway ATL ILS 26R based on current ATIS and prior experience that landings in ATL are usually on shorter runways and with arrival from the north; 26R was expectation and highest probability. Initial descent via arrival and ATC altitudes assignments; to include crossing ERLIN at 14;000 at 280 knots. Initial contact with ATL Approach Control confirmed Runway 26R as assigned landing runway. Then over or just after passing KOLTT and in descent to 7;000 feet; landing runway was changed to 27L and told to 'follow Runway 27L path.' As Pilot Monitoring; I immediately selected ILS 27L from FMS database; and then attempted to select KOLTT arrival for 27L. There are 18 pages of arrivals for ATL and FMS would not cycle through the arrivals to correct page. Tried to get the correct page for 25-30 seconds; too long. At the same time; the Pilot Flying was attempting to manually enter EAGYL fix to get an initial heading to join the arrival. The Pilot Flying asked me to get a heading from ATC; and I told ATC that 'XXX; having FMS programming problem; request heading.' ATC issued a heading of 170; Pilot Flying made the heading change; and then was heads down making inputs on his CDU to manually input points on the arrival starting with EAGYL. Both Pilot Flying and Pilot Monitoring were heads down making inputs. I took over making FMC inputs after EAGYL through TAMMY. The boxed items on the descent checklist were completed. We were turned to 095 heading; but inside the programmed/charted KOLTT RNAV flight path. I asked Approach Control how long the final was and was told '10 miles.' Shortly afterwards; Approach Control turned us north; heading 360; asked is we had the field in sight; Pilot Flying said he had the field; and I told Approach Control; 'XXX; has field in sight.' The vector was just outside the final approach fix. We were cleared for a visual approach; and switched to Tower frequency. Remainder of approach and landing were normal. Preventive Measure: There are 18 pages of arrivals for ATL in the FMS database; starts on page one when DEP/ARR selected. It is time-consuming to get to the desired page in a short time period. It was taking several seconds to cycle from one page to the next...too long in a time critical segment. Pilot Flying was making manual arrival fix inputs; as Pilot Monitoring was trying to select the correct KOLTT RNAV arrival for 27L. Selected ILS 27L first; thinking it might limit the arrival choices...it did not. Didn't realize the Pilot Flying was heads down also; until he said he had EAGYL fix programmed. Kept trying to get the arrival page too long; maybe 20-25 seconds. Both pilots were heads down for 15-20 seconds; too long for phase of flight; though augmented crew was theoretically was listening and watching. Should have just stayed with heading assignments from Approach Control. Fortunately; it was VFR. Seems making a 'short notice' runway change by Approach Control; requiring FMS reprogramming; and telling the crew to follow the '27L path;' a terminology or phraseology I am not familiar with; added unnecessary threat to the arrival.

Data retrieved from NASA's ASRS site as of July 2013 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.