37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 290665 |
Time | |
Date | 199412 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : cle |
State Reference | OH |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | SA-227 AC Metro III |
Operating Under FAR Part | Part 135 |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : cfi pilot : atp pilot : commercial |
Experience | flight time last 90 days : 170 flight time total : 6500 flight time type : 2600 |
ASRS Report | 290665 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | incursion : runway non adherence : clearance |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
The WX was bad with rain and fog and reduced visibility. This was only my second time at night being in cle. During my initial call to ground frequency to call for taxi for departure, I informed ground that I was unfamiliar with cle, and with all the construction, I asked for progressive instructions to be sure I didn't make any mistakes. My first officer was new and he had the ground layout open and was trying to follow our progress. The controller told me to proceed straight ahead and then jog left. I was actually closer to the right taxiway than I thought so I thought it was one more taxiway, then left. I was relying on his instruction rather than really locking closely at the signs (which I still think are confusing). I was 1/2 way onto an active runway when I noticed centerline lights. I immediately stopped and I kept hearing the controller call air carrier X. Air carrier X is the call sign for air carrier which used to be the carrier that flew into cle. I corrected the controller and needed instruction. He told me to continue down the runway and exit at the next taxiway. There were a few seconds there where communications were hindered due to the wrong call sign used. We exited the active runway without incident. I asked the ground controller if there was any problem and he said no, not at all. We continued without incident. I feel that all entrances to runways should have flashing yellow lights like there are in pittsburgh. At night in bad WX with low visibility in the SA227, it is very difficult to see. I think the bad WX in cle and not looking forward to a bumpy 1 1/2 hour flight back to ind where a minimums approach was going to take place also occupied my mind. I would like to say I did need to rely on the controller for specific instructions because I did feel uncomfortable. The controller was very nice about it, but there was a breakdown in communication in part due to the fact of the wrong call sign being used. This whole problem would never have happened if cle had flashing yellow runway identifier marking lights. They really do help!
Original NASA ASRS Text
Title: COMMUTER ACFT HAS RWY INCURSION. CTLR USING WRONG CALL SIGN.
Narrative: THE WX WAS BAD WITH RAIN AND FOG AND REDUCED VISIBILITY. THIS WAS ONLY MY SECOND TIME AT NIGHT BEING IN CLE. DURING MY INITIAL CALL TO GND FREQ TO CALL FOR TAXI FOR DEP, I INFORMED GND THAT I WAS UNFAMILIAR WITH CLE, AND WITH ALL THE CONSTRUCTION, I ASKED FOR PROGRESSIVE INSTRUCTIONS TO BE SURE I DIDN'T MAKE ANY MISTAKES. MY FO WAS NEW AND HE HAD THE GND LAYOUT OPEN AND WAS TRYING TO FOLLOW OUR PROGRESS. THE CTLR TOLD ME TO PROCEED STRAIGHT AHEAD AND THEN JOG L. I WAS ACTUALLY CLOSER TO THE R TXWY THAN I THOUGHT SO I THOUGHT IT WAS ONE MORE TXWY, THEN L. I WAS RELYING ON HIS INSTRUCTION RATHER THAN REALLY LOCKING CLOSELY AT THE SIGNS (WHICH I STILL THINK ARE CONFUSING). I WAS 1/2 WAY ONTO AN ACTIVE RWY WHEN I NOTICED CTRLINE LIGHTS. I IMMEDIATELY STOPPED AND I KEPT HEARING THE CTLR CALL ACR X. ACR X IS THE CALL SIGN FOR ACR WHICH USED TO BE THE CARRIER THAT FLEW INTO CLE. I CORRECTED THE CTLR AND NEEDED INSTRUCTION. HE TOLD ME TO CONTINUE DOWN THE RWY AND EXIT AT THE NEXT TXWY. THERE WERE A FEW SECONDS THERE WHERE COMS WERE HINDERED DUE TO THE WRONG CALL SIGN USED. WE EXITED THE ACTIVE RWY WITHOUT INCIDENT. I ASKED THE GND CTLR IF THERE WAS ANY PROB AND HE SAID NO, NOT AT ALL. WE CONTINUED WITHOUT INCIDENT. I FEEL THAT ALL ENTRANCES TO RWYS SHOULD HAVE FLASHING YELLOW LIGHTS LIKE THERE ARE IN PITTSBURGH. AT NIGHT IN BAD WX WITH LOW VISIBILITY IN THE SA227, IT IS VERY DIFFICULT TO SEE. I THINK THE BAD WX IN CLE AND NOT LOOKING FORWARD TO A BUMPY 1 1/2 HR FLT BACK TO IND WHERE A MINIMUMS APCH WAS GOING TO TAKE PLACE ALSO OCCUPIED MY MIND. I WOULD LIKE TO SAY I DID NEED TO RELY ON THE CTLR FOR SPECIFIC INSTRUCTIONS BECAUSE I DID FEEL UNCOMFORTABLE. THE CTLR WAS VERY NICE ABOUT IT, BUT THERE WAS A BREAKDOWN IN COM IN PART DUE TO THE FACT OF THE WRONG CALL SIGN BEING USED. THIS WHOLE PROB WOULD NEVER HAVE HAPPENED IF CLE HAD FLASHING YELLOW RWY IDENTIFIER MARKING LIGHTS. THEY REALLY DO HELP!
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.