 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B777-200 flight crew concerned with nct approach clearance for runway 28L visual approach to sfo while slowly overtaking a B757 on approach to runway 28R and tower concerned with succeeding traffic to runway 28R.
| Attributes | |
| ACN | 589579 |
| Time | |
| Date | 200307 |
| Day | Wed |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : sfo.airport |
| State Reference | CA |
| Altitude | msl single value : 2000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : nct.tracon tower : sfo.tower tower : zzz.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B777-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : nct.tracon tower : sfo.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 589579 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Airspace Structure Airport ATC Human Performance Aircraft |
| Primary Problem | ATC Human Performance |
Narrative:
We were cleared by norcal approach for a visual approach to runway 28L at sfo with traffic (B757) ahead landing on runway 28R. We were also instructed to maintain 180 KTS to the bridge. As we approached the bridge, it was evident that we were gaining on the runway 28R traffic, so I slowed to final approach speed to remain behind the parallel traffic. Even at our approach speed, we were faster than the runway 28R traffic, so that by the time we reached the runway, we were abeam the other aircraft. I realize that ATC is attempting to maximum the traffic into sfo, however, I don't think they should issue a speed restr when they want you to remain behind a leading aircraft on closely spaced visual approachs. Additionally, they should issue some indication of speed differential (eg, your speeds are matched, or, you have a 30 KT overtake on traffic) especially at night. This would greatly assist the pilot in planning a safe approach. Additionally, after landing, sfo tower requested that we expedite off the runway due to landing traffic behind us. Sometimes the sfo operation cuts the safety margin a little too thin.
Original NASA ASRS Text
Title: B777-200 FLT CREW CONCERNED WITH NCT APCH CLRNC FOR RWY 28L VISUAL APCH TO SFO WHILE SLOWLY OVERTAKING A B757 ON APCH TO RWY 28R AND TWR CONCERNED WITH SUCCEEDING TFC TO RWY 28R.
Narrative: WE WERE CLRED BY NORCAL APCH FOR A VISUAL APCH TO RWY 28L AT SFO WITH TFC (B757) AHEAD LNDG ON RWY 28R. WE WERE ALSO INSTRUCTED TO MAINTAIN 180 KTS TO THE BRIDGE. AS WE APCHED THE BRIDGE, IT WAS EVIDENT THAT WE WERE GAINING ON THE RWY 28R TFC, SO I SLOWED TO FINAL APCH SPD TO REMAIN BEHIND THE PARALLEL TFC. EVEN AT OUR APCH SPD, WE WERE FASTER THAN THE RWY 28R TFC, SO THAT BY THE TIME WE REACHED THE RWY, WE WERE ABEAM THE OTHER ACFT. I REALIZE THAT ATC IS ATTEMPTING TO MAX THE TFC INTO SFO, HOWEVER, I DON'T THINK THEY SHOULD ISSUE A SPD RESTR WHEN THEY WANT YOU TO REMAIN BEHIND A LEADING ACFT ON CLOSELY SPACED VISUAL APCHS. ADDITIONALLY, THEY SHOULD ISSUE SOME INDICATION OF SPD DIFFERENTIAL (EG, YOUR SPDS ARE MATCHED, OR, YOU HAVE A 30 KT OVERTAKE ON TFC) ESPECIALLY AT NIGHT. THIS WOULD GREATLY ASSIST THE PLT IN PLANNING A SAFE APCH. ADDITIONALLY, AFTER LNDG, SFO TWR REQUESTED THAT WE EXPEDITE OFF THE RWY DUE TO LNDG TFC BEHIND US. SOMETIMES THE SFO OP CUTS THE SAFETY MARGIN A LITTLE TOO THIN.
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.