37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1301497 |
Time | |
Date | 201510 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Dash 8-400 |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural FAR Deviation - Procedural Weight And Balance |
Narrative:
We were given our load sheet by the ramp crew and nothing looked out of the ordinary. They had amended an original count of 22 bags in R1 to 24 in R1 and it was correctly crossed out with a single line and initialed by the ramp agent. Due to VHF no communication the captain had to call for numbers. The performance solution came back with a valid solution and we departed.while in cruise we got an ACARS message from dispatch that we had been given a false load report and we had 22 bags in R1 that were not reflected on our load sheet. We asked dispatch to rerun our takeoff numbers with the correct number of bags and it turned out that we had departed out of cg to the rear and would have needed to move 100lbs to F1 to be within cg. We did have a uniformed jumpseater from another carrier who had come up to the flight deck prior to departure. He believed he was going to be up front so we had verified his status and checked his required documents to occupy the jumpseat. The captain asked dispatch to rerun the numbers with the jumpseater in the flight deck jumpseat instead of the cabin and that put us in cg. As we had verified his status the captain asked him to occupy the jumpseat for landing. We landed without incident.possible solution: an automated system which links the bags scanned by the ramp with the hand reader to the ACARS system or to dispatch.
Original NASA ASRS Text
Title: While in cruise flight; DHC8-400 flight crew received word from Dispatch that they had departed with an incorrect load report and that the correct load would have put the aircraft out of CG limits for takeoff. However; the revised load report did not reflect an occupied jumpseat which had put the aircraft within CG.
Narrative: We were given our load sheet by the ramp crew and nothing looked out of the ordinary. They had amended an original count of 22 bags in R1 to 24 in R1 and it was correctly crossed out with a single line and initialed by the ramp agent. Due to VHF NO COM the captain had to call for numbers. The performance solution came back with a valid solution and we departed.While in cruise we got an ACARS message from Dispatch that we had been given a false load report and we had 22 bags in R1 that were not reflected on our load sheet. We asked dispatch to rerun our takeoff numbers with the correct number of bags and it turned out that we had departed out of CG to the rear and would have needed to move 100lbs to F1 to be within CG. We did have a uniformed jumpseater from another carrier who had come up to the flight deck prior to departure. He believed he was going to be up front so we had verified his status and checked his required documents to occupy the jumpseat. The captain asked Dispatch to rerun the numbers with the jumpseater in the flight deck jumpseat instead of the cabin and that put us in CG. As we had verified his status the captain asked him to occupy the jumpseat for landing. We landed without incident.Possible solution: An automated system which links the bags scanned by the ramp with the hand reader to the ACARS system or to Dispatch.
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.