Narrative:

The flight in question was being flown as a charter for the military. I and both my first officer's reviewed the NOTAMS pertaining to ZZZ. We took note of the fact that 1 of the 2 runways was closed; but for some reason; did not see that the open runway had 1731 ft closed at the far end. This information was not given to us by our dispatcher; and was not noted on any of the performance data generated by dispatch. The shortened runway was also not noted in the ATIS information at ZZZ. According to the correct performance data; the aircraft was able to land and come to a full stop within 48% of the available length of the shortened runway; which we accomplished without incident. We became aware of the problem after the aircraft blocked in; but prior to taking off on the next leg. The takeoff was accomplished with correct performance data for the shortened runway. This incident did not result in any serious incident; but I believe had the potential to have been worse; given the fact that the closure was at the departure end of the runway and not the approach end. Dispatch should do a more careful analysis of airports we are not familiar with; and I should also demand the same from myself and my crew. I have been informed that the company who generates our performance information needs to have a request for the new data. I would like to recommend that procedure be changed so that critical data such as that is transmitted automatically in conjunction with the release of the NOTAM package for the airport.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767-300 LANDS ON RWY SHORTENED BY NOTAM USING PERFORMANCE DATA FOR THE FULL LENGTH.

Narrative: THE FLT IN QUESTION WAS BEING FLOWN AS A CHARTER FOR THE MIL. I AND BOTH MY FO'S REVIEWED THE NOTAMS PERTAINING TO ZZZ. WE TOOK NOTE OF THE FACT THAT 1 OF THE 2 RWYS WAS CLOSED; BUT FOR SOME REASON; DID NOT SEE THAT THE OPEN RWY HAD 1731 FT CLOSED AT THE FAR END. THIS INFO WAS NOT GIVEN TO US BY OUR DISPATCHER; AND WAS NOT NOTED ON ANY OF THE PERFORMANCE DATA GENERATED BY DISPATCH. THE SHORTENED RWY WAS ALSO NOT NOTED IN THE ATIS INFO AT ZZZ. ACCORDING TO THE CORRECT PERFORMANCE DATA; THE ACFT WAS ABLE TO LAND AND COME TO A FULL STOP WITHIN 48% OF THE AVAILABLE LENGTH OF THE SHORTENED RWY; WHICH WE ACCOMPLISHED WITHOUT INCIDENT. WE BECAME AWARE OF THE PROB AFTER THE ACFT BLOCKED IN; BUT PRIOR TO TAKING OFF ON THE NEXT LEG. THE TKOF WAS ACCOMPLISHED WITH CORRECT PERFORMANCE DATA FOR THE SHORTENED RWY. THIS INCIDENT DID NOT RESULT IN ANY SERIOUS INCIDENT; BUT I BELIEVE HAD THE POTENTIAL TO HAVE BEEN WORSE; GIVEN THE FACT THAT THE CLOSURE WAS AT THE DEP END OF THE RWY AND NOT THE APCH END. DISPATCH SHOULD DO A MORE CAREFUL ANALYSIS OF ARPTS WE ARE NOT FAMILIAR WITH; AND I SHOULD ALSO DEMAND THE SAME FROM MYSELF AND MY CREW. I HAVE BEEN INFORMED THAT THE COMPANY WHO GENERATES OUR PERFORMANCE INFO NEEDS TO HAVE A REQUEST FOR THE NEW DATA. I WOULD LIKE TO RECOMMEND THAT PROC BE CHANGED SO THAT CRITICAL DATA SUCH AS THAT IS XMITTED AUTOMATICALLY IN CONJUNCTION WITH THE RELEASE OF THE NOTAM PACKAGE FOR THE ARPT.

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