Narrative:

During normal preflight planning for departure from dsm; the desired runway was discussed. Runway 13 was advertised but with near calm winds a runway 31 intersection departure at D2 was considered and determined to offer acceptable performance. Full length runway 31 was unavailable due to construction. The [efb] indicated that at the runway 31 intersection D2 had 8;600 ft available; just 500 ft less than the full length of 9;100 ft. We agreed on this plan but; when we requested this runway; ground control granted our request but indicated that there was only 7;300 ft available from D2; a full 1;300 ft less than the [efb] indicated. With this newfound conflicting data and potentially unreliable performance data; a runway 13 full length departure was requested. After a normal departure; we double checked the information in the [efb] and the performance from ACARS and both incorrectly indicated the available distance from D2 was 8;600 ft. In discussing this errant information; we determined that recent construction at the airport had reconfigured some of the intersecting taxiways but these changes have not been integrated into the performance packages. Dispatch (ground ops) and flight operations performance should review all airports; and especially recently acquired cities; for accuracy of all runway data. This problem may be more pronounced at our newer and lesser utilized airports that were added [recently].

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 Captain departing DSM discovers that the runway available from Taxiway D2 provided by the company is not correct.

Narrative: During normal preflight planning for departure from DSM; the desired runway was discussed. Runway 13 was advertised but with near calm winds a Runway 31 intersection departure at D2 was considered and determined to offer acceptable performance. Full length Runway 31 was unavailable due to construction. The [EFB] indicated that at the Runway 31 intersection D2 had 8;600 FT available; just 500 FT less than the full length of 9;100 FT. We agreed on this plan but; when we requested this runway; Ground Control granted our request but indicated that there was only 7;300 FT available from D2; a full 1;300 FT less than the [EFB] indicated. With this newfound conflicting data and potentially unreliable performance data; a Runway 13 full length departure was requested. After a normal departure; we double checked the information in the [EFB] and the performance from ACARS and BOTH incorrectly indicated the available distance from D2 was 8;600 FT. In discussing this errant information; we determined that recent construction at the airport had reconfigured some of the intersecting taxiways but these changes have not been integrated into the performance packages. Dispatch (Ground Ops) and Flight Operations Performance should review all airports; and especially recently acquired cities; for accuracy of all runway data. This problem may be more pronounced at our newer and lesser utilized airports that were added [recently].

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