Narrative:

During the final cockpit preparation we received takeoff data from the FMC and ACARS for runway 28. However we were unable to get info for runways 32 and 34; the longer runways in use. I called dispatch and learned that this MEL had been applied to our aircraft due to local maintenance discovery. The first officer did not notice this on his walk around. Dispatch advised that we were not legal for takeoff on any runway due to the severe weight penalty. The company canceled this flight after exhausting all possible relief from this MEL.my concerns and questions:1) why did the flight crew not receive an alert regarding this change to the original signed release?2) why did we receive takeoff data for runway 28?3) why does the [release] not print in sequential page order?

Google
 

Original NASA ASRS Text

Title: B787 Captain reported that an MEL weight penalty resulted in a maintenance action and flight cancellation.

Narrative: During the final cockpit preparation we received takeoff data from the FMC and ACARS for Runway 28. However we were unable to get info for Runways 32 and 34; the longer runways in use. I called Dispatch and learned that this MEL had been applied to our aircraft due to local maintenance discovery. The First Officer did not notice this on his walk around. Dispatch advised that we were not legal for takeoff on any runway due to the severe weight penalty. The company canceled this flight after exhausting all possible relief from this MEL.My concerns and questions:1) Why did the flight crew not receive an alert regarding this change to the original signed release?2) Why did we receive takeoff data for Runway 28?3) Why does the [release] not print in sequential page order?

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.