Narrative:

There are some minor inconsistencies with the takeoff data at mht we experienced today, that I am not completely comfortable with. For runway 17/35: 1) 10-9 page shows an under construction runway 17/35 that is 7001 ft long effective date oct/fri/02. 2) mht ATIS showed 7150 ft available for departure runway 35. 3) opc data and dispatch showed an open runway 35 7100 ft long for departure. 4) FMC database december through january/03, operation program recognized runway 35 for both arrs and departures. Additionally, the 10-9 page does not accurately depict open txwys 'east' and 'a' leading to runway 35. We safely met all ATOG requirements for runway 35, but it would have been nice to have an accurate 10-9 page for xchk.

Google
 

Original NASA ASRS Text

Title: B737 FLC ENCOUNTERS TXWY AND RWY DATA DISPARITY BTWN ACTUAL AND CHARTED INFO AT MHT.

Narrative: THERE ARE SOME MINOR INCONSISTENCIES WITH THE TKOF DATA AT MHT WE EXPERIENCED TODAY, THAT I AM NOT COMPLETELY COMFORTABLE WITH. FOR RWY 17/35: 1) 10-9 PAGE SHOWS AN UNDER CONSTRUCTION RWY 17/35 THAT IS 7001 FT LONG EFFECTIVE DATE OCT/FRI/02. 2) MHT ATIS SHOWED 7150 FT AVAILABLE FOR DEP RWY 35. 3) OPC DATA AND DISPATCH SHOWED AN OPEN RWY 35 7100 FT LONG FOR DEP. 4) FMC DATABASE DECEMBER THROUGH JANUARY/03, OP PROGRAM RECOGNIZED RWY 35 FOR BOTH ARRS AND DEPS. ADDITIONALLY, THE 10-9 PAGE DOES NOT ACCURATELY DEPICT OPEN TXWYS 'E' AND 'A' LEADING TO RWY 35. WE SAFELY MET ALL ATOG REQUIREMENTS FOR RWY 35, BUT IT WOULD HAVE BEEN NICE TO HAVE AN ACCURATE 10-9 PAGE FOR XCHK.

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