An air carrier medium large transport took off with improper paperwork.

Attributes
ACN	317047
Time
Date	199509
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : clt
State Reference	NC
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 6000 flight time type : 200
ASRS Report	317047
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : less severe non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Air Traffic Incident	Pilot Deviation other

Narrative:

Dispatch provided takeoff data for south departure runways. Using ACARS, I requested north departure takeoff data due to ATIS stating north departures in use. Company policy is ACARS takeoff data is a 'stand alone' document if received after final closeout. The FMC uplinked the data from dispatch and it matched the ACARS takeoff data exactly in gross weight/stabilizer trim/flaps/center gravity. During taxi, originally we were assigned runway 36, then changed to runway 05. FMC was changed to runway 05, and all numbers matched takeoff power setting. Quite often, during this phase, we are using all the same formats and printout. Since the numbers and parameters were matching perfectly, I assumed we had a final close out. After takeoff, I realized we hadn't received the actual closeout ACARS printout. I called operations and they were mystified. Printout came up a few mins later. Final closeout was the same in all parameters as the original ACARS tps. I have noticed a possible break that may occur and have sent several recommendations to the company: no 'stand alone' ACARS tps printouts, change in checklist to prevent this, a check on myself to be more attentive during paperwork phase while taxiing.

Original NASA ASRS Text

Title: AN ACR MLG TOOK OFF WITH IMPROPER PAPERWORK.

Narrative: DISPATCH PROVIDED TKOF DATA FOR S DEP RWYS. USING ACARS, I REQUESTED N DEP TKOF DATA DUE TO ATIS STATING N DEPS IN USE. COMPANY POLICY IS ACARS TKOF DATA IS A 'STAND ALONE' DOCUMENT IF RECEIVED AFTER FINAL CLOSEOUT. THE FMC UPLINKED THE DATA FROM DISPATCH AND IT MATCHED THE ACARS TKOF DATA EXACTLY IN GROSS WT/STABILIZER TRIM/FLAPS/CTR GRAVITY. DURING TAXI, ORIGINALLY WE WERE ASSIGNED RWY 36, THEN CHANGED TO RWY 05. FMC WAS CHANGED TO RWY 05, AND ALL NUMBERS MATCHED TKOF PWR SETTING. QUITE OFTEN, DURING THIS PHASE, WE ARE USING ALL THE SAME FORMATS AND PRINTOUT. SINCE THE NUMBERS AND PARAMETERS WERE MATCHING PERFECTLY, I ASSUMED WE HAD A FINAL CLOSE OUT. AFTER TKOF, I REALIZED WE HADN'T RECEIVED THE ACTUAL CLOSEOUT ACARS PRINTOUT. I CALLED OPS AND THEY WERE MYSTIFIED. PRINTOUT CAME UP A FEW MINS LATER. FINAL CLOSEOUT WAS THE SAME IN ALL PARAMETERS AS THE ORIGINAL ACARS TPS. I HAVE NOTICED A POSSIBLE BREAK THAT MAY OCCUR AND HAVE SENT SEVERAL RECOMMENDATIONS TO THE COMPANY: NO 'STAND ALONE' ACARS TPS PRINTOUTS, CHANGE IN CHKLIST TO PREVENT THIS, A CHK ON MYSELF TO BE MORE ATTENTIVE DURING PAPERWORK PHASE WHILE TAXIING.

Data retrieved from NASA's ASRS site as of July 2007 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.