MD-11
Flight Crew Air Transport Pilot (ATP)
Human-Machine Interface; Distraction; Time Pressure; Situational Awareness; Communication Breakdown
Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Overcame Equipment Problem
Human Factors
Taking the runway; cleared for takeoff; when the FO (First Officer) called out 'FMC' I got to where I normally check 'NAV armed' and I realized I had never selected a runway in the FMS. We had V speeds and everything looked (almost) normal. I told the FO to select the runway; not thinking this would wipe out our V Speeds. We started the roll; I called '80 knots'; made one last check of the engine instruments and looked up. At this point I noticed the display wasn't right. We were already over 100 kts. So I elected to continue. I knew rotate speed was in the low 160 knot range (turned out it was 162) so I waited and called rotate at 170. FO called out he didn't have a Flight Director. He did a nice job of flying the jet. After some confusion we got PROF selected and the Flight Director was once again active. Causal chain started early. Last flight of trip. FO and I get along well; very comfortable with each other. When doing the numbers; I obviously missed that the FMS didn't have a runway in when I called 'runway'. I was just listening for the correct response from the FO.  Then; taking the runway; I should have stopped the airplane and solved the problem. There was no reason to rush. We could have taxied off the runway if necessary to make sure we had it all squared away. It was complacency on my part that missed the lack of a runway in the FMS. I usually stare right at it when I call 'runway' and obviously I wasn't. I've caught this same mistake in the past. Then when I realized the mistake taking the runway I should have stopped everything and solved the problem as a crew. Biggest set of errors in my career and most dangerous.
MD11 Captain reported failure to properly program FMS prior to takeoff.