37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 319247 |
Time | |
Date | 199510 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : stl |
State Reference | MO |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Jetstream 32 |
Operating Under FAR Part | Part 135 |
Flight Phase | ground other : taxi landing other |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | DC-9 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : takeoff other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 245 flight time total : 2075 flight time type : 305 |
ASRS Report | 319247 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 8200 flight time type : 5000 |
ASRS Report | 319106 |
Events | |
Anomaly | incursion : runway non adherence : published procedure non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact none taken : insufficient time other |
Consequence | faa : assigned or threatened penalties faa : investigated faa : reviewed incident with flight crew |
Miss Distance | horizontal : 6500 vertical : 0 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : unspecified |
Airport | other physical facility |
Narrative:
I was the first officer (PNF) on a visual approach to land on st louis lambert's runway 24 and hold short of runway 30L. This was completed without incident. However, on the rollout we received the following instructions: 'xyz, roll right on through runway 30R, left on taxiway P' (this is a quote given to us by the tower over the phone after the occurrence). I (the PNF) read back: 'cleared to cross, left of taxiway P,' and we proceeded to cross runway 30L. Immediately after crossing we were informed that we were not cleared across runway 30L. The captain immediately requested that the tapes be 'pulled' and a phone number be provided for discussion -- ie, we were both convinced that we had been cleared across runway 30L. Ironically, I believe the genesis of this problem was caused by we the crew doing a better than average job of holding short -- which we did. When the controller saw us coming up short of where he intended on turning us off the runway, his remedy was to issue the fateful 'roll right on through runway 30R' phraseology -- which will be talked about more thoroughly later in this report. As a side note, I'm a fairly new first officer with 305 hours in type. I believe the instructions issued to us on rollout were exceptionally misleading. There appear to be no operational restrs regarding these 2 runways. Finally, there was only one intersection along the entire length of runway 24 that required a clearance to cross -- that being runway 30L. With hindsight and time to examine the instructions given to us, one can see what the controller intended. But time is not a plentiful commodity at st louis, particularly during hold short operations.
Original NASA ASRS Text
Title: RWY INCURSION. REVISED HOLD SHORT CLRNC INTERP NOT QUESTIONED. AMENDED CLRNC ISSUED DURING LNDG ROLLOUT. FLC ATC REVIEW PERFORMED.
Narrative: I WAS THE FO (PNF) ON A VISUAL APCH TO LAND ON ST LOUIS LAMBERT'S RWY 24 AND HOLD SHORT OF RWY 30L. THIS WAS COMPLETED WITHOUT INCIDENT. HOWEVER, ON THE ROLLOUT WE RECEIVED THE FOLLOWING INSTRUCTIONS: 'XYZ, ROLL RIGHT ON THROUGH RWY 30R, L ON TXWY P' (THIS IS A QUOTE GIVEN TO US BY THE TWR OVER THE PHONE AFTER THE OCCURRENCE). I (THE PNF) READ BACK: 'CLRED TO CROSS, L OF TXWY P,' AND WE PROCEEDED TO CROSS RWY 30L. IMMEDIATELY AFTER XING WE WERE INFORMED THAT WE WERE NOT CLRED ACROSS RWY 30L. THE CAPT IMMEDIATELY REQUESTED THAT THE TAPES BE 'PULLED' AND A PHONE NUMBER BE PROVIDED FOR DISCUSSION -- IE, WE WERE BOTH CONVINCED THAT WE HAD BEEN CLRED ACROSS RWY 30L. IRONICALLY, I BELIEVE THE GENESIS OF THIS PROB WAS CAUSED BY WE THE CREW DOING A BETTER THAN AVERAGE JOB OF HOLDING SHORT -- WHICH WE DID. WHEN THE CTLR SAW US COMING UP SHORT OF WHERE HE INTENDED ON TURNING US OFF THE RWY, HIS REMEDY WAS TO ISSUE THE FATEFUL 'ROLL RIGHT ON THROUGH RWY 30R' PHRASEOLOGY -- WHICH WILL BE TALKED ABOUT MORE THOROUGHLY LATER IN THIS RPT. AS A SIDE NOTE, I'M A FAIRLY NEW FO WITH 305 HRS IN TYPE. I BELIEVE THE INSTRUCTIONS ISSUED TO US ON ROLLOUT WERE EXCEPTIONALLY MISLEADING. THERE APPEAR TO BE NO OPERATIONAL RESTRS REGARDING THESE 2 RWYS. FINALLY, THERE WAS ONLY ONE INTXN ALONG THE ENTIRE LENGTH OF RWY 24 THAT REQUIRED A CLRNC TO CROSS -- THAT BEING RWY 30L. WITH HINDSIGHT AND TIME TO EXAMINE THE INSTRUCTIONS GIVEN TO US, ONE CAN SEE WHAT THE CTLR INTENDED. BUT TIME IS NOT A PLENTIFUL COMMODITY AT ST LOUIS, PARTICULARLY DURING HOLD SHORT OPS.
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.