37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1112161 |
Time | |
Date | 201309 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B737-800 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
An A321 was cleared for the FMS bridge visual approach runway 28R upon sighting the airport 25 NM east of sfo. The A321 was indicating 200 KTS and about 7 NM in trail of a preceding B757. A B737 was inbound from the southeast of sfo via the big sur 2 arrival routing and expecting the tip toe visual to runway 28L. The B737 did not check in with woodside until about 20 NM south of sfo descending only out of 7;000 MSL and indicating 300 KTS. The B737 was issued a vector upon check in for a right turn heading 040 and a descent to 4;000. The B737 was then instructed to reduce to 180 KTS. As the B737 and the A321 converged traffic was given to both aircraft. The A321 reported sighting the B737 first and was instructed to maintain visual separation. The A321 acknowledged with a read back. The B737 at this point was about 4 NM south of the A321 and still did not report sighting the B737 nor did a speed reduction look apparent. The B737 was issued a vector back to the west heading 270 to parallel the A321 on final and line up for a straight in to [runway] 28L. Traffic was once again issued to the B737. At this point both aircraft were leaving 5;200 MSL. The B737 reported sighting the A321 and was told to maintain visual separation. The B737 was slow to turn and went well north of the final approach course converging with the A321 at an altitude of 4;800. The B737 continued north of final before indicating a westerly heading. Both aircraft reported responding to an RA. When the A321 reported that the RA was complete it received a cancellation of clearance and told to maintain 4;000 and traffic calls were issued to both aircraft. The B737 was instructed to fly heading 300 and continue descent to 2;500. The A321 reported not sighting the B737 flight and was issued a vector heading 250 at 4;000. The B737 was turned back to final and upon sighting the airport cleared for a visual approach to runway 28R. The A321 was re-sequenced to the south for a visual approach to [runway] 28L. The B737 should have either been switched to my frequency sooner or they should have checked in sooner to receive proper speed restrictions and shallower vectors for the approach. Altitude separation should have been ensured until both aircraft were in positions to make safe side by side approaches. The B737 could have stayed on the arrival and left fast to pair with the preceding B757.
Original NASA ASRS Text
Title: NCT Controller described an unsafe event during side-by visual approach procedures at SFO when one aircraft failed to see parallel traffic; the reporter believes speed and a late hand off were causal factors.
Narrative: An A321 was cleared for the FMS Bridge Visual Approach Runway 28R upon sighting the airport 25 NM east of SFO. The A321 was indicating 200 KTS and about 7 NM in trail of a preceding B757. A B737 was inbound from the southeast of SFO via the Big Sur 2 arrival routing and expecting the Tip Toe Visual to Runway 28L. The B737 did not check in with Woodside until about 20 NM south of SFO descending only out of 7;000 MSL and indicating 300 KTS. The B737 was issued a vector upon check in for a right turn heading 040 and a descent to 4;000. The B737 was then instructed to reduce to 180 KTS. As the B737 and the A321 converged traffic was given to both aircraft. The A321 reported sighting the B737 first and was instructed to maintain visual separation. The A321 acknowledged with a read back. The B737 at this point was about 4 NM south of the A321 and still did not report sighting the B737 nor did a speed reduction look apparent. The B737 was issued a vector back to the west heading 270 to parallel the A321 on final and line up for a straight in to [Runway] 28L. Traffic was once again issued to the B737. At this point both aircraft were leaving 5;200 MSL. The B737 reported sighting the A321 and was told to maintain visual separation. The B737 was slow to turn and went well north of the final approach course converging with the A321 at an altitude of 4;800. The B737 continued north of final before indicating a westerly heading. Both aircraft reported responding to an RA. When the A321 reported that the RA was complete it received a cancellation of clearance and told to maintain 4;000 and traffic calls were issued to both aircraft. The B737 was instructed to fly heading 300 and continue descent to 2;500. The A321 reported not sighting the B737 flight and was issued a vector heading 250 at 4;000. The B737 was turned back to final and upon sighting the airport cleared for a visual approach to Runway 28R. The A321 was re-sequenced to the south for a visual approach to [Runway] 28L. The B737 should have either been switched to my frequency sooner or they should have checked in sooner to receive proper speed restrictions and shallower vectors for the approach. Altitude separation should have been ensured until both aircraft were in positions to make safe side by side approaches. The B737 could have stayed on the arrival and left fast to pair with the preceding B757.
Data retrieved from NASA's ASRS site as of July 2013 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.