37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 108132 |
Time | |
Date | 198904 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sts |
State Reference | CA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air taxi |
Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | ground : holding ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 75 flight time total : 7500 flight time type : 250 |
ASRS Report | 108132 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : atp pilot : instrument |
Experience | flight time last 90 days : 60 flight time total : 1870 flight time type : 60 |
ASRS Report | 108117 |
Events | |
Anomaly | incursion : runway non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew Other |
Supplementary | |
Primary Problem | Ambiguous |
Air Traffic Incident | Intra Facility Coordination Failure Operational Deviation Pilot Deviation |
Situations | |
Airport | other physical facility |
Narrative:
First officer called ground control and advised them that we were ready to taxi for departure. We were cleared to taxi to runway 14. While taxiing to runway 14, we were advised by ground to expect runway 19 for departure. As we taxied up to hold bar, we received clearance to taxi across runway 14 and contact the tower on 118.5. As we started across runway 14, the first officer contacted the tower. The tower controller told us that we had not been cleared onto the runway and that we should never taxi onto a runway west/O clearance from the tower. He then cleared us for takeoff on runway 14. The runway incursion was the result of miscom between the controllers and the crew. We believed that we were cleared to cross 14 and contact the tower for departure on 19. (It is possible that ground and the local controller had a misunderstanding, as well.) the event probably could have been avoided had we contacted tower prior to commencing our taxi across 14. Supplemental information from acn 108117: we had been told to expect runway 19 for departure. When approaching the end of the runway, we both understood the instruction to cross 14 for 19 and contact the tower on 118.5. I do not believe that this was well coordinated as the tower controller said we were not cleared to cross the end of 14. By this time we had reached 19 and were cleared to depart on 14. By that time we were both really confused and had to make another swing around to get back to 14. The intxns of 14/19 on the commercial chart appear to have space between them when in fact they do not. A note should be placed on the chart (and in the aim) that pilots may not cross 14 to get to 19 west/O specific tower approval (this is our guess). Our lack of familiarity with the airport probably contributed to the runway incursion, but it seemed that there was not terrific coordination between ground and tower. The attitude of the tower controller was not great. We got a lengthy on the air bawling out. When trying to fly a turbo jet bizjet, that kind of distraction just adds to the difficulty of the moment. Traffic was very light and we did not cause any aircraft to go around or modify their approach.
Original NASA ASRS Text
Title: SMT FLT CREW SAYS THEY WERE CLEARED TO CROSS RWY 14 FOR TKOF ON RWY 19 BY GND CTLR. ACFT WAS ALSO ADVISED TO CONTACT TWR. TWR DISPUTES CLRNC TO CROSS RWY 14 AND IS HIGHLY CRITICAL ON RADIO TO FLT CREW.
Narrative: F/O CALLED GND CTL AND ADVISED THEM THAT WE WERE READY TO TAXI FOR DEP. WE WERE CLRED TO TAXI TO RWY 14. WHILE TAXIING TO RWY 14, WE WERE ADVISED BY GND TO EXPECT RWY 19 FOR DEP. AS WE TAXIED UP TO HOLD BAR, WE RECEIVED CLRNC TO TAXI ACROSS RWY 14 AND CONTACT THE TWR ON 118.5. AS WE STARTED ACROSS RWY 14, THE F/O CONTACTED THE TWR. THE TWR CTLR TOLD US THAT WE HAD NOT BEEN CLRED ONTO THE RWY AND THAT WE SHOULD NEVER TAXI ONTO A RWY W/O CLRNC FROM THE TWR. HE THEN CLRED US FOR TKOF ON RWY 14. THE RWY INCURSION WAS THE RESULT OF MISCOM BTWN THE CTLRS AND THE CREW. WE BELIEVED THAT WE WERE CLRED TO CROSS 14 AND CONTACT THE TWR FOR DEP ON 19. (IT IS POSSIBLE THAT GND AND THE LCL CTLR HAD A MISUNDERSTANDING, AS WELL.) THE EVENT PROBABLY COULD HAVE BEEN AVOIDED HAD WE CONTACTED TWR PRIOR TO COMMENCING OUR TAXI ACROSS 14. SUPPLEMENTAL INFO FROM ACN 108117: WE HAD BEEN TOLD TO EXPECT RWY 19 FOR DEP. WHEN APCHING THE END OF THE RWY, WE BOTH UNDERSTOOD THE INSTRUCTION TO CROSS 14 FOR 19 AND CONTACT THE TWR ON 118.5. I DO NOT BELIEVE THAT THIS WAS WELL COORDINATED AS THE TWR CTLR SAID WE WERE NOT CLRED TO CROSS THE END OF 14. BY THIS TIME WE HAD REACHED 19 AND WERE CLRED TO DEPART ON 14. BY THAT TIME WE WERE BOTH REALLY CONFUSED AND HAD TO MAKE ANOTHER SWING AROUND TO GET BACK TO 14. THE INTXNS OF 14/19 ON THE COMMERCIAL CHART APPEAR TO HAVE SPACE BTWN THEM WHEN IN FACT THEY DO NOT. A NOTE SHOULD BE PLACED ON THE CHART (AND IN THE AIM) THAT PLTS MAY NOT CROSS 14 TO GET TO 19 W/O SPECIFIC TWR APPROVAL (THIS IS OUR GUESS). OUR LACK OF FAMILIARITY WITH THE ARPT PROBABLY CONTRIBUTED TO THE RWY INCURSION, BUT IT SEEMED THAT THERE WAS NOT TERRIFIC COORD BTWN GND AND TWR. THE ATTITUDE OF THE TWR CTLR WAS NOT GREAT. WE GOT A LENGTHY ON THE AIR BAWLING OUT. WHEN TRYING TO FLY A TURBO JET BIZJET, THAT KIND OF DISTR JUST ADDS TO THE DIFFICULTY OF THE MOMENT. TFC WAS VERY LIGHT AND WE DID NOT CAUSE ANY ACFT TO GO AROUND OR MODIFY THEIR APCH.
Data retrieved from NASA's ASRS site as of August 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.