B767-300 flight crew reported they executed an rejected takeoff after they failed to properly set co...

Attributes
ACN	1281818
Time
Date	201507
Local Time Of Day	1201-1800
Place
Locale Reference	MEM.Airport
State Reference	TN
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
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	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Speed All Types

Narrative:

Rejected takeoff 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.

Original NASA ASRS Text

Title: 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.

Narrative: 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.

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.

B767-300 flight crew reported they executed an rejected takeoff 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.