|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : bur|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||common carrier : air carrier|
|Make Model Name||Medium Large Transport, Low Wing, 2 Turbojet Eng|
|Navigation In Use||Other|
|Flight Phase||landing other|
|Route In Use||approach : visual|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Experience||flight time last 90 days : 230|
flight time total : 8500
flight time type : 2000
|Affiliation||company : air carrier|
|Function||flight crew : first officer|
|Qualification||pilot : instrument|
pilot : commercial
|Anomaly||incursion : runway|
non adherence : far
other anomaly other
|Independent Detector||other flight crewa|
|Resolutory Action||none taken : detected after the fact|
|Air Traffic Incident||other|
I carefully reviewed each dispatch release and WX printout prior to each pushback. There were no unusual comments on the release, and the WX printout showed only 2 NOTAMS for phx (not relevant for this flight), and nothing else for NOTAMS. In range to bur, the first officer, who was the PNF, left radio 1 in order to copy the bur ATIS. He filled out the landing data card. I planned on a visual approach to runway 15. Upon handoff to bur approach, the controller asked which runway we would like, and we replied runway 15. I made a normal flaps 40 degrees approach to runway 15. At 100' RA, I noticed construction vehicles off the end of the runway (off departure end). I T/ded, lowered the nose to the runway, and was alarmed at noticing that the construction vehicles were on the runway and that the last 1/3 of the runway was all torn up. As it turned out, I had only 4500' of runway available for landing. The dispatch release said nothing. The WX and NOTAM printout said nothing (although bur did issue a NOTAM). The first officer only listened to the WX portion of the ATIS (the runway closure was being broadcast on the ATIS). The approach controller said nothing although we were probably the only air carrier to choose runway 15. For all intent and purposes, I crashed. I got lucky, I get to fill out an ASRS report. Callback conversation with reporter revealed the following: this air carrier gets their WX and dispatch information from commercial flight planning service. Code is placed at top of release which tells computer which NOTAMS to put on dispatch release. In this case wrong code was used and bur NOTAMS not issued. Reporter talked to chief pilot and advised all pilots should be advised what this code at top of release is so they will know if they have proper NOTAMS. Reported he was very light and with 5000' runway available, no trouble stopping, although may not have met t-category requirement. Said controllers were not concerned since runway not notamed closed to any aircraft, but just notamed to length available.
Original NASA ASRS Text
Title: ACR MLG LNDG ON RWY WITH INSUFFICIENT LENGTH TO MEET FEDERAL AVIATION REG REQUIREMENT.
Narrative: I CAREFULLY REVIEWED EACH DISPATCH RELEASE AND WX PRINTOUT PRIOR TO EACH PUSHBACK. THERE WERE NO UNUSUAL COMMENTS ON THE RELEASE, AND THE WX PRINTOUT SHOWED ONLY 2 NOTAMS FOR PHX (NOT RELEVANT FOR THIS FLT), AND NOTHING ELSE FOR NOTAMS. IN RANGE TO BUR, THE F/O, WHO WAS THE PNF, LEFT RADIO 1 IN ORDER TO COPY THE BUR ATIS. HE FILLED OUT THE LNDG DATA CARD. I PLANNED ON A VISUAL APCH TO RWY 15. UPON HDOF TO BUR APCH, THE CTLR ASKED WHICH RWY WE WOULD LIKE, AND WE REPLIED RWY 15. I MADE A NORMAL FLAPS 40 DEGS APCH TO RWY 15. AT 100' RA, I NOTICED CONSTRUCTION VEHICLES OFF THE END OF THE RWY (OFF DEP END). I T/DED, LOWERED THE NOSE TO THE RWY, AND WAS ALARMED AT NOTICING THAT THE CONSTRUCTION VEHICLES WERE ON THE RWY AND THAT THE LAST 1/3 OF THE RWY WAS ALL TORN UP. AS IT TURNED OUT, I HAD ONLY 4500' OF RWY AVAILABLE FOR LNDG. THE DISPATCH RELEASE SAID NOTHING. THE WX AND NOTAM PRINTOUT SAID NOTHING (ALTHOUGH BUR DID ISSUE A NOTAM). THE F/O ONLY LISTENED TO THE WX PORTION OF THE ATIS (THE RWY CLOSURE WAS BEING BROADCAST ON THE ATIS). THE APCH CTLR SAID NOTHING ALTHOUGH WE WERE PROBABLY THE ONLY ACR TO CHOOSE RWY 15. FOR ALL INTENT AND PURPOSES, I CRASHED. I GOT LUCKY, I GET TO FILL OUT AN ASRS RPT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: THIS ACR GETS THEIR WX AND DISPATCH INFO FROM COMMERCIAL FLT PLANNING SVC. CODE IS PLACED AT TOP OF RELEASE WHICH TELLS COMPUTER WHICH NOTAMS TO PUT ON DISPATCH RELEASE. IN THIS CASE WRONG CODE WAS USED AND BUR NOTAMS NOT ISSUED. RPTR TALKED TO CHIEF PLT AND ADVISED ALL PLTS SHOULD BE ADVISED WHAT THIS CODE AT TOP OF RELEASE IS SO THEY WILL KNOW IF THEY HAVE PROPER NOTAMS. RPTED HE WAS VERY LIGHT AND WITH 5000' RWY AVAILABLE, NO TROUBLE STOPPING, ALTHOUGH MAY NOT HAVE MET T-CATEGORY REQUIREMENT. SAID CTLRS WERE NOT CONCERNED SINCE RWY NOT NOTAMED CLOSED TO ANY ACFT, BUT JUST NOTAMED TO LENGTH AVAILABLE.
Data retrieved from NASA's ASRS site as of August 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.