37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 162875 |
Time | |
Date | 199011 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : rdu |
State Reference | NC |
Altitude | agl bound lower : 0 agl bound upper : 600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | descent : approach landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : commercial pilot : instrument pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 2400 flight time type : 800 |
ASRS Report | 162875 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | other anomaly other other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
Normal visibility approach to rdu. First time at airport for PIC (sic/PF had been to rdu). I was PNF. On initial call to final approach controller requested runway 32. Aircraft requires airport analysis; had checked and runway 32 was included. Airport diagram on airport page indicated that 32 xed 23L ended on ramp. Wind reported 300/9 (4000' plus available). Runway 32 landing was favored for wind and rollout to ramp. Approach controller approved runway 32. What he didn't tell us was that runway 32 was only 3200' available due to the elimination of the crossing at the end of runway 23L. We were cleared for a visibility approach to 32 and turned over to tower. Tower cleared us to land, #2 behind a helicopter. On short final requested rollout to the end. Was told 'negative' and the first officer flying asked me something to the effect that 'should we continue.' first officer landed on the end of the runway (approximately 5 yds past threshold) and applied hard reverse and brakes. Cleared runway to right. First officer had heard call on 100-200' final regarding actual length of runway 32. Asked if we should continue and then put it as close to the approach end of 32 as possible. After requesting rollout to the end (expecting approval), I was listening to the ctrl, the first officer, and cleaning up the before landing checklist. I missed the reference to runway 32 limited length, and my response to the first officer (PF) was 'continue to land.' after landing asked controller about the runway 32 exits requested clarification on the instruction 'unable to rollout to the end.' controller confirmed that rollout to the end was available, but that the end of the runway was prior taxiing runway 23L. PF then told me about actual length available.
Original NASA ASRS Text
Title: PIC OF LTT WAS UNAWARE THAT RWY LENGTH OF RWY 32 AT RDU WAS RESTRICTED (NOT TO CROSS 5R/23L). SOMEHOW FO FLYING THE APCH AND LNDG UNDERSTOOD THE RWY WAS RESTRICTED IN LENGTH AND SET THE ACFT DOWN ON THE VERY END AND BRAKED HEAVILY TO COME TO A STOP.
Narrative: NORMAL VIS APCH TO RDU. FIRST TIME AT ARPT FOR PIC (SIC/PF HAD BEEN TO RDU). I WAS PNF. ON INITIAL CALL TO FINAL APCH CTLR REQUESTED RWY 32. ACFT REQUIRES ARPT ANALYSIS; HAD CHKED AND RWY 32 WAS INCLUDED. ARPT DIAGRAM ON ARPT PAGE INDICATED THAT 32 XED 23L ENDED ON RAMP. WIND RPTED 300/9 (4000' PLUS AVAILABLE). RWY 32 LNDG WAS FAVORED FOR WIND AND ROLLOUT TO RAMP. APCH CTLR APPROVED RWY 32. WHAT HE DIDN'T TELL US WAS THAT RWY 32 WAS ONLY 3200' AVAILABLE DUE TO THE ELIMINATION OF THE XING AT THE END OF RWY 23L. WE WERE CLRED FOR A VIS APCH TO 32 AND TURNED OVER TO TWR. TWR CLRED US TO LAND, #2 BEHIND A HELI. ON SHORT FINAL REQUESTED ROLLOUT TO THE END. WAS TOLD 'NEGATIVE' AND THE F/O FLYING ASKED ME SOMETHING TO THE EFFECT THAT 'SHOULD WE CONTINUE.' F/O LANDED ON THE END OF THE RWY (APPROX 5 YDS PAST THRESHOLD) AND APPLIED HARD REVERSE AND BRAKES. CLRED RWY TO R. F/O HAD HEARD CALL ON 100-200' FINAL REGARDING ACTUAL LENGTH OF RWY 32. ASKED IF WE SHOULD CONTINUE AND THEN PUT IT AS CLOSE TO THE APCH END OF 32 AS POSSIBLE. AFTER REQUESTING ROLLOUT TO THE END (EXPECTING APPROVAL), I WAS LISTENING TO THE CTRL, THE F/O, AND CLEANING UP THE BEFORE LNDG CHKLIST. I MISSED THE REFERENCE TO RWY 32 LIMITED LENGTH, AND MY RESPONSE TO THE F/O (PF) WAS 'CONTINUE TO LAND.' AFTER LNDG ASKED CTLR ABOUT THE RWY 32 EXITS REQUESTED CLARIFICATION ON THE INSTRUCTION 'UNABLE TO ROLLOUT TO THE END.' CTLR CONFIRMED THAT ROLLOUT TO THE END WAS AVAILABLE, BUT THAT THE END OF THE RWY WAS PRIOR TAXIING RWY 23L. PF THEN TOLD ME ABOUT ACTUAL LENGTH AVAILABLE.
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.