37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 561584 |
Time | |
Date | 200210 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bna.airport |
State Reference | TN |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bna.tower |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : holding |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 150 flight time total : 3700 flight time type : 350 |
ASRS Report | 561584 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 230 flight time total : 24000 flight time type : 1000 |
ASRS Report | 561734 |
Events | |
Anomaly | incursion : runway non adherence : clearance non adherence : company policies non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew other other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Environmental Factor Airport ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Situations | |
ATC Facility | procedure or policy : bna.tower |
Narrative:
Runway incursion. While taxiing to runway 20C, I called 'in sequence for runway 20C' (there was an aircraft Y jet holding short, off to the side). My transmission was blocked so I repeated it again. Tower immediately responded and asked if we could accept an 'immediate takeoff.' I responded 'affirmative' and tower read back a call sign that we thought was our call sign -- it sounded like our call sign -- and continued to give a heading and DME clearance and clearance to take off. He also said that traffic was on a 4 mi final at the beginning of that transmission. Both the captain and I saw the traffic (it looked like it was for runway 20C but actually was runway 20R). I read back the takeoff clearance instructions followed by 'cleared for takeoff runway 20C company number.' we proceeded on the runway and aircraft Y called out on frequency and asked if we were really cleared. Tower came back and told us we were in error but cleared us anyway at that point. We elected to clear the runway, collect ourselves, and see what we did wrong. A few moments later, we were cleared for takeoff. Tower said not to worry about it -- they were taking no action. We all agreed the radios were very busy (all 3 runways had airplanes ready for takeoff). Expectation theory set us up for a fall. Everything seemed normal and fit into place. Aircraft Y saved us because I am not sure tower saw us in those few seconds. I do not know how I would have done this differently other than reading everything back and waiting for a correction from tower before taking the runway. This is very frustrating because I can easily see this happening again. Maybe I should have added our call sign to our 'affirmative' call. I don't remember if I did or not. Maybe be more careful with multiple runways. Supplemental information from acn 561734: immediately after the first officer's call, the tower responded with an 'expedite takeoff clearance, traffic on a 4 mi final' and started with what I thought was our call sign. Turns out there was an aircraft #bdxc on runway 20L. We were company #bdxh. If you clip the first and last with too many radios at the same time, and 3 runways with traffic on every one of them, then trouble brews. I asked the controller how much paperwork we generated and 'none' was his reply. It's the same stuff, different day and crew. What's the cure? Maybe another frequency for runway 20L. We can keep an eye on each other on the center and right, but I don't have a clue that maybe someone with a similar call sign is on the right. What about positive traffic control lights. Green you cross the hold line, red you hold short. I will try my hardest to not make the same mistake twice. What scares me the most is knowing it was such a perfect trap, that on any day I might fall for it again.
Original NASA ASRS Text
Title: RWY INCURSION DURING A CALL SIGN MIX-UP DURING A 3 RWY OP AT BNA, TN.
Narrative: RWY INCURSION. WHILE TAXIING TO RWY 20C, I CALLED 'IN SEQUENCE FOR RWY 20C' (THERE WAS AN ACFT Y JET HOLDING SHORT, OFF TO THE SIDE). MY XMISSION WAS BLOCKED SO I REPEATED IT AGAIN. TWR IMMEDIATELY RESPONDED AND ASKED IF WE COULD ACCEPT AN 'IMMEDIATE TKOF.' I RESPONDED 'AFFIRMATIVE' AND TWR READ BACK A CALL SIGN THAT WE THOUGHT WAS OUR CALL SIGN -- IT SOUNDED LIKE OUR CALL SIGN -- AND CONTINUED TO GIVE A HDG AND DME CLRNC AND CLRNC TO TAKE OFF. HE ALSO SAID THAT TFC WAS ON A 4 MI FINAL AT THE BEGINNING OF THAT XMISSION. BOTH THE CAPT AND I SAW THE TFC (IT LOOKED LIKE IT WAS FOR RWY 20C BUT ACTUALLY WAS RWY 20R). I READ BACK THE TKOF CLRNC INSTRUCTIONS FOLLOWED BY 'CLRED FOR TKOF RWY 20C COMPANY NUMBER.' WE PROCEEDED ON THE RWY AND ACFT Y CALLED OUT ON FREQ AND ASKED IF WE WERE REALLY CLRED. TWR CAME BACK AND TOLD US WE WERE IN ERROR BUT CLRED US ANYWAY AT THAT POINT. WE ELECTED TO CLR THE RWY, COLLECT OURSELVES, AND SEE WHAT WE DID WRONG. A FEW MOMENTS LATER, WE WERE CLRED FOR TKOF. TWR SAID NOT TO WORRY ABOUT IT -- THEY WERE TAKING NO ACTION. WE ALL AGREED THE RADIOS WERE VERY BUSY (ALL 3 RWYS HAD AIRPLANES READY FOR TKOF). EXPECTATION THEORY SET US UP FOR A FALL. EVERYTHING SEEMED NORMAL AND FIT INTO PLACE. ACFT Y SAVED US BECAUSE I AM NOT SURE TWR SAW US IN THOSE FEW SECONDS. I DO NOT KNOW HOW I WOULD HAVE DONE THIS DIFFERENTLY OTHER THAN READING EVERYTHING BACK AND WAITING FOR A CORRECTION FROM TWR BEFORE TAKING THE RWY. THIS IS VERY FRUSTRATING BECAUSE I CAN EASILY SEE THIS HAPPENING AGAIN. MAYBE I SHOULD HAVE ADDED OUR CALL SIGN TO OUR 'AFFIRMATIVE' CALL. I DON'T REMEMBER IF I DID OR NOT. MAYBE BE MORE CAREFUL WITH MULTIPLE RWYS. SUPPLEMENTAL INFO FROM ACN 561734: IMMEDIATELY AFTER THE FO'S CALL, THE TWR RESPONDED WITH AN 'EXPEDITE TKOF CLRNC, TFC ON A 4 MI FINAL' AND STARTED WITH WHAT I THOUGHT WAS OUR CALL SIGN. TURNS OUT THERE WAS AN ACFT #BDXC ON RWY 20L. WE WERE COMPANY #BDXH. IF YOU CLIP THE FIRST AND LAST WITH TOO MANY RADIOS AT THE SAME TIME, AND 3 RWYS WITH TFC ON EVERY ONE OF THEM, THEN TROUBLE BREWS. I ASKED THE CTLR HOW MUCH PAPERWORK WE GENERATED AND 'NONE' WAS HIS REPLY. IT'S THE SAME STUFF, DIFFERENT DAY AND CREW. WHAT'S THE CURE? MAYBE ANOTHER FREQ FOR RWY 20L. WE CAN KEEP AN EYE ON EACH OTHER ON THE CTR AND R, BUT I DON'T HAVE A CLUE THAT MAYBE SOMEONE WITH A SIMILAR CALL SIGN IS ON THE R. WHAT ABOUT POSITIVE TFC CTL LIGHTS. GREEN YOU CROSS THE HOLD LINE, RED YOU HOLD SHORT. I WILL TRY MY HARDEST TO NOT MAKE THE SAME MISTAKE TWICE. WHAT SCARES ME THE MOST IS KNOWING IT WAS SUCH A PERFECT TRAP, THAT ON ANY DAY I MIGHT FALL FOR IT AGAIN.
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.