Date: 201409
Local time of day: 0601-1200
Location: ATL.Airport, GA
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ATL
ATC / advisory: TRACON A80
Aircraft component: FMS/FMC
Component problem: Design; Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Human-Machine Interface; Situational Awareness; Time Pressure; Confusion; Communication Breakdown; Distraction
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew FLC Overrode Automation
Contributing factors: Aircraft; Airport; Chart Or Publication; Human Factors; Procedure
Primary problem: Human Factors

Narrative: While on the KOLTT RNAV STAR arrival we had originally expected and configured for runway 8R. When approximately 5 miles from KOLTT we were issued a runway change to ILS PRM 9R. I saw my FO start to input the new approach into the FMS (or so I thought). I also swapped pages in my book and was given a quick briefing change due to this being a low IMC PRM approach. The problem started when the arrival runway was not changed prior to reaching KOLTT causing a course deviation. We had just about reached THUNDR (3 miles past KOLTT) when ATC advised us that we had missed a turn. He then issued vectors for the ILS PRM 9R. The FO finished the programming of the approach at this time and the flight plan executed; however; the transition was not put in correctly giving a discontinuity on the approach. We were both heads down trying to figure out why the approach was not being displayed correctly. At this time we were given direct ANDIY for which was executed and the NAV button pushed; however the FMS did not arm or capture. We were very close to the fix which added to the confusion. As the aircraft started to pass ANDIY I rotated the heading bug around to fly inbound on the approach still fully expected the FMS to capture. It did not and we continued to drift to the south until we were approximately 1 mile south of course at 21 DME when I turned off the autopilot and corrected the approach alignment. The rest of the approach and landing were normal and to SOP. I believe due to the high workload and last minute runway change along with a stick NAV button caused a compounding situation up to and including the course deviation. We can not always anticipate last minute runway changes and must work through them as a crew with good CRM.'While on the KOLTT RNAV STAR arrival we had originally expected and configured for runway 8R. When approximately 5 miles from KOLTT we were issued a runway change to ILS PRM 9R. I saw my FO start to input the new approach into the FMS (or so I thought). I also swapped pages in my book and was given a quick briefing change due to this being a low IMC PRM approach. The problem started when the arrival runway was not changed prior to reaching KOLTT causing a course deviation. We had just about reached THNDR (3 miles past KOLTT) when ATC advised us that we had missed a turn. He then issued vectors for the ILS PRM 9R. The FO finished the programming of the approach at this time and the flight plan executed; however; the transition was not put in correctly giving a discontinuity on the approach. We were both heads down trying to figure out why the approach was not being displayed correctly. At this time we were given direct ANDIY for which was executed and the NAV button pushed; however the FMS did not arm or capture. We were very close to the fix which added to the confusion. As the aircraft started to pass ANDIY I rotated the heading bug around to fly inbound on the approach still fully expected the FMS to capture. It did not and we continued to drift to the south until we were approximately 1 mile south of course at 21 DME when I turned off the autopilot and corrected the approach alignment. The rest of the approach and landing were normal and to SOP. I believe due to the high workload and last minute runway change along with a stick NAV button caused a compounding situation up to and including the course deviation. We can not always anticipate last minute runway changes and must work through them as a crew with good CRM.




Synopsis: A CRJ-900 flight crew just five miles from KOLTT on the KOLTT RNAV STAR--having planned for; programmed and briefed for a landing on Runway 8R--was instead changed to land on Runway 9R. The First Officer was unable to program the substantial changes of routing and approach; causing multiple track deviations and the ultimate disengagement of all auto flight tools to execute a manual approach and landing.