37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 478109 |
Time | |
Date | 200006 |
Day | Wed |
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 | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bos.tower tower : lax.tower |
Operator | common carrier : air carrier |
Make Model Name | B767-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi ground : holding |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bos.tower |
Operator | common carrier : air carrier |
Make Model Name | SF 340A |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : vacating altitude |
Route In Use | approach : visual approach : traffic pattern |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial pilot : multi engine |
ASRS Report | 478109 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 478110 |
Events | |
Anomaly | conflict : ground less severe non adherence : required legal separation non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance flight crew : executed go around |
Consequence | Other |
Miss Distance | horizontal : 1000 vertical : 200 |
Supplementary | |
Problem Areas | Flight Crew Human Performance Environmental Factor Airport ATC Human Performance Aircraft |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Location: bos. We were holding at the bravo hold point on our way to runway 4R. We were cleared to cross the approach end of runway 4L up to and hold short of runway 4R. Tower informed us of traffic on a 2 mi final for runway 4L. As we proceeded to cross the approach end of runway 4L, tower stated no delay across runway 4L. We told him we were heavy and doing our best 'we're working on it -- we're pretty heavy.' when we started to cross runway 4L, final approach was clear but as we moved across, a saab 340 on a visual approach to runway 4L came up the channel and rolled out on a very short final. The saab was not in our view when we initially started across runway 4L. The captain was using maximum allowable power for breakaway thrust, heavy B767-200. The airplane was slow to move and the GA ramp was right behind us. The saab continued his approach to runway 4L, down to approximately 200 ft AGL, when the tower told him to go around. We believe the saab may have continued his approach to touchdown if not commanded to go around. When the tower first told us about the traffic he did not tell us that the traffic was not a straight-in but in fact on a left downwind to an approach requiring a hard turn to final. We suggest the tower be made aware of the limitations of an airplane like the B767-200 on a warm day. I think we can do better -- even in consideration of business of the bos flight operation at this time of day. Supplemental information from acn 478110: we told the tower we were heavy and we would do our best. I used maximum allowable power for breakaway thrust and airplane was slow to move. It is our view that the saab would have possibly flown over our aircraft had the tower not told him to go around. To see him appear from the west as we were crossing was quite startling. The controllers seem to have very little knowledge as to the power and time requirements to taxi a heavy airliner on a hot day.
Original NASA ASRS Text
Title: A B767-200 FLC IS SLOW TO MOVE THEIR HVY ACFT ACROSS RWY 4L TAXIING TO RWY 4R. TWR HAS AN SF340 ON SHORT FINAL GO AROUND AT BOS, MA.
Narrative: LOCATION: BOS. WE WERE HOLDING AT THE BRAVO HOLD POINT ON OUR WAY TO RWY 4R. WE WERE CLRED TO CROSS THE APCH END OF RWY 4L UP TO AND HOLD SHORT OF RWY 4R. TWR INFORMED US OF TFC ON A 2 MI FINAL FOR RWY 4L. AS WE PROCEEDED TO CROSS THE APCH END OF RWY 4L, TWR STATED NO DELAY ACROSS RWY 4L. WE TOLD HIM WE WERE HVY AND DOING OUR BEST 'WE'RE WORKING ON IT -- WE'RE PRETTY HVY.' WHEN WE STARTED TO CROSS RWY 4L, FINAL APCH WAS CLR BUT AS WE MOVED ACROSS, A SAAB 340 ON A VISUAL APCH TO RWY 4L CAME UP THE CHANNEL AND ROLLED OUT ON A VERY SHORT FINAL. THE SAAB WAS NOT IN OUR VIEW WHEN WE INITIALLY STARTED ACROSS RWY 4L. THE CAPT WAS USING MAX ALLOWABLE PWR FOR BREAKAWAY THRUST, HVY B767-200. THE AIRPLANE WAS SLOW TO MOVE AND THE GA RAMP WAS RIGHT BEHIND US. THE SAAB CONTINUED HIS APCH TO RWY 4L, DOWN TO APPROX 200 FT AGL, WHEN THE TWR TOLD HIM TO GO AROUND. WE BELIEVE THE SAAB MAY HAVE CONTINUED HIS APCH TO TOUCHDOWN IF NOT COMMANDED TO GO AROUND. WHEN THE TWR FIRST TOLD US ABOUT THE TFC HE DID NOT TELL US THAT THE TFC WAS NOT A STRAIGHT-IN BUT IN FACT ON A L DOWNWIND TO AN APCH REQUIRING A HARD TURN TO FINAL. WE SUGGEST THE TWR BE MADE AWARE OF THE LIMITATIONS OF AN AIRPLANE LIKE THE B767-200 ON A WARM DAY. I THINK WE CAN DO BETTER -- EVEN IN CONSIDERATION OF BUSINESS OF THE BOS FLT OP AT THIS TIME OF DAY. SUPPLEMENTAL INFO FROM ACN 478110: WE TOLD THE TWR WE WERE HVY AND WE WOULD DO OUR BEST. I USED MAX ALLOWABLE PWR FOR BREAKAWAY THRUST AND AIRPLANE WAS SLOW TO MOVE. IT IS OUR VIEW THAT THE SAAB WOULD HAVE POSSIBLY FLOWN OVER OUR ACFT HAD THE TWR NOT TOLD HIM TO GO AROUND. TO SEE HIM APPEAR FROM THE W AS WE WERE XING WAS QUITE STARTLING. THE CTLRS SEEM TO HAVE VERY LITTLE KNOWLEDGE AS TO THE PWR AND TIME REQUIREMENTS TO TAXI A HVY AIRLINER ON A HOT DAY.
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.