Narrative:

I want to start by saying thank you. The [safety reporting system] alert on the in-range notice prevented us from missing the company note on the jeppesen [chart] reminding us about being below sfo class B airspace on a portion of the arrival into oak. It did take a little time while beginning the descent to load the sfo airport in the efb; select the class B chart; and then try to go back and forth between two different airports in the jeppesen pages to decide exactly where we should slow down so as not to exceed 200 kts below the class B. The alert worked as advertised but I wanted to offer a few suggestions on how to help alleviate these types of potential pilot deviations from taking place in the future. Having a STAR procedure that has no speed and altitude restrictions published on it to slow to 200 kts before descending below class B airspace is a recipe for failure. The two arrivals the alert mention are: OAKES2 and EMZOH3. I think it would help to have jeppesen modify the arrivals to include speed and altitude restrictions to comply with speed limits under the class B; overlay the sfo class B chart on the oak arrivals to have an easy reference; or list the fixes on the company 10-10 page where we should slow to 200 kts by. I believe on the EMZOH3; the mynee fix is where we want to slow to 200. On the oakes 2; the prfct and bbubb fixes should have the same note. It would be best to have the STAR republished with inserted restrictions; but short of that; listing specifics on the 10-10; and or overlaying the sfo airspace on the oak stars would also be helpful. Thank you for looking into this and for the interim alerts on the in-range ACARS message.

Google
 

Original NASA ASRS Text

Title: Air carrier First Officer reported chart deficiencies related to Class B floor awareness on RNAV arrivals into SFO and OAK.

Narrative: I want to start by saying Thank You. The [safety reporting system] Alert on the in-range notice prevented us from missing the company note on the Jeppesen [chart] reminding us about being below SFO Class B airspace on a portion of the arrival into OAK. It did take a little time while beginning the descent to load the SFO airport in the EFB; select the Class B chart; and then try to go back and forth between two different airports in the Jeppesen pages to decide exactly where we should slow down so as not to exceed 200 kts below the Class B. The alert worked as advertised but I wanted to offer a few suggestions on how to help alleviate these types of potential pilot deviations from taking place in the future. Having a STAR procedure that has no speed and altitude restrictions published on it to slow to 200 kts before descending below Class B Airspace is a recipe for failure. The two arrivals the Alert mention are: OAKES2 and EMZOH3. I think it would help to have Jeppesen modify the arrivals to include speed and altitude restrictions to comply with speed limits under the Class B; overlay the SFO Class B chart on the OAK arrivals to have an easy reference; or list the fixes on the company 10-10 page where we should slow to 200 kts by. I believe on the EMZOH3; the MYNEE fix is where we want to slow to 200. On the OAKES 2; the PRFCT and BBUBB fixes should have the same note. It would be best to have the STAR republished with inserted restrictions; but short of that; listing specifics on the 10-10; and or overlaying the SFO airspace on the OAK STARS would also be helpful. Thank you for looking into this and for the interim Alerts on the in-range ACARS message.

Data retrieved from NASA's ASRS site 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.