37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 469383 |
Time | |
Date | 200004 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bos.airport |
State Reference | MA |
Altitude | msl bound lower : 0 msl bound upper : 1000 |
Environment | |
Flight Conditions | VMC |
Weather Elements | Windshear Turbulence |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bos.tower |
Operator | common carrier : air carrier |
Make Model Name | B727-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 27 |
Flight Phase | landing : touch and go landing : go around |
Route In Use | approach : visual |
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 | climbout : takeoff climbout : initial |
Route In Use | departure : noise abatement |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 14000 flight time type : 4000 |
ASRS Report | 469383 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : commercial pilot : flight engineer |
Experience | flight time last 90 days : 180 flight time total : 6000 flight time type : 1000 |
ASRS Report | 469601 |
Events | |
Anomaly | conflict : airborne critical inflight encounter : turbulence non adherence : required legal separation other anomaly other |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | controller : issued advisory flight crew : executed go around flight crew : took evasive action |
Consequence | other |
Miss Distance | horizontal : 1000 vertical : 100 |
Supplementary | |
Problem Areas | FAA Flight Crew Human Performance Environmental Factor Weather ATC Human Performance Airport |
Primary Problem | FAA |
Situations | |
ATC Facility | procedure or policy : bos.tower |
Narrative:
We were landing on runway 27 in boston. The WX was clear, VFR, but with gusty winds. The landing resulted in a high bounce, from which we elected to go around. Although an unusual circumstance, the transition to the go around went well. However, as per usual ZBW procedures, another aircraft (a saab 340) had departed runway 22R, creating a converging conflict with a missed approach/go around situation of runway 27. As we commenced the go around, bos tower immediately issued us a turn to 140 degrees. This reminded us of the fact we'd seen and commented on the saab in position on runway 22R, as we approached runway 27, and the potential of conflict should we miss and they take off. We commenced an assertive left turn and continuation of our climb. Although no TCASII alert took place (too low for activation?) a quick glance of concern to the TCASII showed a target nearly under us by a mere 100 ft. This added vigor to our maneuver. We also asked the tower where the saab was -- they said it was going straight out and not a factor. Settled down, we made a nice visual approach and landing to runway 29. (An airbus A320 was also on a lahso approach to runway 22L, hold short of runway 27 -- imagine if they'd missed approach, too!). Obviously the go around was unusual and concerning to the passenger, some commented that they'd seen the other aircraft and it was close. Quite a few were also and understandably scared. We made appropriate follow-up PA announcements. Summary: from a pilot's point of view, the bounce and go around, although not common, was straight forward and well under control. Our main concern came from the close vicinity of the aircraft departing off runway 22R, and the fact that the sequence of runway 27 lndgs with runway 22R departures will result in 'too close for comfort' sits, should there be a runway 27 go around. These sits need be resequenced to consider gars, too, or else it seems 'only a matter of time!' callback conversation with reporter 469601 revealed the following information: the aircraft was turned so that it did not pass runway 22L, missing the saab by about 1000 ft horizontal. The captain had taken over the controls and made a tight turn to the assigned heading of 140 degrees to keep the flight away from the saab which was on a runway heading of 220 degrees below them. The first officer reported that this procedure has been in use for some time at bos. He stated that the PIC did talk with the facility chief, but does not know what transpired. The captain also turned in a company report, but so far as he knows did not report this to the union. The first officer was counseled to do so. One problem with this procedure is that the 2 aircraft were on separate frequencys, the saab on 128.8 and the B727 on 119.1. With departure jet traffic, there is not a conflict on a normal go around from runway 27 and a departure from runway 22L/right as the jet (unless very light) would be well under the flight path of a go around aircraft from runway 27. The other problem is that the turboprops, like the saab, are lifting off sooner, climbing out on runway heading and does create a conflict area with any aircraft on the go around from runway 27.
Original NASA ASRS Text
Title: A NEAR NMAC OCCURS AT THE END OF RWY 27 WHEN A B727-200 PERFORMS A GAR AND NEARLY HITS A DEP SF340 ON INITIAL CLB OFF RWY 22R AT BOS, MA.
Narrative: WE WERE LNDG ON RWY 27 IN BOSTON. THE WX WAS CLR, VFR, BUT WITH GUSTY WINDS. THE LNDG RESULTED IN A HIGH BOUNCE, FROM WHICH WE ELECTED TO GO AROUND. ALTHOUGH AN UNUSUAL CIRCUMSTANCE, THE TRANSITION TO THE GAR WENT WELL. HOWEVER, AS PER USUAL ZBW PROCS, ANOTHER ACFT (A SAAB 340) HAD DEPARTED RWY 22R, CREATING A CONVERGING CONFLICT WITH A MISSED APCH/GAR SIT OF RWY 27. AS WE COMMENCED THE GAR, BOS TWR IMMEDIATELY ISSUED US A TURN TO 140 DEGS. THIS REMINDED US OF THE FACT WE'D SEEN AND COMMENTED ON THE SAAB IN POS ON RWY 22R, AS WE APCHED RWY 27, AND THE POTENTIAL OF CONFLICT SHOULD WE MISS AND THEY TAKE OFF. WE COMMENCED AN ASSERTIVE L TURN AND CONTINUATION OF OUR CLB. ALTHOUGH NO TCASII ALERT TOOK PLACE (TOO LOW FOR ACTIVATION?) A QUICK GLANCE OF CONCERN TO THE TCASII SHOWED A TARGET NEARLY UNDER US BY A MERE 100 FT. THIS ADDED VIGOR TO OUR MANEUVER. WE ALSO ASKED THE TWR WHERE THE SAAB WAS -- THEY SAID IT WAS GOING STRAIGHT OUT AND NOT A FACTOR. SETTLED DOWN, WE MADE A NICE VISUAL APCH AND LNDG TO RWY 29. (AN AIRBUS A320 WAS ALSO ON A LAHSO APCH TO RWY 22L, HOLD SHORT OF RWY 27 -- IMAGINE IF THEY'D MISSED APCH, TOO!). OBVIOUSLY THE GAR WAS UNUSUAL AND CONCERNING TO THE PAX, SOME COMMENTED THAT THEY'D SEEN THE OTHER ACFT AND IT WAS CLOSE. QUITE A FEW WERE ALSO AND UNDERSTANDABLY SCARED. WE MADE APPROPRIATE FOLLOW-UP PA ANNOUNCEMENTS. SUMMARY: FROM A PLT'S POINT OF VIEW, THE BOUNCE AND GAR, ALTHOUGH NOT COMMON, WAS STRAIGHT FORWARD AND WELL UNDER CTL. OUR MAIN CONCERN CAME FROM THE CLOSE VICINITY OF THE ACFT DEPARTING OFF RWY 22R, AND THE FACT THAT THE SEQUENCE OF RWY 27 LNDGS WITH RWY 22R DEPS WILL RESULT IN 'TOO CLOSE FOR COMFORT' SITS, SHOULD THERE BE A RWY 27 GAR. THESE SITS NEED BE RESEQUENCED TO CONSIDER GARS, TOO, OR ELSE IT SEEMS 'ONLY A MATTER OF TIME!' CALLBACK CONVERSATION WITH RPTR 469601 REVEALED THE FOLLOWING INFO: THE ACFT WAS TURNED SO THAT IT DID NOT PASS RWY 22L, MISSING THE SAAB BY ABOUT 1000 FT HORIZ. THE CAPT HAD TAKEN OVER THE CTLS AND MADE A TIGHT TURN TO THE ASSIGNED HDG OF 140 DEGS TO KEEP THE FLT AWAY FROM THE SAAB WHICH WAS ON A RWY HDG OF 220 DEGS BELOW THEM. THE FO RPTED THAT THIS PROC HAS BEEN IN USE FOR SOME TIME AT BOS. HE STATED THAT THE PIC DID TALK WITH THE FACILITY CHIEF, BUT DOES NOT KNOW WHAT TRANSPIRED. THE CAPT ALSO TURNED IN A COMPANY RPT, BUT SO FAR AS HE KNOWS DID NOT RPT THIS TO THE UNION. THE FO WAS COUNSELED TO DO SO. ONE PROB WITH THIS PROC IS THAT THE 2 ACFT WERE ON SEPARATE FREQS, THE SAAB ON 128.8 AND THE B727 ON 119.1. WITH DEP JET TFC, THERE IS NOT A CONFLICT ON A NORMAL GAR FROM RWY 27 AND A DEP FROM RWY 22L/R AS THE JET (UNLESS VERY LIGHT) WOULD BE WELL UNDER THE FLT PATH OF A GAR ACFT FROM RWY 27. THE OTHER PROB IS THAT THE TURBOPROPS, LIKE THE SAAB, ARE LIFTING OFF SOONER, CLBING OUT ON RWY HDG AND DOES CREATE A CONFLICT AREA WITH ANY ACFT ON THE GAR FROM RWY 27.
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.