37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 459037 |
Time | |
Date | 199912 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : cmh.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : holding ground : position and hold |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : cmh.tower |
Operator | general aviation : corporate |
Make Model Name | British Aerospace Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : position and hold ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 200 flight time total : 2900 flight time type : 200 |
ASRS Report | 459037 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : far non adherence : clearance other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued alert controller : issued new clearance flight crew : took precautionary avoidance action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 2000 vertical : 0 |
Supplementary | |
Problem Areas | Environmental Factor Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
As we approached #1 (runway hold line) for runway 28L at cmh, we switched from ground control to tower frequency. No other aircraft were between our position and the end of the runway. We heard cmh tower say 'yxx cleared for takeoff, runway 28L.' we responded to the call by saying 'air carrier yxx cleared for takeoff,' taxied onto the runway and completed required checklist items. After visually clearing final approach to the runway, we directed our attention down the runway and saw a hawker pull onto the runway from an intersection in front of us. We called, 'tower air carrier yxx' and began to exit the runway. Tower replied 'yxx, what are you doing?' we responded that we had acknowledged our takeoff clearance. Tower said we had not been cleared for takeoff and that we could just stay where we were. We repositioned the aircraft for takeoff, requested a phone number to discuss the matter after we arrived at our destination and reaccomplished required checklist items in preparation for departure. Upon discussion with the cmh tower supervisor, the captain was told the tapes revealed the following: we had mistaken 'hawker yx' for 'air carrier yxx.' the controller had never mentioned the intersection takeoff in the takeoff clearance. Our 'air carrier yxx cleared for takeoff' response was audible but there was no response from tower. To prevent recurrence, proper terminology should always be used to include full call sign and intersection designation if takeoff clearance is being issued from other than the end of the runway. If an incorrect readback (or acknowledgement) of a clearance is heard immediate action should be taken to clarify the situation.
Original NASA ASRS Text
Title: A B737-300 TAKES POS AND HOLD ON RWY 28L WHEN THE CLRNC WAS FOR A HAWKER WITH A SIMILAR ALPHA NUMERIC AT CMH, OH.
Narrative: AS WE APCHED #1 (RWY HOLD LINE) FOR RWY 28L AT CMH, WE SWITCHED FROM GND CTL TO TWR FREQ. NO OTHER ACFT WERE BTWN OUR POS AND THE END OF THE RWY. WE HEARD CMH TWR SAY 'YXX CLRED FOR TKOF, RWY 28L.' WE RESPONDED TO THE CALL BY SAYING 'ACR YXX CLRED FOR TKOF,' TAXIED ONTO THE RWY AND COMPLETED REQUIRED CHKLIST ITEMS. AFTER VISUALLY CLRING FINAL APCH TO THE RWY, WE DIRECTED OUR ATTN DOWN THE RWY AND SAW A HAWKER PULL ONTO THE RWY FROM AN INTXN IN FRONT OF US. WE CALLED, 'TWR ACR YXX' AND BEGAN TO EXIT THE RWY. TWR REPLIED 'YXX, WHAT ARE YOU DOING?' WE RESPONDED THAT WE HAD ACKNOWLEDGED OUR TKOF CLRNC. TWR SAID WE HAD NOT BEEN CLRED FOR TKOF AND THAT WE COULD JUST STAY WHERE WE WERE. WE REPOSITIONED THE ACFT FOR TKOF, REQUESTED A PHONE NUMBER TO DISCUSS THE MATTER AFTER WE ARRIVED AT OUR DEST AND REACCOMPLISHED REQUIRED CHKLIST ITEMS IN PREPARATION FOR DEP. UPON DISCUSSION WITH THE CMH TWR SUPVR, THE CAPT WAS TOLD THE TAPES REVEALED THE FOLLOWING: WE HAD MISTAKEN 'HAWKER YX' FOR 'ACR YXX.' THE CTLR HAD NEVER MENTIONED THE INTXN TKOF IN THE TKOF CLRNC. OUR 'ACR YXX CLRED FOR TKOF' RESPONSE WAS AUDIBLE BUT THERE WAS NO RESPONSE FROM TWR. TO PREVENT RECURRENCE, PROPER TERMINOLOGY SHOULD ALWAYS BE USED TO INCLUDE FULL CALL SIGN AND INTXN DESIGNATION IF TKOF CLRNC IS BEING ISSUED FROM OTHER THAN THE END OF THE RWY. IF AN INCORRECT READBACK (OR ACKNOWLEDGEMENT) OF A CLRNC IS HEARD IMMEDIATE ACTION SHOULD BE TAKEN TO CLARIFY THE SIT.
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.