Narrative:

The same exact sequence of events occurred on previous trip to san. Runway 27 was not in use and no NOTAM regarding shortened length of runway 27. Ground control issued clearance to 'taxi to runway 27 via bravo.' approaching the end of taxiway bravo; more than one half the normal throat from bravo onto the runway is obstructed with flashing red barricade. New right edge of taxiway as you approach hold short line is marked and blue taxiway edge 'pylons' form a definitive boundary and force aircraft onto runway 27 approximately 500 ft from where we normally align aircraft for departure (by the blast fence). Airport diagram is inaccurate. Chart appears to show taxiway B1 coming from the west and being the most western part of pavement. Taxiway B1 is also marked on the left side of taxiway bravo and at the beginning of the large throat normally available. This distance equates to 8;550 ft of runway. The full distance of runway 27 in the pwb data is 9;401 ft. The difference is 551 ft. Without a NOTAM indicating runway 27 east of B1 is closed and with ground issuing a clearance to taxi to runway 27 via bravo; the crew has no knowledge that the performance they have derived for runway 27 (9;401 ft) is wrong. Performance must be calculated from B1 based on the current un-notamed closure. The danger is that a crew looking at any stopping margin less than 1;051 ft will in fact have less than 500 ft of stopping margin on takeoff. San is a short runway. All indications are that runway 27 should be selected as normal when deriving performance. Crews may also misunderstand that any runway shortening is already accounted for in the performance data once they visually see that normal access to the runway is obstructed. Performance data does not account for an unidentified shortening. I recommend a note be immediately placed on weather packet and more than one half the normal throat from bravo onto the runway is obstructed release to notify crews to request performance data for runway 27/B1 to avoid this trap. Also recommend san airport ops put a NOTAM out that the first 551 of runway 27 not available for takeoff. Be more than happy to discuss. It is very difficult to explain it all in a report.

Google
 

Original NASA ASRS Text

Title: B737 NG Captain reported the lack of NOTAMs regarding the shortened length of Runway 27 in SAN.

Narrative: The same exact sequence of events occurred on previous trip to SAN. Runway 27 was not in use and no NOTAM regarding shortened length of Runway 27. Ground Control issued clearance to 'Taxi to Runway 27 via Bravo.' Approaching the end of Taxiway Bravo; more than one half the normal throat from Bravo onto the runway is obstructed with flashing red barricade. New right edge of taxiway as you approach hold short line is marked and blue taxiway edge 'pylons' form a definitive boundary and force aircraft onto Runway 27 approximately 500 ft from where we normally align aircraft for departure (by the blast fence). Airport diagram is inaccurate. Chart appears to show Taxiway B1 coming from the west and being the most western part of pavement. Taxiway B1 is also marked on the left side of Taxiway Bravo and at the beginning of the large throat normally available. This distance equates to 8;550 ft of runway. The full distance of Runway 27 in the PWB data is 9;401 ft. The difference is 551 ft. Without a NOTAM indicating Runway 27 east of B1 is closed and with Ground issuing a clearance to taxi to Runway 27 via Bravo; the Crew has no knowledge that the performance they have derived for Runway 27 (9;401 ft) is wrong. Performance must be calculated from B1 based on the current un-NOTAMed closure. The danger is that a Crew looking at any stopping margin less than 1;051 ft will in fact have less than 500 ft of stopping margin on takeoff. SAN is a short runway. All indications are that Runway 27 should be selected as normal when deriving performance. Crews may also misunderstand that any runway shortening is already accounted for in the performance data once they visually see that normal access to the runway is obstructed. Performance data does not account for an unidentified shortening. I recommend a note be immediately placed on weather packet and more than one half the normal throat from Bravo onto the runway is obstructed Release to notify Crews to request performance data for Runway 27/B1 to avoid this trap. Also recommend SAN Airport Ops put a NOTAM out that the first 551 of Runway 27 not available for takeoff. Be more than happy to discuss. It is very difficult to explain it all in a report.

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.