37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 439601 |
Time | |
Date | 199906 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mbs.airport |
State Reference | MI |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : mbs.tower |
Operator | common carrier : air taxi |
Make Model Name | Light Transport, Low Wing, 2 Turbojet Eng |
Operating Under FAR Part | Part 135 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : mbs.tower |
Operator | common carrier : air carrier |
Make Model Name | Challenger CL604 |
Operating Under FAR Part | Part 121 |
Flight Phase | landing : go around |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain |
Qualification | pilot : multi engine pilot : atp pilot : cfi |
Experience | flight time last 90 days : 300 flight time total : 9000 flight time type : 800 |
ASRS Report | 439601 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : cfi pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 310 flight time total : 3250 flight time type : 550 |
ASRS Report | 739549 |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance controller : separated traffic flight crew : executed go around flight crew : exited penetrated airspace |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We had our takeoff clearance canceled, to return to the FBO due to a hydraulic quantity reading. Upon our taxi the gauge gave a normal reading. I was sure it was the gauge. We elected to get another departure time from saginaw clearance to newark. Ground control told us there would not be a problem and offered us the option of turning around on the taxiway we were on. We advised unable. Ground then told us to taxi ahead and utilize the next taxiway for turnaround or onto the runway, with incoming traffic, not a problem. Both runway 5/23 were being used. Incoming traffic was using runway 5 were to use runway 23. We utilized taxiway G onto the runway. I called clear left. Upon entering the runway my first officer said there's incoming traffic. I accelerated the aircraft then immediately tower advised a regional jet to go around and then immediately for us to exit the runway. Both crews were advised to call the tower supervisor. I spoke with the supervisor who allowed me to hear the tape. It sounded like the first officer clicked the yoke microphone button and blocked out the tower's remark 'runway 23 available for back taxi in 2 mins due to incoming traffic.' my first officer's anxiousness to respond blocked this part of the transmission. We departed to yip as our next destination and he did it again. Upon reaching yip, we had a long discussion on 'the importance of good communication.' I believe it will help. I do wonder why the control did not issue the instruction 'hold short' with the appropriate readback.
Original NASA ASRS Text
Title: AIR TAXI CREW USED RWY FOR TAXI CAUSING A GAR BY ACR. COMPLETE CLRNC WAS NOT RECEIVED ACCOUNT RADIO INTERFERENCE. NO HOLD SHORT GIVEN BY CTLR. TWR TAPES REVIEWED WITH ALL CONCERNED.
Narrative: WE HAD OUR TKOF CLRNC CANCELED, TO RETURN TO THE FBO DUE TO A HYD QUANTITY READING. UPON OUR TAXI THE GAUGE GAVE A NORMAL READING. I WAS SURE IT WAS THE GAUGE. WE ELECTED TO GET ANOTHER DEP TIME FROM SAGINAW CLRNC TO NEWARK. GND CTL TOLD US THERE WOULD NOT BE A PROB AND OFFERED US THE OPTION OF TURNING AROUND ON THE TXWY WE WERE ON. WE ADVISED UNABLE. GND THEN TOLD US TO TAXI AHEAD AND UTILIZE THE NEXT TXWY FOR TURNAROUND OR ONTO THE RWY, WITH INCOMING TFC, NOT A PROB. BOTH RWY 5/23 WERE BEING USED. INCOMING TFC WAS USING RWY 5 WERE TO USE RWY 23. WE UTILIZED TXWY G ONTO THE RWY. I CALLED CLR L. UPON ENTERING THE RWY MY FO SAID THERE'S INCOMING TFC. I ACCELERATED THE ACFT THEN IMMEDIATELY TWR ADVISED A REGIONAL JET TO GO AROUND AND THEN IMMEDIATELY FOR US TO EXIT THE RWY. BOTH CREWS WERE ADVISED TO CALL THE TWR SUPVR. I SPOKE WITH THE SUPVR WHO ALLOWED ME TO HEAR THE TAPE. IT SOUNDED LIKE THE FO CLICKED THE YOKE MIKE BUTTON AND BLOCKED OUT THE TWR'S REMARK 'RWY 23 AVAILABLE FOR BACK TAXI IN 2 MINS DUE TO INCOMING TFC.' MY FO'S ANXIOUSNESS TO RESPOND BLOCKED THIS PART OF THE XMISSION. WE DEPARTED TO YIP AS OUR NEXT DEST AND HE DID IT AGAIN. UPON REACHING YIP, WE HAD A LONG DISCUSSION ON 'THE IMPORTANCE OF GOOD COM.' I BELIEVE IT WILL HELP. I DO WONDER WHY THE CTL DID NOT ISSUE THE INSTRUCTION 'HOLD SHORT' WITH THE APPROPRIATE READBACK.
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.