 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of a canadair CL65 taxied to an active taxiway without clearance after gate pushback clearance due to ramp congestion and unable to make contact with the ground controller.
| Attributes | |
| ACN | 439100 |
| Time | |
| Date | 199906 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : bos.airport |
| State Reference | MA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | Challenger CL604 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : commercial pilot : cfi pilot : flight engineer |
| Experience | flight time last 90 days : 150 flight time total : 1920 flight time type : 600 |
| ASRS Report | 439100 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | incursion : taxiway non adherence : far |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued alert none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Airport Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Our flight was cleared to push out of gate AC and issued traffic that was coming in to gate ag (farther down the alley). When trying to contact ground to taxi, the frequency was completely full and everyone was stepping on each other. Our traffic had already taxied in to their gate and another airplane was ready to push out of gate ad. The captain started to slowly taxi to the end of alley, since we would be blocking traffic into and out of the alley. Finally, I was able to contact ground. He informed us we were on an active taxiway without a clearance. When we were at the end of the alley, our nose may have been blocking the end of taxiway a. Separate frequencys at bos might be a good idea (inbound/outbound or north/south). It also seems that tower has to provide many ground control functions. If ground had 2 frequencys, they could handle pushback requests, freeing up clearance delivery frequency (also very busy during peak times).
Original NASA ASRS Text
Title: FLC OF A CANADAIR CL65 TAXIED TO AN ACTIVE TXWY WITHOUT CLRNC AFTER GATE PUSHBACK CLRNC DUE TO RAMP CONGESTION AND UNABLE TO MAKE CONTACT WITH THE GND CTLR.
Narrative: OUR FLT WAS CLRED TO PUSH OUT OF GATE AC AND ISSUED TFC THAT WAS COMING IN TO GATE AG (FARTHER DOWN THE ALLEY). WHEN TRYING TO CONTACT GND TO TAXI, THE FREQ WAS COMPLETELY FULL AND EVERYONE WAS STEPPING ON EACH OTHER. OUR TFC HAD ALREADY TAXIED IN TO THEIR GATE AND ANOTHER AIRPLANE WAS READY TO PUSH OUT OF GATE AD. THE CAPT STARTED TO SLOWLY TAXI TO THE END OF ALLEY, SINCE WE WOULD BE BLOCKING TFC INTO AND OUT OF THE ALLEY. FINALLY, I WAS ABLE TO CONTACT GND. HE INFORMED US WE WERE ON AN ACTIVE TXWY WITHOUT A CLRNC. WHEN WE WERE AT THE END OF THE ALLEY, OUR NOSE MAY HAVE BEEN BLOCKING THE END OF TXWY A. SEPARATE FREQS AT BOS MIGHT BE A GOOD IDEA (INBOUND/OUTBOUND OR N/S). IT ALSO SEEMS THAT TWR HAS TO PROVIDE MANY GND CTL FUNCTIONS. IF GND HAD 2 FREQS, THEY COULD HANDLE PUSHBACK REQUESTS, FREEING UP CLRNC DELIVERY FREQ (ALSO VERY BUSY DURING PEAK TIMES).
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.