CL600 first officer reported taking off with a data error of 10;000 pounds entered into the FMS. FMS...

Narrative:

While inputting data into the FMS; each key stroke would often cause multiple digits to populate the scratch pad. When entering the fuel weight into the ACARS for the track detail message (tdm); I input 1;100 instead of 11;000. We didn't receive any error message and don't notice it. We set the speeds according to the tdm. We took off from atl with takeoff data that was 10;000 pounds too low. I realized it when I pulled up our landing data and our fuel on arrival was -3;000 pounds.we didn't encounter any low speed indications; probably because the N1 setting was higher than the N1 required in the tdm. However; taking off with speeds predicated on erroneous takeoff weight was unsafe and could have resulted in an undesired aircraft state.fix the FMS anomaly that causes multiple characters per key stroke. Program safeties for the fuel amount; similar to those that exist for the number of passengers in each zone; so that the ACARS wouldn't accept a planned fuel that would result in landing with unreasonable amounts of fuel. By the way; we received landing data included -3;000 pounds of estimated fuel on arrival; and the aircraft landing weight was stated as zero fuel weight (ZFW) minus 3;000 pounds.

Original NASA ASRS Text

Title: CL600 FO reported taking off with a data error of 10;000 LBS entered into the FMS. FMS multiple character input issue was a factor in the incident.

Narrative: While inputting data into the FMS; each key stroke would often cause multiple digits to populate the scratch pad. When entering the fuel weight into the ACARS for the Track Detail Message (TDM); I input 1;100 instead of 11;000. We didn't receive any error message and don't notice it. We set the speeds according to the TDM. We took off from ATL with takeoff data that was 10;000 pounds too low. I realized it when I pulled up our landing data and our fuel on arrival was -3;000 pounds.We didn't encounter any low speed indications; probably because the N1 setting was higher than the N1 required in the TDM. However; taking off with speeds predicated on erroneous takeoff weight was unsafe and could have resulted in an undesired aircraft state.Fix the FMS anomaly that causes multiple characters per key stroke. Program safeties for the fuel amount; similar to those that exist for the number of passengers in each zone; so that the ACARS wouldn't accept a planned fuel that would result in landing with unreasonable amounts of fuel. By the way; we received landing data included -3;000 pounds of estimated fuel on arrival; and the aircraft landing weight was stated as Zero Fuel Weight (ZFW) minus 3;000 pounds.

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.

Attributes
ACN	1285762
Time
Date	201508
Local Time Of Day	0601-1200
Place
Locale Reference	ATL.Airport
State Reference	GA
Aircraft 1
Make Model Name	Regional Jet 900 (CRJ900)
Operating Under FAR Part	Part 121
Flight Phase	Parked
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy

CL600 first officer reported taking off with a data error of 10;000 pounds entered into the FMS. FMS multiple character input issue was a factor in the incident.