B737-300 crew departed the gate with a weight and balance form intended for a B737-500 aircraft.

Attributes
ACN	560761
Time
Date	200209
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : oak.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 18000 flight time type : 15000
ASRS Report	560761
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial
Experience	flight time last 90 days : 190 flight time total : 5000 flight time type : 2000
ASRS Report	560303
Events
Anomaly	non adherence : far non adherence : published procedure non adherence : company policies other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact other
Consequence	other
Supplementary
Problem Areas	Company Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Incorrect weight/balance load sheet. A newly trained operations agent prepared our load sheet. He had some math problems in the preparatory, and as a result, he got in a hurry. The load sheet was folded in the appropriate manner (about 1/2 way, just above the passenger count box), tossed on the radar scope, and we then pushed back, started engines and taxied towards the runway after the checklists were completed. On further review of the load sheet, we realized, in fact, that it was a 500 load sheet, and, of course, we were in a 300 model. We called dispatch and taxied back to the gate, kept engines running, swapped for the correct load sheet, pushed back, taxied, and continued on. Suggestions: 1) better train operations agents. 2) don't fold loading schedule. 3) print model number (-200, -300, -500, -700) around edge of load sheet. 4) memorize model number load sheet color codes.

Original NASA ASRS Text

Title: B737-300 CREW DEPARTED THE GATE WITH A WT AND BAL FORM INTENDED FOR A B737-500 ACFT.

Narrative: INCORRECT WT/BAL LOAD SHEET. A NEWLY TRAINED OPS AGENT PREPARED OUR LOAD SHEET. HE HAD SOME MATH PROBS IN THE PREPARATORY, AND AS A RESULT, HE GOT IN A HURRY. THE LOAD SHEET WAS FOLDED IN THE APPROPRIATE MANNER (ABOUT 1/2 WAY, JUST ABOVE THE PAX COUNT BOX), TOSSED ON THE RADAR SCOPE, AND WE THEN PUSHED BACK, STARTED ENGS AND TAXIED TOWARDS THE RWY AFTER THE CHKLISTS WERE COMPLETED. ON FURTHER REVIEW OF THE LOAD SHEET, WE REALIZED, IN FACT, THAT IT WAS A 500 LOAD SHEET, AND, OF COURSE, WE WERE IN A 300 MODEL. WE CALLED DISPATCH AND TAXIED BACK TO THE GATE, KEPT ENGS RUNNING, SWAPPED FOR THE CORRECT LOAD SHEET, PUSHED BACK, TAXIED, AND CONTINUED ON. SUGGESTIONS: 1) BETTER TRAIN OPS AGENTS. 2) DON'T FOLD LOADING SCHEDULE. 3) PRINT MODEL NUMBER (-200, -300, -500, -700) AROUND EDGE OF LOAD SHEET. 4) MEMORIZE MODEL NUMBER LOAD SHEET COLOR CODES.

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.