Narrative:

I was operating a flight into sfo from the west. During our radar vectors to an enroute descent to ILS runway 28R in sfo; the sfo approach controller (norcal) directed us to descend to cross osi (woodside) VOR at 8;000 ft/MSL and then take up a heading of 040 for radar vectors to final for a visual to ILS runway 28R. As we received the clearance; and remembering a previous approach into sfo from osi; I advised my first officer to standby for a 'slam dunk' for the approach into sfo after woodside. My first officer replied that he had seen it all before; as well. Since osi is basically on an 11 mile dogleg to dumba intx from runway 28R; both the first officer and I thought that attitude clearance was a little high. The depicted minimum recommended altitude on the sfo ILS 28R; page 11-4; is 4;100 ft/MSL to dumba intx; 16 NM out on the approach. Using a normal 3/1 rule; to arrive at or slightly above dumba at 4;100 MSL; is 12 mile. But if you factor in slowing down from 250 KIAS to approximately 210 KIAS as well as descending 4;000 ft; you need an additional 5 miles. This is assuming the approach controller takes us to dumba or extends us downwind to turn final to the ILS 28R. Of course; that is not what the norcal approach controller did. Shortly after we crossed osi VOR and took up a heading of 030; norcal gave us a descent to 4;000 ft. Then she directed us to take up a heading of approximately 360 degrees; then 310-330 degrees and cleared us for a visual approach to 28R. You guessed it; we were now passing thru about 7;000 ft MSL at 240 KIAS heading toward the airport which was now about 12-14 miles away and the FAF about 7 miles away and 5;200 ft below. With a normal 3/1 rule; to arrive at the FAF configured for landing; from 8;000 MSL to 1;800 MSL would take approximately 18 miles; and slow from 240 to 145 KIAS would take 5-8 miles for a total of 23-26 miles in VFR conditions. The norcal controller had just given us a clearance to complete the same task in about 14 miles. Fortunately; it was VFR and clear. However; to complete the visual approach would require a high rate of descent of approximately 1;500-2;000 ft per minute or more; then slowing the aircraft and configuring for landing; and doing all of this with less than 12 miles. Not wanting to try to fly a 'controller induced acrobatic maneuver' to a landing after flying all night; or give my passengers a 'runaway roller coaster simulation' and put my flight attendants on the ceiling as they are scrambling to sit down of landing; I set up a maximum rate of descent of about 1;500 ft. I told my first officer if we were not slowed down; configured and stabilized by 1;000 ft AGL; then plan on us making a missed approach. The first officer agreed. Somehow; we were just able to slow and configure completely for landing at 1;000 MSL and completed a normal landing. This is a repeat for the same problem which occurred on another flight into sfo.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier arrival from the West was issued an 8;000 FT crossing restriction over OSI and vectors after to Runway 28R; the reporter voicing concern regarding the necessary descent profile given the flying distance to SFO.

Narrative: I was operating a flight into SFO from the West. During our RADAR vectors to an enroute descent to ILS Runway 28R in SFO; the SFO Approach Controller (NORCAL) directed us to descend to cross OSI (Woodside) VOR at 8;000 FT/MSL and then take up a heading of 040 for RADAR vectors to final for a visual to ILS Runway 28R. As we received the clearance; and remembering a previous approach into SFO from OSI; I advised my First Officer to standby for a 'slam dunk' for the approach into SFO after Woodside. My First Officer replied that he had seen it all before; as well. Since OSI is basically on an 11 mile dogleg to Dumba INTX from Runway 28R; both the First Officer and I thought that attitude clearance was a little high. The depicted minimum recommended altitude on the SFO ILS 28R; page 11-4; is 4;100 FT/MSL to Dumba INTX; 16 NM out on the approach. Using a normal 3/1 Rule; to arrive at or slightly above Dumba at 4;100 MSL; is 12 mile. But if you factor in slowing down from 250 KIAS to approximately 210 KIAS as well as descending 4;000 FT; you need an additional 5 miles. This is assuming the Approach Controller takes us to Dumba or extends us downwind to turn final to the ILS 28R. Of course; that is not what the NORCAL Approach Controller did. Shortly after we crossed OSI VOR and took up a heading of 030; NORCAL gave us a descent to 4;000 FT. Then she directed us to take up a heading of approximately 360 degrees; then 310-330 degrees and cleared us for a Visual Approach to 28R. You guessed it; we were now passing thru about 7;000 FT MSL at 240 KIAS heading toward the airport which was now about 12-14 miles away and the FAF about 7 miles away and 5;200 FT below. With a normal 3/1 Rule; to arrive at the FAF configured for landing; from 8;000 MSL to 1;800 MSL would take approximately 18 miles; and slow from 240 to 145 KIAS would take 5-8 miles for a total of 23-26 miles in VFR conditions. The NORCAL Controller had just given us a clearance to complete the same task in about 14 miles. Fortunately; it was VFR and clear. However; to complete the Visual Approach would require a high rate of descent of approximately 1;500-2;000 FT per minute OR more; then slowing the aircraft and configuring for landing; and doing all of this with less than 12 miles. Not wanting to try to fly a 'controller induced acrobatic maneuver' to a landing after flying all night; or give my passengers a 'runaway roller coaster simulation' and put my flight attendants on the ceiling as they are scrambling to sit down of landing; I set up a maximum rate of descent of about 1;500 FT. I told my First Officer if we were not slowed down; configured and stabilized by 1;000 FT AGL; then plan on us making a missed approach. The First Officer agreed. Somehow; we were just able to slow and configure completely for landing at 1;000 MSL and completed a normal landing. This is a repeat for the same problem which occurred on another flight into SFO.

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.