Narrative:

Our release for flight to bur contained MEL 32-42-xx #4 main landing gear tachometer inoperative. We were dispatched to land on bur runway 08; mlw (maximum landing weight) 287.4; calm winds; dry; flaps 40 and included the MEL. Contacted dispatcher per directives and release note during bur construction; and confirmed ILS runway 08 would be available. About 1.5 hours into flight; ran our own landing performance data using current ATIS information and estimated landing weight of 275. The computations revealed that the only runway we could use to land was runway 33. NOTAMS showed runway 33 was scheduled to close 20-25 minutes prior to our arrival. Contacted dispatcher; and he coordinated with bur operations to keep the runway open for our arrival. There were a lot of clouds in the area and we needed 5000/5 to fly RNAV visual runway 33 approach. Once in the destination environment we attempted the visual approach; but it was obvious that we could not maintain VMC on the profile; so we terminated the approach and proceeded to silex to hold; hoping the weather would improve. Once established in holding we were informed that bur runway 33 was closed; so we proceeded to our filed alternate. The information on the release showed that we could use bur runway 08 at mlw of 287.4; including the MEL so we proceeded to bur. Our landing performance data indicated runway 08 was not valid. Some MEL's restrict landing at several short runway airports (bur; sna) and I think this one should be evaluated for that limitation. Ensure the release landing data is consistent with computation/software we use in the aircraft.

Google
 

Original NASA ASRS Text

Title: A300 flight crew discovered enroute that the landing data provided by the Dispatcher prior to departure does not agree with the data produced by their iPad app. The only suitable BUR Runway was 33 which was accessed via an RNAV visual; but the weather did not allow. The crew diverted to their alternate airport.

Narrative: Our release for flight to BUR contained MEL 32-42-XX #4 Main Landing Gear Tachometer INOP. We were dispatched to land on BUR Runway 08; MLW (Maximum Landing Weight) 287.4; calm winds; dry; flaps 40 and included the MEL. Contacted dispatcher per directives and release note during BUR construction; and confirmed ILS Runway 08 would be available. About 1.5 hours into flight; ran our own landing performance data using current ATIS information and estimated landing weight of 275. The computations revealed that the only runway we could use to land was Runway 33. NOTAMS showed Runway 33 was scheduled to close 20-25 minutes prior to our arrival. Contacted dispatcher; and he coordinated with BUR operations to keep the runway open for our arrival. There were a lot of clouds in the area and we needed 5000/5 to fly RNAV Visual Runway 33 approach. Once in the destination environment we attempted the Visual approach; but it was obvious that we could not maintain VMC on the profile; so we terminated the approach and proceeded to SILEX to hold; hoping the weather would improve. Once established in holding we were informed that BUR Runway 33 was closed; so we proceeded to our filed alternate. The information on the release showed that we could use BUR Runway 08 at MLW of 287.4; including the MEL so we proceeded to BUR. Our landing performance data indicated Runway 08 was not valid. Some MEL's restrict landing at several short runway airports (BUR; SNA) and I think this one should be evaluated for that limitation. Ensure the release landing data is consistent with computation/software we use in the aircraft.

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.