Date: 201708
Local time of day: 0601-1200
Location: DCA.Airport, DC
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B DCA
ATC / advisory: Tower DCA
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Following take off from 15; at 400 feet; I called for NAV mode as we were flying the HORTO2 RNAV departure. The First Officer (FO) selected NAV and confirmed 'FMS.' I happened to look down at the CDI and saw the head of the needle pointing toward HORTO which was behind us! My first reaction was we didn't have the proper runway selected. The FO checked the FMS and said it showed 15. The MFD showed the proper ground track. I expected the next fix to be CAPVC. Having briefed this at the gate; I knew a right turn was required at 515 feet; so I started a right turn. Then; the FMS 'caught up' with us. I've never seen this on any FMS before. After returning to DCA; we were able to depart 15 again. The second time; the FMS worked properly.Not sure what the cause was. We did have some ACARS issues enroute which seemed due to the ACARS-FMS keypad interface. I don't know if those are somehow related.


Second narrative: Following a runway change to 15 from 19 the FMS either dropped out or was never updated with the departure runway. We already had set the aircraft up and briefed for 19. On the initial climb out the Captain (CA) caught the fact that the Map page was blank. He then verbally remarked that there was no runway entered into the FMS after he tried to call for NAV. I reacted by trying to change the FMS to input the runway back into the box. At the same time a caution appeared for a Right AOA HEAT error. At this point we were still in our initial climb phase. This caused me to get distracted as I had to see what the message was. When I saw it was something we could handle at a later point I refocused on reentering the runway. I entered 15 into the SID; executed; and told the CA we had good NAV. During this the CA had started a turn at 512 feet as depicted on the SID. However; with the delay in reacting to the FMS combined with the caution message we flew beyond the SID turn by at least 2 miles. We competed the turn on NAV/FMS and continued with no other issues on the SID. Failure to check the FMS during the Takeoff Brief for a runway change by myself. Whether the FMS dropped out or the runway was never entered was not known. We only realized it after rotation.


Synopsis: CRJ200 flight crew reported departing Runway 15 at DCA on the HORTO2 RNAV with Runway 19 selected in the FMC. The Captain turned late at 515 feet while the First Officer corrected the FMC.