Erj-170 flight crew reported a track deviation and an airborne conflict shortly after takeoff from a...

Attributes
ACN	1319933
Time
Date	201512
Local Time Of Day	1801-2400
Place
Locale Reference	ATL.Airport
State Reference	GA
Environment
Flight Conditions	IMC
Aircraft 1
Make Model Name	EMB ERJ 170/175 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	SID UGAAA6
Flight Plan	IFR
Person 1
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Clearance was UGAAA6 ahn transition. Push clearance was tail north; indicating a 9L departure. The FMS was programmed for 8R and was not changed. The taxi check was completed and the brief was UGAAA6; 10;000; ronii was called as the first fix; I did not catch this. We were issued to line up and wait; followed by a takeoff clearance; RNAV to lidas. We took off with the wrong runway programmed in the FMS and when the navigation was selected at 400 feet we were tracking the wrong course. We received an RA; complied with it; and were then issued a heading to fly to get us back on our appropriate course. We continued without having further incidences.when we were issued the push clearance indicating a 9L departure; I should have reverified the FMS. It was a busy taxi; yet in retrospect I should have set the brake and visually confirmed the FMS and the first fix. Upon accepting the line up and wait clearance I should have verified the runway on the flight plan page. The extra seconds to do these actions would have prevented this loss of separation.

Original NASA ASRS Text

Title: ERJ-170 flight crew reported a track deviation and an airborne conflict shortly after takeoff from ATL when they failed to reprogram the FMS following a late runway change on taxi out.

Narrative: Clearance was UGAAA6 AHN transition. Push clearance was tail north; indicating a 9L departure. The FMS was programmed for 8R and was not changed. The taxi check was completed and the brief was UGAAA6; 10;000; RONII was called as the first fix; I did not catch this. We were issued to line up and wait; followed by a takeoff clearance; RNAV to LIDAS. We took off with the wrong runway programmed in the FMS and when the navigation was selected at 400 feet we were tracking the wrong course. We received an RA; complied with it; and were then issued a heading to fly to get us back on our appropriate course. We continued without having further incidences.When we were issued the push clearance indicating a 9L departure; I should have reverified the FMS. It was a busy taxi; yet in retrospect I should have set the brake and visually confirmed the FMS and the first fix. Upon accepting the line up and wait clearance I should have verified the runway on the flight plan page. The extra seconds to do these actions would have prevented this loss of separation.

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.

Erj-170 flight crew reported a track deviation and an airborne conflict shortly after takeoff from atl when they failed to reprogram the FMS following a late runway change on taxi out.