37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 431407 |
Time | |
Date | 199903 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : sfo.vor |
State Reference | CA |
Altitude | msl single value : 5500 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : o90.tracon |
Operator | common carrier : air carrier |
Make Model Name | B767-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | approach : charted visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : o90.tracon |
Operator | common carrier : air carrier |
Make Model Name | B767 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : instrument pilot : flight engineer pilot : cfi pilot : atp pilot : commercial |
Experience | flight time total : 13500 flight time type : 180 |
ASRS Report | 431407 |
Person 2 | |
Function | flight crew : first officer |
Qualification | pilot : flight engineer pilot : instrument pilot : multi engine pilot : atp pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 200 flight time total : 3000 flight time type : 200 |
ASRS Report | 430574 |
Events | |
Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure non adherence : far |
Independent Detector | aircraft equipment : tcas other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued alert controller : separated traffic none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew Other |
Miss Distance | horizontal : 9000 vertical : 0 |
Supplementary | |
Problem Areas | ATC Human Performance FAA |
Primary Problem | FAA |
Air Traffic Incident | other |
Narrative:
Last night we were inbound on the FMS runway 28R visual, just as last week with an altitude restr of 11000 ft MSL. We needed to ask bay approach for lower altitudes throughout the approach. We reached cedes intersection at 11000 ft MSL and 250 KTS. I slowed to 225 KTS and had to inquire about a lower altitude again. We were then given 7000 ft MSL late and then 4000 ft just prior to baron. Approximately at that time, I noticed an aircraft within a close proximity from the north. My map display was on 5 mi range (767-200). My first officer was changing frequency with his head down, when I queried approach about an aircraft that was to the north crossing my path at the altitude I was assigned and descending to. The closure rate was fast. At that time approach broke me off the approach and turned me 70 degrees to the right to avoid the aircraft, then back gain 90 degrees to the left. This all occurred over dumbarton bridge. I feel that bay approach is not conforming to any separation rules, they seem to be compromising the safety of the aircraft on the approachs to accommodate aircraft for time and slot allocation. The aircraft on this approach need separation. At this point I feel we should refuse visual approachs into sfo and the bay area, and only accept ILS approachs maybe then the spacing will become adequate.
Original NASA ASRS Text
Title: AN ACR B767-200 FLC RPTS THAT THEY LOST STANDARD SEPARATION WITH ANOTHER B767 WHILE BEING VECTORED FOR A VISUAL APCH.
Narrative: LAST NIGHT WE WERE INBOUND ON THE FMS RWY 28R VISUAL, JUST AS LAST WK WITH AN ALT RESTR OF 11000 FT MSL. WE NEEDED TO ASK BAY APCH FOR LOWER ALTS THROUGHOUT THE APCH. WE REACHED CEDES INTXN AT 11000 FT MSL AND 250 KTS. I SLOWED TO 225 KTS AND HAD TO INQUIRE ABOUT A LOWER ALT AGAIN. WE WERE THEN GIVEN 7000 FT MSL LATE AND THEN 4000 FT JUST PRIOR TO BARON. APPROX AT THAT TIME, I NOTICED AN ACFT WITHIN A CLOSE PROX FROM THE N. MY MAP DISPLAY WAS ON 5 MI RANGE (767-200). MY FO WAS CHANGING FREQ WITH HIS HEAD DOWN, WHEN I QUERIED APCH ABOUT AN ACFT THAT WAS TO THE N XING MY PATH AT THE ALT I WAS ASSIGNED AND DSNDING TO. THE CLOSURE RATE WAS FAST. AT THAT TIME APCH BROKE ME OFF THE APCH AND TURNED ME 70 DEGS TO THE R TO AVOID THE ACFT, THEN BACK GAIN 90 DEGS TO THE L. THIS ALL OCCURRED OVER DUMBARTON BRIDGE. I FEEL THAT BAY APCH IS NOT CONFORMING TO ANY SEPARATION RULES, THEY SEEM TO BE COMPROMISING THE SAFETY OF THE ACFT ON THE APCHS TO ACCOMMODATE ACFT FOR TIME AND SLOT ALLOCATION. THE ACFT ON THIS APCH NEED SEPARATION. AT THIS POINT I FEEL WE SHOULD REFUSE VISUAL APCHS INTO SFO AND THE BAY AREA, AND ONLY ACCEPT ILS APCHS MAYBE THEN THE SPACING WILL BECOME ADEQUATE.
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.