B767-300 and 300 ER
Flight Crew Air Transport Pilot (ATP)
Situational Awareness; Distraction
Aircraft Equipment Problem Less Severe; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Became Reoriented; Flight Crew Rejected Takeoff
Human Factors
RTO due to takeoff configure warning. Planned for takeoff on Runway 27; then Tower assigned Runway 36L. First Officer proceeded to change runway in FMS then check takeoff data. Some problem in FMC prevented calculation of climb and takeoff data. Informed Tower we had a problem and stopped on taxiway. After several attempts; we reset all data in FMS and displayed takeoff and climb information. Continued taxi; cleared across intersecting runway; then shifted to parallel; but FMS problem broke up our flow and we failed to configure properly for takeoff; resulting in warning light/bell. Taxied clear; reset data; insured proper configuration; and took off safely.FMS system malfunction distracted us from normal flow of pre-takeoff checks.When any non-normal situation occurs recheck and rethink all requirements to restore situational awareness.
[Report narrative contained no additional information].
B767-300 flight crew reported they executed an RTO after they failed to properly set configuration for takeoff. Flight crew reported having difficulty reprogramming the FMS following a late runway change on taxi out that distracted them from SOP.