37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 473122 |
Time | |
Date | 200005 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : cvg.airport |
State Reference | OH |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : cvg.tower |
Operator | general aviation : corporate |
Make Model Name | IAI1125 (Astra) |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : takeoff roll ground : holding |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : cvg.tower |
Operator | general aviation : corporate |
Make Model Name | Gulfstream Jet Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Navigation In Use | ils localizer & glide slope : 18r other |
Flight Phase | descent : vacating altitude landing : go around |
Route In Use | approach : instrument precision |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 70 flight time total : 3280 flight time type : 1590 |
ASRS Report | 473122 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 5000 flight time type : 1300 |
ASRS Report | 473111 |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : clearance non adherence : required legal separation non adherence : published procedure non adherence : far other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance controller : issued alert flight crew : executed go around flight crew : rejected takeoff |
Consequence | faa : investigated faa : reviewed incident with flight crew other |
Miss Distance | horizontal : 2000 vertical : 800 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance Airport Environmental Factor |
Primary Problem | Environmental Factor |
Air Traffic Incident | Operational Deviation |
Narrative:
We received clearance to taxi to cvg runway 18R, hold short of runway 27, cross runway 27 hold short of a taxiway for an rj to pass and continue to runway 18R. We completed our taxi checks and were fourth in line for takeoff when we started to monitor tower. The PF and I discussed the WX in the departure course and possible deviations required. An airline jet took off and we moved up and held short of runway 18R. We could see landing traffic on the TCASII and visually while waiting takeoff clearance. The PF and myself heard us be cleared for takeoff and I read back the clearance, checking and confirming final for traffic spacing which appeared to be adequate. We completed the lineup checklist and started takeoff. The tower called for us to abort at a low speed. We complied and exited the runway. An aircraft landing runway 18R executed a go around. Tower then issued a clearance to taxi back to runway 18R on their frequency. We had no indication that we might have made a mistake. No mention of error from tower for anyone to call the supervisor. My experience at cvg gars are fairly normal due to the amount of traffic and spacing of traffic. We completed another before takeoff checklist and lineup checklist. Another aircraft landed and tower cleared us into position and hold. Tower then cleared us for takeoff. The takeoff went normally. Once we reached cruise, we discussed what happened. I contacted cvg tower via the flight phone (poor connections, lots of static -- it took several calls) talking with both the controllers. They informed me that a pilot deviation had been filed on us. The PF and I are still certain that the takeoff clearance was issued to us. Cvg tower also said that they were handling 3 aircraft -- all ending with nxxxxg. Their review of the tapes had no record of takeoff clearance being issued to us, however, there was a garbled transmission before we lined up on the runway which most likely was our readback of the takeoff clearance. If the transmission had not been blocked, tower should have heard us unless tower was transmitting at the same time. There was no loss of separation with runway 27 (intersects runway 18R). After talking with cvg tower, I contacted our chief pilot to inform him that a pilot deviation was filed through louisville and atlanta. I told him our impressions and disbelief of both of us hearing the wrong clearance. We were expecting takeoff clearance and when we received what we both heard was that clearance we continued with our takeoff flows and checks. As a standard practice if one of the flight crew is in doubt about a clearance we always confirm with the controller. Neither of us were in doubt of being cleared for takeoff. Having so many similar sounding n-numbers is confusing for controllers as well as pilots. Possibly we mistook the aircraft departing runway 27 readback of their takeoff clearance and our own takeoff clearance. I do not know why my readback of 'nxxxxg cleared for takeoff runway 18R' was not heard. When I checked to make sure final was clear, there appeared to be enough separation. What I did not know is the aircraft on final was a gulfstream and not an MD80 I thought I saw. If my readback of our takeoff clearance was covered by tower, or another aircraft, tower might not have heard me. Although, while waiting to take off, tower frequency was blocked at least once with another pilot coming on saying 'blocked,' nothing was said after we took the runway. We experienced a major breakdown of communication of which we were unaware until contacting cvg tower from the air. We both understood we were cleared for takeoff. It is disturbing to think that we could simultaneously hear and interpret the same information in error. Given the amount of traffic at many airports such as cvg, and the inherent limitations of radio communications, I would like to see additional lighting at the hold area: red = hold/hold short and green = proceed. I don't know if it would help much, but if air traffic is going to increase as predicted, additional system might be necessary to prevent decreases in safety. Supplemental information from acn 473111: we were holding short of runway 18R when we got the clearance to take off runway 18R. Both of us acted independently to the clearance. I pulled off the parking brake and started moving into position. The PNF read back the clearance 'astra nxxxxg cleared to takeoff runway 18R.' the aircraft landing on runway 18R announced he was going around.
Original NASA ASRS Text
Title: AN ASTRA 1125 FLC TAKES THEIR ACFT ONTO THE RWY ON A ROLLING TKOF WITHOUT BENEFIT OF TWR CLRNC AT CVG, OH.
Narrative: WE RECEIVED CLRNC TO TAXI TO CVG RWY 18R, HOLD SHORT OF RWY 27, CROSS RWY 27 HOLD SHORT OF A TXWY FOR AN RJ TO PASS AND CONTINUE TO RWY 18R. WE COMPLETED OUR TAXI CHKS AND WERE FOURTH IN LINE FOR TKOF WHEN WE STARTED TO MONITOR TWR. THE PF AND I DISCUSSED THE WX IN THE DEP COURSE AND POSSIBLE DEVS REQUIRED. AN AIRLINE JET TOOK OFF AND WE MOVED UP AND HELD SHORT OF RWY 18R. WE COULD SEE LNDG TFC ON THE TCASII AND VISUALLY WHILE WAITING TKOF CLRNC. THE PF AND MYSELF HEARD US BE CLRED FOR TKOF AND I READ BACK THE CLRNC, CHKING AND CONFIRMING FINAL FOR TFC SPACING WHICH APPEARED TO BE ADEQUATE. WE COMPLETED THE LINEUP CHKLIST AND STARTED TKOF. THE TWR CALLED FOR US TO ABORT AT A LOW SPD. WE COMPLIED AND EXITED THE RWY. AN ACFT LNDG RWY 18R EXECUTED A GAR. TWR THEN ISSUED A CLRNC TO TAXI BACK TO RWY 18R ON THEIR FREQ. WE HAD NO INDICATION THAT WE MIGHT HAVE MADE A MISTAKE. NO MENTION OF ERROR FROM TWR FOR ANYONE TO CALL THE SUPVR. MY EXPERIENCE AT CVG GARS ARE FAIRLY NORMAL DUE TO THE AMOUNT OF TFC AND SPACING OF TFC. WE COMPLETED ANOTHER BEFORE TKOF CHKLIST AND LINEUP CHKLIST. ANOTHER ACFT LANDED AND TWR CLRED US INTO POS AND HOLD. TWR THEN CLRED US FOR TKOF. THE TKOF WENT NORMALLY. ONCE WE REACHED CRUISE, WE DISCUSSED WHAT HAPPENED. I CONTACTED CVG TWR VIA THE FLT PHONE (POOR CONNECTIONS, LOTS OF STATIC -- IT TOOK SEVERAL CALLS) TALKING WITH BOTH THE CTLRS. THEY INFORMED ME THAT A PLTDEV HAD BEEN FILED ON US. THE PF AND I ARE STILL CERTAIN THAT THE TKOF CLRNC WAS ISSUED TO US. CVG TWR ALSO SAID THAT THEY WERE HANDLING 3 ACFT -- ALL ENDING WITH NXXXXG. THEIR REVIEW OF THE TAPES HAD NO RECORD OF TKOF CLRNC BEING ISSUED TO US, HOWEVER, THERE WAS A GARBLED XMISSION BEFORE WE LINED UP ON THE RWY WHICH MOST LIKELY WAS OUR READBACK OF THE TKOF CLRNC. IF THE XMISSION HAD NOT BEEN BLOCKED, TWR SHOULD HAVE HEARD US UNLESS TWR WAS XMITTING AT THE SAME TIME. THERE WAS NO LOSS OF SEPARATION WITH RWY 27 (INTERSECTS RWY 18R). AFTER TALKING WITH CVG TWR, I CONTACTED OUR CHIEF PLT TO INFORM HIM THAT A PLTDEV WAS FILED THROUGH LOUISVILLE AND ATLANTA. I TOLD HIM OUR IMPRESSIONS AND DISBELIEF OF BOTH OF US HEARING THE WRONG CLRNC. WE WERE EXPECTING TKOF CLRNC AND WHEN WE RECEIVED WHAT WE BOTH HEARD WAS THAT CLRNC WE CONTINUED WITH OUR TKOF FLOWS AND CHKS. AS A STANDARD PRACTICE IF ONE OF THE FLC IS IN DOUBT ABOUT A CLRNC WE ALWAYS CONFIRM WITH THE CTLR. NEITHER OF US WERE IN DOUBT OF BEING CLRED FOR TKOF. HAVING SO MANY SIMILAR SOUNDING N-NUMBERS IS CONFUSING FOR CTLRS AS WELL AS PLTS. POSSIBLY WE MISTOOK THE ACFT DEPARTING RWY 27 READBACK OF THEIR TKOF CLRNC AND OUR OWN TKOF CLRNC. I DO NOT KNOW WHY MY READBACK OF 'NXXXXG CLRED FOR TKOF RWY 18R' WAS NOT HEARD. WHEN I CHKED TO MAKE SURE FINAL WAS CLR, THERE APPEARED TO BE ENOUGH SEPARATION. WHAT I DID NOT KNOW IS THE ACFT ON FINAL WAS A GULFSTREAM AND NOT AN MD80 I THOUGHT I SAW. IF MY READBACK OF OUR TKOF CLRNC WAS COVERED BY TWR, OR ANOTHER ACFT, TWR MIGHT NOT HAVE HEARD ME. ALTHOUGH, WHILE WAITING TO TAKE OFF, TWR FREQ WAS BLOCKED AT LEAST ONCE WITH ANOTHER PLT COMING ON SAYING 'BLOCKED,' NOTHING WAS SAID AFTER WE TOOK THE RWY. WE EXPERIENCED A MAJOR BREAKDOWN OF COM OF WHICH WE WERE UNAWARE UNTIL CONTACTING CVG TWR FROM THE AIR. WE BOTH UNDERSTOOD WE WERE CLRED FOR TKOF. IT IS DISTURBING TO THINK THAT WE COULD SIMULTANEOUSLY HEAR AND INTERPRET THE SAME INFO IN ERROR. GIVEN THE AMOUNT OF TFC AT MANY ARPTS SUCH AS CVG, AND THE INHERENT LIMITATIONS OF RADIO COMS, I WOULD LIKE TO SEE ADDITIONAL LIGHTING AT THE HOLD AREA: RED = HOLD/HOLD SHORT AND GREEN = PROCEED. I DON'T KNOW IF IT WOULD HELP MUCH, BUT IF AIR TFC IS GOING TO INCREASE AS PREDICTED, ADDITIONAL SYS MIGHT BE NECESSARY TO PREVENT DECREASES IN SAFETY. SUPPLEMENTAL INFO FROM ACN 473111: WE WERE HOLDING SHORT OF RWY 18R WHEN WE GOT THE CLRNC TO TAKE OFF RWY 18R. BOTH OF US ACTED INDEPENDENTLY TO THE CLRNC. I PULLED OFF THE PARKING BRAKE AND STARTED MOVING INTO POS. THE PNF READ BACK THE CLRNC 'ASTRA NXXXXG CLRED TO TKOF RWY 18R.' THE ACFT LNDG ON RWY 18R ANNOUNCED HE WAS GOING AROUND.
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.